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.

Park from Device

The device-initiated parking workflow is triggered when the user removes the card from Apple Wallet. Since this action is performed directly on the device, it's guaranteed that the device is online.

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 device initiated parking workflow:

  1. Card Removal: The user selects the transit card and taps 'Remove Card' to initiate the removal process.

  2. Unlink Card: Apple notifies D1 Transit platform that the user wants to remove the transit card from his device. Since it's CBT, a park session is started.

  3. Park Card: Apple device connects to D1 Transit platform in order to read the content of the applet instance, so Transit Issuer can save the card state on backend side.

Sequence diagram

When the user selects the transit card for removal, Apple initiates a managePass API call to D1 Transit platform with the action unlink to indicate the intention to delete the card.

Park card

In CBT ecosystems, the applet instance is not deleted rigth away. Device connects to D1 Transit platform in order to execute commands that can be used for reading and updating applet content.

D1 Transit sends getDigitalCardBundleCommands to Transit Issuer to fetch the commands that shall be returned and executed on device side.

Several round trips may occur to complete the park session.

Once the park session is completed, the applet instance is deleted from the device.

Last updated

Was this helpful?