Wallet Post Provisioning Fare Product Purchase

The Wallet Post-Provisioning Fare Product Purchase workflow is initiated by the user through the Wallet app. The primary goal is for the user to purchase or renew a fare product and have it seamlessly applied to his transit card in Google Wallet for immediate use.

Workflow

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

Fare Product Selection: The user selects the fare product they wish to purchase. Options may include adding stored value to an existing balance or purchasing/renewing a commute plan.

Payment: Once the user authorizes the purchase of the selected fare product, the Payment Manager processes the payment.

Metadata Retrieval and Wallet Display Update: Upon receiving a metadataUpdated request, Google requests the updated card metadata from D1 Transit.

Fare Product Selection

Error Scenarios

Purchase not permitted

If the cohabitation rule engine determines that no products are available to purchase due to business rules, D1 Transit must notify Google by returning a response with an empty array. This indicates that no purchase actions are available for the selected card.

Payment

Upon the user authorizing the payment, a purchaseProducts API call is triggered and sent to D1 Transit platform, which sends a purchaseProducts request to Transit Issuer. Transit Issuer is responsible for ensuring the payment request is processed by the PSP.

After processing, the outcome of the transaction is communicated back to Google.

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.