> 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/classic-tokenization/get-started/overview.md).

# Overview

The **Tokenization Service** provides a single integration point for an **Issuer** (and processors) to connect to international and domestic **TSPs** (token service providers).

It supports payment network tokenization platforms such as **VTS** (Visa Token Service) and **MDES** (Mastercard digital enablement service), plus domestic TSPs.

Issuers can digitize cards and provision them to **xPay Wallets** (Apple Pay, Google Pay, Samsung Pay) and other digital wallets.

Thales **TIG** is a turnkey component that covers the card digitization journey end-to-end: enrollment, provisioning, **LCM** (life cycle management), and Tokenization for secure payments.

### A single connection to the digital payment ecosystem

With a single connection to the Tokenization Service, you can:

* Digitize Visa, Mastercard, and domestic cards.
* Provision tokens to xPay Wallets.
* Support wearable wallets (for example, Garmin Pay and Fitbit).
* Enable e-commerce token use cases such as **Card-on-file (COF)** Tokenization and SRC (where supported).

The Tokenization Service also includes tooling to efficiently onboard new wallets. This helps you:

* Improve digital card management.
* Reduce integration and project delivery effort.

The Tokenization Service exposes an **Issuer Gateway API**. It stays aligned with payment network and wallet updates.

### Scheme compliance

Supported API families and versions include:

* **Visa (VTS)**: Visa Token Service JSON API 3.7
* **Mastercard (MDES)**:
  * MDES Customer Service
  * Pre-Digitization API 2.0.13
* **UPI**: Issuer Host JSON API v1.18
* **American Express**: Digital Wallet API v2.0
* **Discover (DDX - Discover Digital Exchange)**:
  * Issuer Wallet Services (Issuer) API specification v1.6
  * Issuer Wallet Services (NWP) API specification v1.5

Optional MDES APIs not supported:

* Notify Suspicious Events
* Authentication Service (Click to Pay)

<figure><img src="/files/PLRCtmEl8sv0jzzVaP5k" alt=""><figcaption><p>Tokenization Service ecosystem overview.</p></figcaption></figure>

### Concepts

The Tokenization Service supports:

* Card digitization and provisioning, including **ID\&V** (identification and verification).
  * In the **issuer application**
  * With step-up authentication initiated by the wallet provider
    * SMS OTP or email OTP
    * Customer service activation
    * Mobile banking authentication
* Card and token **LCM**.
* Card updates (for example, renewal).

#### Card digitization

The digitization and provisioning process typically consists of:

* Check card eligibility.
* Authenticate the **end user**.
* Provision the token to the wallet.

Example flow:

<figure><img src="/files/aOVsQbBBe4tCaebEa2P2" alt=""><figcaption><p>High-level card digitization flow.</p></figcaption></figure>

#### Payment

<figure><img src="/files/Hkrwn2xXozgSH7w4788p" alt=""><figcaption><p>Tokenized payment flow.</p></figcaption></figure>

#### Life cycle management

LCM actions can be initiated by the issuer backend, the end user, or the wallet provider.

**From the issuer backend**

* **Suspend**: Temporarily deactivate the token for payments.
* **Resume**: Reactivate the token for payments.
* **Delete**: Delete the token from the device.
* **Update card**: Update card details such as expiry, renewal, or product/profile changes.

**From the end user**

* **Delete**: Delete the token from the device.

**From the wallet provider**

* **Suspend** or **Delete**: Use when the end user loses their device.

<figure><img src="/files/VuPf4fu1OeucctZiD0Ec" alt=""><figcaption><p>Typical LCM actions and initiators.</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 dynamically by asking a question.

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

```
GET https://docs.payments.thalescloud.io/classic-tokenization/get-started/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.