← Payment Reference GuidesSecurity Reference

Payment Tokenization

How real card numbers (FPAN) are replaced by tokens (DPAN) for digital wallets, card-on-file, and IoT payments. Covers the full lifecycle, cryptogram generation, and the Visa VTS vs. Mastercard MDES service comparison.

FPAN vs. DPAN

Payment tokenization replaces a cardholder's real card number (FPAN — Funding PAN) with a surrogate value (DPAN — Device/Digital PAN) that is useless outside a restricted domain. Defined by the EMVCo Payment Tokenization Specification v2.0+, the token passes the Luhn check and appears to be a valid PAN to legacy systems while being restricted to a specific device, merchant, or use case.

FPAN

Funding PAN

  • The real card number issued by the bank
  • 16-19 digits, Luhn-valid
  • Linked to cardholder's account
  • If compromised, entire card must be reissued
  • Stored in issuer's card management system
  • Never transmitted by tokenized wallets
→
DPAN

Device / Digital PAN

  • Token issued by Token Service Provider (TSP)
  • Same 16-digit format, Luhn-valid
  • Restricted to specific device / merchant / channel
  • If compromised, only that token is affected
  • Stored in device Secure Element or cloud
  • Used in actual payment transactions

Key Benefits

Breach Isolation

A merchant data breach exposes only DPANs, not real card numbers. No reissuance required for unaffected merchants.

Domain Restriction

Tokens are valid only within their provisioned domain. A mobile wallet token cannot be used for card-on-file at a different merchant.

Card on File

Merchants store DPAN instead of FPAN. Recurring charges continue uninterrupted even when the physical card is replaced.

Cryptographic Proof

Each transaction carries a fresh cryptogram (an EMV ARQC in store, TAVV or DSRP for remote payments) that the token service validates. Replays are declined.

🧩 Check yourself

Can you get a phone tap approved by a bank that has never seen the phone’s card number?

Medium · shortest route 6 hops · hints included
Put it into practice

Next steps

ToolToken Format CheckerSee what a token's format does and does not reveal: Luhn, network, valid length, masking limits — card or network token, custom token, or opaque vault ID.Open the tool ToolCustom Token GeneratorMake proprietary payment tokens without the card networks: vault tokens, vaultless FF1 format-preserving encryption or keyed hashes. Keep the BIN and last four, force a Luhn failure, and detokenize.Open the tool ToolWallet Provisioning InspectorIdentify and check push-provisioning payloads for Apple Pay and Google Wallet: PKAddPaymentPassRequest, Mastercard IIDD / Opaque Payment Card, push account receipts, Visa JWE fields, Google UAPP (OpenPGP) and app-to-app ID&V.Open the tool FlowNetwork token lifecycleSee the animated message flow, step by step, between every party involved.Watch the flow
Keep reading

Related articles

Authentication3D Secure (EMV 3DS)Authentication flows, message types, ECI values, SCA exemptionsRead article Card RailsISO 8583 ProtocolMessage structure, bitmap mechanics, 128 data elements, network variationsRead article ContactlessNFC in PaymentsHow a contactless tap works end to end — from RF layer to cryptogramRead article IdentityEUDI Wallet & PaymentseIDAS 2.0 deadlines, the SD-JWT VC / mdoc / OID4VP stack, wallet-based PSD2 SCARead article

Common questions

What is a network token?

A network token (DPAN) is a substitute card number issued by the scheme's token service that replaces the real PAN (FPAN) in transactions — the mechanism behind Apple Pay, Google Pay, and secure card-on-file.

What is the difference between a DPAN and an FPAN?

The FPAN is the funding PAN printed on the card; the DPAN is the device/merchant-specific token that represents it. The token service maps DPAN back to FPAN during authorization.

What are VTS and MDES?

Visa Token Service and Mastercard Digital Enablement Service are the schemes' tokenization platforms: they issue tokens, manage their lifecycle, and validate token cryptograms.

Why do tokenized payments use cryptograms?

A per-transaction cryptogram (e.g. TAVV) proves the token was used by the legitimate holder in its bound domain, so a stolen token is useless outside it.

What is the difference between DPAN and FPAN?

The FPAN (funding PAN) is the card number printed on the card. The DPAN (device PAN) is the network token stored in a wallet such as Apple Pay. Payments use the DPAN; the network’s token service maps it back to the FPAN before the issuer authorizes.

Can a token be converted back to the card number?

Only by the token service provider (for network tokens, Visa VTS or Mastercard MDES) during de-tokenization. Merchants and wallets never get the PAN back from a network token; the issuer sees both.

What is a token requestor?

An entity registered with a card network to request tokens — a wallet, a merchant, a PSP or a click-to-pay service. Each has a Token Requestor ID, and every token it receives can only be used in its domain.