Lifecycle Management

Life cycle management (LCM) is very important to deliver an optimal user experience throughout the lifetime of card accounts and digital cards.

This section below describes the core aspects of LCM.

To begin with, details about the 6 main LCM actions:

• Provisioning
• Park and Recover
• Suspend and Resume
• Delete

Then, a view on Card Account and Digital Card state management within D1 Transit solution.

LifeCycle Management Actions

Provisioning

Provisioning adds a transit digital card to the Digital Wallets. There are 2 ways to provision a digital card:

• From Wallet (aka DCI for Apple)
• From Transit operator application (aka In-app provisioning for Apple, Push provisioning for Google)

Park and Recover

Parking a digital card removes its instance from the Wallet temporarily while maintaining relative card account association with the user's wallet account. Parking can be initiated by both the Issuer and the user.

Users can "recover", or add a card from the user's wallet account to the Wallet.

Suspend and Resume

When a transit digital card is suspended in the Wallet, the card remains visible and accessible to the user, but NFC capabilities are disabled.

Resuming a card reverses the effects of a suspension. Resumption can be initiated by both the Issuer and the user.

Delete

Deletion unbinds the card from the user's wallet account and removes it from the Digital Wallet ecosystem. Both the Transit Issuer and the user can request deletion.

States

Card Account

Card Account state management within D1 Transit platform is as follows.

A card account can be either:

• active: the state a card account is in, when sucessful purchase is performed for initial provisioning.
• parked: the state a card account is in, when park was successfully completed (i.e. digital card linked to this card account was deleted)
• cancelled: card account moves to this state when Transit Issuer requests it through a cancelCardAccount API call. It's a non-reversible state.

card account reference is completely removed from D1 Transit platform when there is no provisioning request from Digital Wallet within a configured TTL.

Digital Card

Digital Card state management within D1 Transit platform is as follows.

A digital card can be either:

• created: the initial state of a digital card, before its provisioning to a device.
• failed_provisioning: in case of failed initial provisioning, a digital card goes into this state.
• active: the state a digital card is in, when fully provisioned into a device.
• suspended (wallet or issuer): digital card moves to this state when either Transit Issuer or Digital Wallet requests the suspension of this digital card.
• unlinked: digital card moves to this state when a park request is done, but there is no guarantee that it's removed from device, i.e. when triggered from cloud or transit issuer side.
• deleted: digital card moves to this state when there is a confirmation that the digital card was removed from the device.

digital card reference is completely removed from D1 Transit platform when there is no provisioning request from Digital Wallet within a configured TTL.

The transitions of a digital card state are slightly different between ABT and CBT.

Account Based Ticketing

The state diagram below illustrates the different transitions in ABT context.

Card Based Ticketing

The state diagram below illustrates the different transitions in CBT context.