> 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/xpay-enablement/es/modelo-de-datos.md).

# Modelo de datos

La API TR-TSP de Thales se basa en el siguiente modelo de datos.

<figure><img src="/files/f31024d8a6ffef9b2230dfc3a85dc7d7847d3b53" alt=""><figcaption><p>Identificadores principales utilizados por la API TR-TSP.</p></figcaption></figure>

| Identificador    | Descripción                                                                                                                                                                                                         | Propietario                     |
| ---------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------- |
| issuerId         | Identificador del emisor para el FPAN.                                                                                                                                                                              | TSH                             |
| cardProductId    | <p>El identificador del producto de tarjeta financiadora.<br>Este valor no se comparte con el TSP pero se mapea con el 'tokenProductId'.</p>                                                                        | TSH                             |
| cardRefId        | Identificador del FPAN conocido por el proveedor de la billetera o el backend del emisor.                                                                                                                           | Proveedor de billetera o emisor |
| walletProviderId | Identificador del proveedor de la billetera.                                                                                                                                                                        | TSH                             |
| tokenId          | El identificador del token.                                                                                                                                                                                         | TSP                             |
| tokenProductId   | Identificador del dominio del token.                                                                                                                                                                                | TSP                             |
| tokenStorageId   | <p>Identificador del elemento que aloja las credenciales del token.<br>Para (e)SE suele ser el identificador del elemento seguro.<br>Para HCE suele ser el identificador de la aplicación de billetera digital.</p> | Proveedor de billetera          |


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/xpay-enablement/es/modelo-de-datos.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.