Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
⌘Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.
Read Applet Data
The Read Applet Data use case can be triggered by Transit Issuer when there is a need for the Back Office to read the last known state of the applet data.
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 read applet data workflow:
Read Applet Data session triggering: Transit issuer initiates the read of the applet data.
Read Applet Data execution: D1 Transit notifies the device through APNS that it needs to connect to D1 Transit platform in order to execute the Transit Issuer commands.
Sequence diagram
Read Applet Data session triggering
The Transit issuer instructs D1 Transit through handleEvent to start a session with the targeted device for reading the digital card applet data.
Read Applet Data execution
Once device is online, it will connect to D1 Transit server with a get pending commands request. 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 read session.
At the end of the read session, D1 Transit sends a retrieve bundle data notification to Transit Issuer.
Error Scenarios
Device Offline
As the request is not device-initiated, there is no certainty that the device will be online. In such cases, the request to read applet data may never reach the device.
