Welcome to our new developer portal! Use the "Ask" button to chat with our AI Agent.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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

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

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

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.

Last updated

Was this helpful?