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.
Google Transit Insights (GTI) Registration
With Google Transit Insights, Google is bringing a superior digital experience for Transit Issuers systems that support open loop.
It provides a means to deeply engage with contactless users and get full value from fares policy.
It helps users understand fares, build confidence in the system and grow trust in the transit agency.
Workflow
Below are the high level steps of the GTI registration workflow:
Discovery: when using a phone containing tokenized open loop card to enter Transit rails, the customer will see a notification about a new program on the phone and in the Google wallet if he opens it later.
Opt-in: The customer taps the notification and is taken to GTI program information and activation terms.
Registration: Google sends a register tokenized card request to D1 Transit in order to link existing device EMV token to a transit account. Once GTI registration is done, Google sends request to fetch Transit-related metadata.
Sequence diagram
Registration
When receiving the registerTokenizedPaymentCard from Google, D1 Transit sends a registerCardAccount to Back Office, so it can decrypt data provided and identify the token to be linked, using its payment gateway.
In case of re-registration (for example renewal of EMV token), Google sends a registerTokenizedPaymentCard with existing cardId. Based on configuration, D1 Transit either creates a new card account or uses the existing one.
Metadata
Google sends a request through metadata API to D1 Transit. D1 Transit returns them to Google by calling Transit Issuer with the get card account metadata API.
