Card issuing - Cards

This table lists the cards endpoints and the events they generate. For information on setting up event notifications, see the Data and reporting overview.

Endpoint

Event

Cards API

Create card

Card created

Associate noname card with customer

Customer bound to noname card

Update card information

Card updated

Update card status

Card updated

Reissue physical card

Card updated (old card)
Card created (new card)

Activate physical card

Card updated

Change card password

Card password changed

Reset password try count

Card updated

Rotate virtual card CVV

Card CVV updated

Start noname card bulk process

Card created
Card can be added to next scheduled embossing
Card embossing notification received
Embossing rejection file processed
Embossing summary received

See Embossing events for more information.

Update PIN from PINBlock

Card password changed

Append issuer script

Card issuer script notification received

Append update PIN script

Card issuer script notification received
Card password updated - When script executes

Automatic Billing Update file sent to Mastercard

ABU notification file sent

Cards on file API

Create card on file

Card on file created
Card on file validation result received
Card excluded

Update card on file

Card on file updated
If the card status is being changed to SUSPENDED, it also generates an Card excluded event

Create card validation

Card on file validation result received

If validation fails, an Card excluded event is generated.

Submit validation try

Card on file validation result received event with PENDING status.

If the verification/validation fails, an Card excluded event is generated and the card is deleted from the customer's wallet.

Card tokenization API

None directly via endpoints, though the tokenization process itself generates a number of events:
Token provisioning response received
Token provisioning rejected
Tokenization challenge sent

See Card tokenization flow and events for more information.