> 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/wallet-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="https://533724207-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuVU9HE1S0V7GM7BaU9NB%2Fuploads%2Fv90Bujiqkrb6kHiAgaIA%2Fimage.png?alt=media&amp;token=6a398b8c-bd3c-46ea-b1df-7d7095f6a31c" 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 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/wallet-enablement/es/modelo-de-datos.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.