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

# Overview

Network tokenization replaces PAN and expiration date with a payment network token. A Token Service Provider (TSP) issues the token, for example VTS or MDES. The token is bound to a token requestor that is the merchant. Use it for Card-on-file (COF) payments and avoid storing PAN in your systems.

<figure><img src="/files/CfoWKIJZL8KsTgx9Aqs7" alt=""><figcaption><p>Payment network tokenization actors</p></figcaption></figure>

### Actors

In a typical flow, you have:

* **End user**: Uses a card to complete an e-commerce transaction.
* **Merchant or PSP**: Acts as the token requestor for COF payments.
* **Acquirer**: Sends the transaction to the payment network.
* **Issuer**: Authorizes (or declines) the token creation and the transactions.
* **Payment network TSP**: Issues tokens, performs detokenization, and publishes LCM events.
* **Thales platform**: Provides a single integration point to multiple payment networks through one API.

### Benefits

* **Reduce risk for COF data** by storing tokens instead of PAN.
* **Stay current with LCM** using automated updates from the payment network TSP.
* **Simplify multi-network connectivity** by integrating once with Thales.

{% hint style="info" %}
Payment network Tokenization reduces PAN exposure, but it does not remove all PCI DSS obligations. Scope depends on your end-to-end flow.
{% 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.payments.thalescloud.io/merchant-tokenization/network-tokenization/overview.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.