Cards data events

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

EndpointEventURL
Cards API
Create cardcreate-1POST /wallet/v2/cards
Associate noname card with customerbind_card-1PUT /wallet/v2/cards/
{cardId}/noname/bind
Update card informationupdate-1PATCH /wallet/v2/cards/{cardId}
Update card statusupdate-1PUT /wallet/v1/customers/{customerId}/accounts/{{accountId}/cards/{cardId}/status
Reissue physical cardupdate-1 (old card)
create-1 (new card)
POST /wallet/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/reissue
Activate physical cardupdate-1PUT /wallet/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/activate
Change card passwordupdate_password-1PUT /pcicards/v2/pcicards/card/{cardId}
Reset password try countupdate-1POST /wallet/v2/cards/{cardId}/password-tries/reset
Rotate virtual card CVVrotate_cvv-1POST /pcicards/v2/pcicards/cvv/{cardId}/reset
Start noname card bulk processcreate-1
embossing_card_ingress-1
embossing-1
card_rejection-1
embossing-summary-1

See Embossing events for more information.
POST /cards/v1/bulks/{bulkID}/start
Update PIN from PINBlockupdate_password-1PUT /pcicards/v1/pcicards/{cardId}/pinblock
Append issuer script issuer-script_1POST /pcicards/v1/pcicards/{cardId}/scripts
Append update PIN scriptissuer-script_1
update_password-1 - When script executes
POST /pcicards/v1/pcicards/{cardId}/scripts/pin-update
Cards on file API
Create card on fileprovision-1
verification-1
exclusion-1
POST /cardsonfile/v3/cardsonfile/cards
Update card on filepatch-cards-1
If the card status is being changed to SUSPENDED, it also generates an exclusion-1 event
PATCH /cardsonfile/v3/cardsonfile/cards
Create card validationverification-1

If validation fails, an exclusion-1 event is generated.
POST /cardsonfile/v2/cardsonfile/cards/{uuid}/validations
Submit validation tryverification-1 event with PENDING status.

If the verification/validation fails, an exclusion-1 event is generated and the card is deleted from the customer's wallet.
POST /cardsonfile/v2/cardsonfile/cards/{uuid}/validations/{validationid}/tries
Card tokenization APINone directly via endpoints, though the tokenization process itself generates a number of events:
notification-1
notification_refusal-1
send_challenge-1

See Card tokenization flow and events for more information.