> 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/tokenization/es/implement-tokenization/card-tokenization-request.md).

# Solicitud de tokenización de tarjeta

Esta sección explica cómo D1 maneja un **Tokenización** solicitud iniciada por un **solicitante de token** (por ejemplo, **xPay Wallets**) y cómo interpretar la decisión devuelta a la red de pago **TSP** (por ejemplo, **MDES** o **VTS**).

{% hint style="info" %}
**Terminología en la API de D1**

En el **API de D1**, un **Usuario final** se denomina `consumidor` (por ejemplo, `consumerId`).
{% endhint %}

### Próximos pasos

* Entender cómo D1 evalúa la solicitud: [Procesando la decisión](https://docs.payments.thalescloud.io/tokenization/es/implement-tokenization/card-tokenization-request/processing-the-decision.md)
* Entender qué ocurre después de la decisión: [Procesando la respuesta](https://docs.payments.thalescloud.io/tokenization/es/implement-tokenization/card-tokenization-request/processing-the-response.md)


---

# 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/tokenization/es/implement-tokenization/card-tokenization-request.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.
