Jul 30

Environment	Date
Pre-Production	Jul 23, 2026
Production	Jul 30, 2026

Core

Improvements

• Validate the PAN against the card product BIN range in registerCard v1 when getCardCredentials API is called.

Tokenization (Classic)

Improvements

• VISA Card lifecycle use case: If a positive 'PAN Lifecycle' response has been received from VTS without PAN Update notification acknowledgment, at lifecycle session TTL expiration, a 'successful' (i.e. without any 'errorCode' ) notifyVirtualCardChange notification (one for each concerned token) is sent to the issuer.

xPay Enablement

Google Transit : Life Cycle Management - Support of Delete and Suspend Use-cases

• Park from Device

  Support of parking the device when the user initiates the park workflow from his wallet. Google attempts to delete the token on the device. Additionally, Google notifies D1 Transit platform of the deletion by sending a deleteToken request.
• Suspend/Resume from Google

  • The user initiates the suspension workflow by activating Lost Mode via the find my phone service. For each card in the user's Wallet, Google will attempt to suspend the token on the device, though this is on a best-effort basis since the device could be offline. Additionally, Google notifies D1 Transit platform of the suspension by sending a suspendToken request. D1 Transit then notifies the Transit Issuer so it can put the card to the deny list, ensuring it cannot be used for transit. This step is crucial if the device is offline, as the card may not be suspended immediately.
  • The user initiates the resumption process by authenticating to his device, which is currently in Lost Mode. For each card in the user's Wallet, Google will attempt to resume the tokens on the device, though this is on a best-effort basis since the device could be offline. Google notifies D1 Transit platform of the resumption by sending a resumeToken request. D1 Transit then notifies the Transit Issuer. Transit Issuer, if the card is on the deny list, can remove it to allow transit use.
• Suspend/Resume from Transit Issuer

  • Transit Issuer sends a manageDigitalCard to D1 Transit platform, which itself, sends handleTspEvent to Google. Upon receiving this request, Google fetches the state change to apply and attempt to apply it to the digital card on the device, though this is on a best-effort basis since the device could be offline. D1 Transit notifies the Transit Issuer that the state change order was submitted to Google.