Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
Payment card tokenisation replaces a card number with a surrogate value that is useless outside its intended context, shrinking both the breach impact and the PCI DSS assessment scope.

What Is Payment Card Tokenisation?
Tokenisation replaces a payment card number with a substitute value that carries no mathematical relationship to the original. The substitute, the token, can be stored, logged, passed between systems, and used to take a repeat payment, but on its own it cannot be used to construct the real card number. The mapping lives in one hardened place, either a token vault operated by a payment service provider or inside the card network itself.
The point is to change what a breach costs. A database of card numbers is immediately monetisable; a database of merchant-scoped tokens is close to worthless, because the tokens only work for transactions initiated by that merchant through that provider. Tokenisation does not make a system secure. It makes the consequences of failure much smaller, which is a different and often more achievable goal.
| Acquirer or vault tokens | Network tokens | |
|---|---|---|
| Issued by | The payment service provider or gateway | The card scheme, through a token service provider |
| Format | Any, often not card-like | A valid card number in its own right, with its own expiry |
| Scope | Usually one merchant and one provider | Restricted to a domain: a device, a merchant, or a channel |
| Lifecycle | Static unless the merchant replaces it | Updated automatically when the underlying card is reissued |
| Typical use | Card on file, recurring billing | Wallets, in-app payments, card on file at scale |
Wallet payments use the network variant. When a card is added to a phone, the wallet stores a device-specific token and a cryptographic key rather than the card number, and each transaction carries a one-time cryptogram. Losing the phone does not disclose the card, and the token can be revoked without reissuing it.
If a merchant never receives, processes, or stores the card number, the systems handling only tokens fall outside the cardholder data environment for assessment purposes. That is the commercial driver behind most tokenisation projects, and it is real, but the qualifying conditions are strict:
That last point is the one merchants get wrong. PCI DSS version 4 made it explicit by adding requirements on managing and monitoring the scripts loaded into a payment page, with a compliance date of 31 March 2025. The reason is web skimming: a tokenised merchant that loads a compromised third-party script still loses every card entered on its checkout, because the skimmer reads the keystrokes before tokenisation happens.
PCI DSS is a contractual requirement imposed by the card schemes and acquirers rather than a statute, but in the UK a card data breach is also a personal data breach, reportable to the Information Commissioner’s Office within 72 hours, and the ICO has treated weak protection of payment data as a failure of the security principle. Tokenisation reduces the volume of card data held, which is also a straightforward application of data minimisation.
In Turkey, card payments are supervised by the banking regulator under Law No. 5464 on bank cards and credit cards, and card data held by merchants and payment providers is personal data under KVKK, with its own security obligations and administrative fines for failure. Turkish acquirers commonly provide card storage services so that merchants do not hold the number at all, and group merchants operating in both markets should check whether their Turkish tokens are portable before assuming a single vault can serve both.
Our regulation and compliance services validate tokenisation boundaries in practice, including whether anything in the checkout path still touches the card number.
No. Encryption transforms the card number mathematically, so anyone with the key can reverse it, and the ciphertext stays in scope for assessment. A token has no mathematical relationship to the card number; recovery requires a lookup in the vault that issued it. Encryption protects data in transit and at rest; tokenisation removes the sensitive value from your systems entirely.
It reduces scope, it does not eliminate obligation. Your payment page, the systems that serve it, and the integration with the provider remain in scope, and version 4 added explicit requirements for managing and monitoring payment page scripts. Most tokenised e-commerce merchants move to a lighter self-assessment questionnaire rather than escaping assessment altogether.
Network tokens are updated automatically by the scheme, so recurring billing continues without the customer re-entering details, which is one of their main commercial advantages. Vault tokens issued by a provider are generally static and break when the card is replaced, unless the provider subscribes to an account updater service on the merchant’s behalf.
Not if domain restriction is configured properly. Tokens are bound to a merchant, a channel, or a device, and a token presented from outside its domain should be declined. The risk comes from poorly scoped vault tokens and from attackers who have also compromised the merchant’s own payment integration, in which case they are using the token exactly as the merchant would.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.