> 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/post-tokenizacion-mediante-el-sdk-movil.md).

# Post-tokenización mediante el SDK móvil

El SDK móvil permite a los emisores implementar algunas [solicitudes posteriores a la tokenización](https://docs.payments.thalescloud.io/tokenization/es/implement-tokenization/post-tokenization-requests.md) directamente en la aplicación del emisor.

Estas solicitudes le permiten:

* Recuperar las tarjetas digitales de una tarjeta dada `cardId` y **vista** mostrarlas en la interfaz de usuario de la aplicación del emisor.
* Permitir al usuario final **controlar** sus tarjetas digitales.
* Activar una tarjeta digital instalada en una billetera móvil después de un flujo de ID\&V satisfactorio.
* Aumentar el método de aseguramiento del token para una tarjeta digital de comercio electrónico después de un flujo de ID\&V exitoso.

{% hint style="info" %}
La integración del SDK móvil en la aplicación del emisor es opcional y está sujeta a cargos adicionales. Póngase en contacto con su representante de ventas de Thales para obtener más información.
{% endhint %}

Para obtener más detalles sobre la integración del SDK móvil en la aplicación del emisor, consulte la sección [Integra el SDK de D1](https://docs.payments.thalescloud.io/tokenization/es/integra-el-sdk-de-d1.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/post-tokenizacion-mediante-el-sdk-movil.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.
