Network tokenization is the replacement of a payment card's number with a substitute value, a token, issued by the card network or another token service provider rather than by a merchant or processor. Each token is restricted to a particular merchant, device or channel, travels with a one-time cryptogram, and is updated automatically when the underlying card expires or is reissued. Card networks offer it through services such as the Visa Token Service and the Mastercard Digital Enablement Service.
It is one form of the wider practice of tokenization. The difference lies in who issues the token and where it works: a processor token is a reference inside one company's vault, while a network token is a full-format card credential recognised across the card system. Network tokens are a type of payment token as defined by EMVCo, and they are unrelated to crypto tokens.
Network tokenization in plain terms
Think of a hotel key card. The hotel never gives guests a master key; it programs a card that opens one room, for a set number of nights, and can be switched off at the front desk without changing any locks. If a guest loses it, the hotel simply makes a new one.
A network token works the same way for your card. The shop where you save your card, or the phone you tap at the till, holds a stand-in number that only works there. If that shop is hacked, the stolen numbers are useless elsewhere. When your bank sends you a new card, the stand-in number keeps working because the network quietly links it to the new card, so subscriptions and saved checkouts do not break.
How network tokens work
The framework comes from EMVCo, the industry body owned by the major card networks, which first published its Payment Tokenisation Specification Technical Framework in 2014 and later revised it. It defines several roles:
- Token service provider (TSP). Usually the card network, it creates tokens, keeps the link between each token and the real primary account number (PAN), and swaps one for the other during authorisation.
- Token requestor. The party that asks for a token: a merchant storing cards on file, a payment processor acting for merchants, or a digital wallet on a phone.
- Card issuer. The card issuer approves each token request, often after checking the cardholder's identity, and sees token transactions alongside normal ones.
When a token is used, the merchant sends it with a cryptogram generated for that single transaction. The network checks the cryptogram, confirms the token is being used in its permitted domain, converts it to the PAN and passes the request to the issuer for authorisation.
Domain controls and lifecycle updates
Two features set network tokens apart from other substitutes for card numbers.
- Domain restriction controls. A token can be limited to one merchant, one device, or one channel such as e-commerce. A token stolen from a merchant's database fails if presented anywhere else, which reduces the payoff from data breaches and much card-not-present fraud.
- Lifecycle management. Because the network holds the link to the card, it can update the token when the card is reissued, renewed or reported lost, and can suspend a single token without cancelling the card. This matters most for recurring payments, where outdated card details are a common cause of declines.
EMVCo's framework also lets a token carry an assurance indicator that tells participants how thoroughly the cardholder was verified when the token was created.
Adoption
Network tokens reached consumers at scale with mobile wallets such as Apple Pay, launched in the United States in October 2014, which stores a device-specific token instead of the card number. Card-on-file tokenisation for online merchants followed. Visa reported in its annual report that it had provisioned more than 16 billion tokens as of 30 September 2025. In June 2024 Mastercard set a goal of tokenising all e-commerce transactions in Europe by 2030.
Network tokens are also the base layer for agent payments. Visa Intelligent Commerce and Mastercard Agent Pay both give AI agents tokens scoped to the agent, so that agentic commerce purchases can be recognised, limited and switched off without exposing the card itself.
Network tokens compared with processor tokens
| Feature | Network token | Processor or vault token |
|---|---|---|
| Issued by | Card network or other token service provider | Payment processor, gateway or merchant vault |
| Format | Card-number format, recognised across the network | Any format, meaningful only to its issuer |
| Portability | Usable with any acquirer that supports tokens | Tied to one provider; switching needs a data migration |
| Card updates | Updated automatically by the network | Depend on separate account-updater services |
| Cryptogram | Required for each transaction | Not part of the design |
The two are often combined: a merchant may keep a processor token in its own systems that points to a network token held by the processor. Network tokenization reduces, but does not remove, a merchant's obligations under the Payment Card Industry Data Security Standard, and some merchants and smaller acquirers still lack full support for tokens, cryptograms and lifecycle messages.