Handle token updates from TSP

The payment network TSP can update a token. Thales backend forwards updates to your token requestor endpoint.

What triggers a token update ?

• The issuer updates the card details.

  • Renewal or reissue changes PAN last digits and/or PAN expiry date.
  • Card art can change.
• The payment network TSP updates token details.

  • Token expiry date can be extended.

    • Mastercard: token lifetime is typically 3 years.
    • Visa: Token expiry date equals card expiry date.
  • Token state can change.

    • DELETED: The card is destroyed or expired without renewal.
    • SUSPENDED: The Issuer blocks the card temporarily.

Flow

Token update notification flow.

Step	Description
1	The issuer backend informs the payment network TSP that card or token data changed.
2	The payment network TSP sends the update to Thales backend.
3	Thales backend notifies the token requestor (merchant or PSP) with the updated token data. Acknowledge the notification, even if you process it asynchronously.

API

Notify token update

Implementation notes

• Make your handler idempotent.
• Expect retries. Notifications can arrive out of order.
• Use lastUpdateTimestamp to discard obsolete updates.

If you store the token PAN, discard it when tokenLastDigits changes.

Fetch the latest token PAN using the Create Transaction API.