Tokenization (payments)

Replacing sensitive card data with a non-sensitive substitute token so the real card number is never stored or reused by the merchant.

Definition

In payments, tokenization swaps the primary account number (PAN) for a surrogate value, a token, that has no exploitable meaning if stolen. A payment processor or the card scheme (network tokens) stores the mapping securely, so the merchant can charge, refund, or re-bill using the token without holding real card data, reducing PCI DSS scope and breach impact. Tokens can be scoped to a single merchant and even auto-updated when a card is reissued, improving success rates. Mobile wallets rely on this: Apple Pay and Google Pay present a device-specific token and cryptogram rather than the actual card number.

Worked example

After the first deposit, the processor returns a token that the operator stores; future deposits and any refunds are made against that token, and the raw card number never touches the operator's systems.

Why it matters

For learners, tokenization explains how merchants charge a saved card without storing it. For professionals, it lowers PCI scope and fraud exposure while improving authorisation rates through network tokens.

Further reading

Authoritative references for payments — regulators, standards bodies and primary sources. Independent, not affiliated.

• EMVCo — Payment Tokenisationemvco.com
• PCI SSC — Document Librarypcisecuritystandards.org
• PCI Security Standards Councilpcisecuritystandards.org
• EMVCoemvco.com
• PSD2 — Directive (EU) 2015/2366 (EUR-Lex)eur-lex.europa.eu
• European Banking Authority — Payment services and electronic moneyeba.europa.eu

Note: Distinct from data-security tokenization in general; here it refers specifically to card and network tokens.