> 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/merchant-tokenization/pci-tokenization/overview.md).

# Overview

## What it is ?

The Thales PCI Tokenization solution replaces an end user’s card data with a `tokenId`. The PAN and expiry date are stored in a PCI DSS-compliant vault.

Use it as a transition path to payment network Tokenization (VTS or MDES).

## How it works ?

1. The end user enters card details in your website or application.
2. Your backend encrypts and sends the PAN and expiry date to Thales backend.
3. Thales backend stores the data and returns a `tokenId`.
4. During a transaction, use the `tokenId` to retrieve the PAN and expiry date (detokenization).

## Typical use cases

* Support Card-on-file (COF) use cases (recurring payments, one-click checkout).
* Reduce the number of systems that process PAN data.
* Combine PCI Tokenization with payment network Tokenization (VTS or MDES).

## Benefits

* **Reduce PCI DSS scope.** Keep PAN handling limited to a smaller CDE (Cardholder Data Environment).
* **Lower breach impact.** Avoid storing PAN in your own databases.
* **Enable hybrid Tokenization.** Use PCI tokens as a fallback or transition path to payment network Tokenization.

{% hint style="info" %}
Thales platform is audited by an independent QSA. This supports PCI DSS compliance.
{% endhint %}


---

# 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/merchant-tokenization/pci-tokenization/overview.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.
