> 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/get-started/concepts/payments.md).

# Payments

Payment is the initial step toward obtaining a digital card when a provisioning or post provisioning fare product purchase is initiated from the Digital Wallets.

During these worklows, D1 Transit platform sends **purchaseProducts** API request to the Transit Issuer system, containing payment credentials built by the Digital Wallets.

It's up to the Transit Issuer to route these requests to the Payment Service Providers (PSPs), so they can validate the payment requests.

This means that the PSPs need to support the payment credentials format from the different Digital Wallets (i.e. Apple Pay, Google Pay)

{% hint style="info" %}
It is required with Apple Transit solution
{% endhint %}

More information about the payment credentials format can be found in the links below:

* [Apple Pay format](https://developer.apple.com/documentation/passkit/payment-token-format-reference)
* [Google Pay format](https://developers.google.com/pay/api/android/guides/resources/payment-data-cryptography)


---

# 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/get-started/concepts/payments.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.