Payments · specification · EMVCo — the technical body collectively owned by American Express, Discover, JCB, Mastercard, UnionPay and Visa

EMV Payment Tokenisation

EMV Payment Tokenisation replaces a card’s primary account number (PAN) with a payment token that is constrained in how it can be used — to a specific merchant, device or payment scenario — so a stolen token is worth far less than a stolen card number. The EMVCo Technical Framework defines the roles (Token Service Providers, Token Requestors, BIN Controllers), the Payment Account Reference that links tokens back to an account, and the domain restrictions and cryptograms that protect each use. It is the foundation of mobile wallets and card-on-file tokens.

EMVCo — the technical body collectively owned by American Express, Discover, JCB, Mastercard, UnionPay and VisaGoverning body
2014First published
Technical Framework v2.4 (9 July 2026)Current version
1providers in the catalog

Also known as EMV Payment Tokenization, Network Tokenization, Payment Tokens, EMV Tokenisation.

Providers that carry EMV Payment Tokenisation 1

These providers' own APIs.json profiles carry EMV Payment Tokenisation as a tag — the provider's statement that the standard is part of what it does. APIs.io has not verified the implementation on this page; the de facto profiles on this site are where that measurement exists. Ordered by Kin Score.

Read from the API Evangelist standards directory, facts verified 2026-09-23. Provider links come from the catalog's own identity tags and are rebuilt nightly. If this page is wrong about a standard or a provider, say so.