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.
Transaction Notification
Notifications are triggered by Transit Issuer so the travel events can be displayed within the wallet.
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 message notification workflow:
Notification initiation : The Transit Issuer instructs D1 Transit to send transaction notification to a targeted digital card.
Wallet notification: D1 Transit uses Google notification API in order to send a push notification to the right wallet.
Transaction Details retrieval: Device connects to Google server which connects to D1 Transit platform in order to retrieve the content of the message.
Sequence Diagram
Notification initiation
The Transit issuer instructs D1 Transit to send transaction notification to the specified digital card using handleEvent API.
Device notification and Transaction Details retrieval
D1 Transit platform uses Google transactionEvent API to send a push notification to the wallet. The device, through Google server, connects to D1 Transit in order to retrieve the transaction details which D1 Transit pulls from Transit Issuer.
Error Scenarios
Device is offline
If the device is offline, the request to notify the transaction details is queued and will be sent to the device as soon as it reconnects.
