Tokenization
Tokenization replaces sensitive data, such as a card number, with a random stand-in value called a token that's useless if stolen. The real data is stored securely elsewhere and only retrieved when truly needed.
Also called: data tokenization, payment tokenization, card tokenization
What is tokenization?
Tokenization swaps a sensitive value for a substitute. A card number like `4111 1111 1111 1111` becomes something like `tok_8f3a92c1`. The token can be stored and passed around business systems freely, because it has no meaning on its own. The real value is kept in a secure "vault", usually run by a payment processor or specialist provider, and only it can map the token back.
Tokenization vs. encryption
Encryption transforms data mathematically, so anyone with the key can reverse it. A token has no mathematical relationship to the original; without access to the vault, there's nothing to reverse. That's why stolen tokens are typically worthless.
Where it's used
- Card payments: online stores and point-of-sale systems store tokens from their payment processor instead of card numbers, including for repeat billing.
- Mobile wallets: Apple Pay and Google Pay use device-specific tokens instead of your real card number.
- Personal data: Social Security numbers or account numbers tokenized in databases and analytics.
Why it matters for businesses
The PCI Security Standards Council's tokenization guidance explains that replacing card numbers with tokens can reduce the number of systems that store cardholder data, and therefore the scope of PCI DSS assessments. For most small businesses, the easiest approach is to use a payment provider's hosted checkout or tokenization so card numbers never touch your systems at all.
Related terms
Sources
- PCI DSS Document Library: Tokenization Guidelines (PCI Security Standards Council)
- SP 800-122: Guide to Protecting the Confidentiality of PII (NIST)
Drafted with AI assistance, then edited and fact-checked by a person. How we use AI.
