Update token state from wallet provider

Some events trigger a token state update initiated by the wallet provider or the payment network TSP (for example, VTS or MDES).

Typical examples:

• End user deletes the token from the digital wallet application.

• End user loses or finds their phone and uses the wallet provider portal to suspend, resume, or delete tokens.

• Issuer uses the payment network customer care interface (CCI) to suspend, resume, or delete tokens.

Flow

Token state update initiated by the wallet provider or payment network TSP.

1

1. Initiate the token state update

The wallet provider or payment network TSP initiates the token state change.

2

2. Receive notifyVirtualCardChange

When the operation completes (or fails), you receive notifyVirtualCardChange.

See notifyVirtualCardChange.

Key parameters:

Parameter	Description
x-correlation-id	Correlates this callback with the related token state update.
virtualCardId	Identifies the updated token.
action	Specifies the action performed by the payment network or wallet provider.

Handle notifyVirtualCardChange idempotently. Callbacks can be duplicated or delayed.

Related documentation

• Update token state from issuer backend