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.

Thales platform is audited by an independent QSA. This supports PCI DSS compliance.