Update token state from issuer backend

Use updateCardState to perform an issuer-initiated token LCM operation.

Typical use cases:

• Suspend or resume a token.

• Delete a token.

• Apply the same action to all tokens for a card.

Choose the scope

You can target:

• A single token, using virtualCardId.

• All tokens belonging to a card, using the card identifiers defined in the API.

See updateCardState for the full request schema.

Update a specific token

Token state update initiated by the issuer backend.

1

1. Call updateCardState

Call updateCardState from the issuer backend.

Include at least:

Parameter	Description
x-correlation-id	Correlates this LCM operation with subsequent callbacks. Generate a new value per operation.
virtualCardId	Identifies the token to update.
action	Specifies the state change to apply.

2

2. Wait for the token update to complete

The payment network and wallet provider apply the state change.

They update the token in the digital wallet application and in the TSP.

3

3. Handle notifyVirtualCardChange

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

See notifyVirtualCardChange.

Parameter	Description
x-correlation-id	Matches the value from updateCardState.
virtualCardId	Identifies the updated token.
action	Specifies the action performed.
errorCode	Indicates failure. For example, 221 means the device was not reachable after retries.

Handle notifyVirtualCardChange idempotently. Callbacks can be duplicated or delayed.

Update all tokens for a card

Token state update for all tokens belonging to a card.

Call updateCardState with the card identifiers defined in the API.

You receive one notifyVirtualCardChange callback per updated token.

Related documentation

• Update token state from wallet provider

• Handle enrollment failures