> 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/es/comenzar/conceptos/pagos.md).

# Pagos

El pago es el paso inicial para obtener una tarjeta digital cuando se inicia una compra de un producto tarifario de aprovisionamiento o post-aprovisionamiento desde las Billeteras Digitales.

Durante estos flujos de trabajo, la plataforma D1 Transit envía **purchaseProducts** solicitud API al sistema del Emisor de Tránsito, que contiene credenciales de pago generadas por las Billeteras Digitales.

Corresponde al Emisor de Tránsito enrutar estas solicitudes a los Proveedores de Servicios de Pago (PSP), para que puedan validar las solicitudes de pago.

Esto significa que los PSP deben admitir el formato de credenciales de pago de las diferentes Billeteras Digitales (es decir, Apple Pay, Google Pay)

{% hint style="info" %}
Se requiere con la solución Apple Transit
{% endhint %}

Se puede encontrar más información sobre el formato de las credenciales de pago en los enlaces a continuación:

* [Formato de Apple Pay](https://developer.apple.com/documentation/passkit/payment-token-format-reference)
* [Formato de Google Pay](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/es/comenzar/conceptos/pagos.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.