> 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/implement-tokenization/post-tokenization-through-mobile-sdk.md).

# Post-tokenization through mobile SDK

The mobile SDK enables issuers to implement some [post-tokenization requests](https://docs.payments.thalescloud.io/tokenization/implement-tokenization/post-tokenization-requests.md) directly in the issuer application.

These requests enable you to:

* Retrieve the digital cards for a given card `cardId` and **view** them in the issuer application UI.
* Allow the end user to **control** their digital cards.
* Activate a digital card installed in a mobile wallet after a successful ID\&V flow.
* Increase the token assurance method for a e-commerce digital card after a successful ID\&V flow.

{% hint style="info" %}
Integrating the mobile SDK into the issuer application is optional and subject to additional fees. Contact your Thales sales representative for details.
{% endhint %}

For more details regarding the integration of the mobile SDK into the issuer application, check the section [Integrate the D1 SDK](https://docs.payments.thalescloud.io/tokenization/integrate-the-d1-sdk.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/implement-tokenization/post-tokenization-through-mobile-sdk.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.
