Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Cancel Card Account

The cancel card account workflow is triggered by Transit Issuer when the card account is cancelled (for example end user closed it)

Once a card account is cancelled, it's not possible to provision digital cards linked to it onto devices anymore.

This section provides an overview of the workflow, including detailed steps, sequence diagrams, and potential error scenarios.

Workflow

Below are the high level steps of the cancel card account workflow:

  1. Card Account Cancellation: Transit issuer initiates the cancellation of the user's card account.

  2. Delete Token: If a digital card linked to the card account is provisioned into a user's device, D1 Transit notifies Google that it needs to be removed.

  3. Card Account Deactivation: D1 Transit notifies Google that this card account can no longer be used.

Sequence diagram

Card Account Cancellation

The Transit issuer instructs D1 Transit to cancel the specified card account.

Delete Token

If a digital card exists in user's device, D1 Transit will notify Google server a token state update. Upon receiving such request from D1 Transit, Google server will request D1 Transit the state change to apply and perform the removal of the token.

Once Google has fetched the state change to D1 Transit, D1 Transit notifies Transit Issuer about the digital card deletion outcome.

Card Account Deactivation

In order to disable the card account to be used again, D1 Transit will notify Google with a card metadata updated notification. Once received, Google is fetching the card metadata from D1 Transit which will return that this card account is no longer available to the end user.

Last updated

Was this helpful?