> For the complete documentation index, see [llms.txt](https://docs.payments.thalescloud.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payments.thalescloud.io/transit-digitization/implement-google-transit/account-based-ticketing-abt/google-transit-insights-gti-registration.md).
# 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:
1. **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.
2. **Opt-in**: The customer taps the notification and is taken to GTI program information and activation terms.
3. **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.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.payments.thalescloud.io/transit-digitization/implement-google-transit/account-based-ticketing-abt/google-transit-insights-gti-registration.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
%20Registration.svg?alt=media&token=b8dc6bb6-fd40-4988-8da1-3357fa8096a1){kind=spacer}