> 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/transit-app-post-provisioning-fare-product-purchase.md).

# Transit App Post Provisioning Fare Product Purchase

The Transit App Post-Provisioning Fare Product Purchase workflow is initiated by the user directly through the transit operator's app. The primary goal is for the user to purchase a fare product within the app and have it seamlessly applied to their transit card in Google Wallet for immediate use.

### Workflow <a href="#workflow" id="workflow"></a>

The following high level steps outline the Transit App Post-Provisioning Fare Product Purchase workflow:

1. **Fare Product Selection and Payment**: The user selects the fare product they wish to purchase from the transit operator's app. It may include adding stored value to an existing balance or purchasing/renewing a fare product.
2. **Metadata Retrieval and Wallet Display Update**: Upon receiving a metadataUpdated request, Google requests the updated card metadata from D1 Transit..

#### Fare Product Selection and Payment <a href="#fare-product-selection-and-payment" id="fare-product-selection-and-payment"></a>

Before the workflow begins, the user must select an eligible fare product within the transit operator's app to add to his transit card.

Once a fare product is selected, the app should display payment options for the user to complete the purchase. The user can then choose his preferred payment method from the available options.

**Error Scenarios**

**Purchase or renewal not allowed**

If the purchase or renewal of a fare product is prohibited due to business rules (e.g., expired card or ineligible fare product), the transit operator's app shall indicate it to the user.

#### Metadata Retrieval and Wallet Display Update <a href="#metadata-retrieval-and-wallet-display-update" id="metadata-retrieval-and-wallet-display-update"></a>

After successfully purchasing or renewing a fare product, Transit Issuer sends handleEvent to D1 Transit which then notifies Google with allProductMetadataUpdated API request.

Upon receiving the allProductMetadataUpdated request, Google retrieves the product metadata by making a getAllProductMetadata request to D1 Transit.

<figure><img src="https://1928701359-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FZoFRCpZeaDWwcHYhJY7B%2Fuploads%2FdS0dInxZgApSfAr7ArGs%2FSequence%20Diagram%20%E2%80%93%20Transit%20App%20Post%20Provisioning%20Fare%20Product%20Purchase.svg?alt=media&amp;token=6eef0691-3857-4460-ba44-5e821a38659b" alt=""><figcaption></figcaption></figure>


---

# 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/transit-app-post-provisioning-fare-product-purchase.md?ask=<question>&goal=<user_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.