Cards data events

Cards API

Create card

create-1

POST /wallet/v2/cards

Associate noname card with customer

bind_card-1

PUT /wallet/v2/cards/
{cardId}/noname/bind

Update card information

update-1

PATCH /wallet/v2/cards/{cardId}

Update card status

update-1

PUT /wallet/v1/customers/{customerId}/accounts/{{accountId}/cards/{cardId}/status

Reissue plastic card

update-1

POST /wallet/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/reissue

Activate physical card

update-1

PUT /wallet/v1/customers/{customerId}/accounts/{accountId}/cards/{cardId}/activate

Change card password

update_password-1

PUT /pcicards/v2/pcicards/card/{cardId}

Rotate virtual card CVV

rotate_cvv-1

POST /pcicards/v2/pcicards/cvv/{cardId}/reset

Start noname card bulk process

create-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 PINBlock

update_password-1

PUT /pcicards/v1/pcicards/{cardId}/pinblock

Cards on file API

Create card on file

provision-1
verification-1
exclusion-1

POST /cardsonfile/v3/cardsonfile/cards

Update card on file

patch-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 validation

verification-1

If validation fails, an exclusion-1 event is generated.

POST /cardsonfile/v2/cardsonfile/cards/{uuid}/validations

Submit validation try

verification-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 API

None 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.