> 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/use-cases/token-re-personalization/thales-initiated.md).

# Thales-initiated

An issuer may update a banking profile to enable new features (for example, remote payment or transit).

Once the new profile is deployed in the Production Environment, Thales can trigger a re-personalization campaign for all active tokens.

Thales does not retain token data elements generated by the TSP.

Because of that, Thales calls the TSP to recover the existing elements and rebuild the full profile.

{% hint style="info" %}
The TSP must recover the existing data associated with the token.

The TSP must not generate new data.
{% endhint %}

{% hint style="info" %}
After receiving a successful notification from Thales, the TSP must set ATC to `0`.

This keeps ATC synchronized between the device and the TSP.
{% endhint %}

<figure><img src="https://3928551874-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FuVU9HE1S0V7GM7BaU9NB%2Fuploads%2FO6yatvjyOdhPswJh1KcR%2Fimage.png?alt=media&amp;token=f34a2cb3-7c4a-4373-bb60-3319c6e6adb8" alt=""><figcaption><p>Thales-initiated token re-personalization flow.</p></figcaption></figure>


---

# 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/use-cases/token-re-personalization/thales-initiated.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.