Part 3: Network tokens
Part 3 of 5 in a deep dive on card tokens, token vaults and where the card number went. Start with Part 1 if you are new to the series.
The card network becomes the vault
A vault token works inside one company. When the merchant charges the card, the vault puts the real number back and the number travels on to the processor, the card network and the issuing bank, as it always has. EMVCo is the body that maintains the EMV specifications for chip cards and other payment technology. In 2014 it published a standard for a token that travels that whole route in place of the number.
EMVCo defines payment tokenization as replacing the card number with a unique alternative value whose use can be limited to a specific merchant, device or type of transaction. Two roles come with it, as Evervault's guide explains. A token service provider, or TSP, creates the tokens and keeps the vault that maps each one to a card number. Visa runs one called Visa Token Service, and Mastercard runs one called MDES. A token requestor is whoever asks the TSP for a token. A phone wallet such as Apple Pay is one, and so is a merchant that wants to keep a card on file.
A network token looks like a card number. It has 13 to 19 digits, passes the Luhn check from Part 2 and starts with a bank identification number, so it fits through systems built for card numbers. One card has many of them. The card in your phone has one token, the same card saved at a streaming service has another, and each is unique to the requestor that asked for it.
The limit on where a token works is called a domain restriction. When the TSP creates a token it records what the token may be used for. The record can say online payments only or tap-to-pay only, name one merchant, or require a fresh one-time code with every payment. The network can refuse a token that shows up anywhere else. If a merchant's tokens are restricted to that merchant, a thief who copies its token file holds numbers that are refused everywhere else.
A code that works once
The second control is the cryptogram. A cryptogram is a short value that proves a payment request is fresh. For a payment the customer starts, the merchant asks the TSP for one, and the TSP returns a one-time value to send along with the token. The PCI council's position is that payment tokens must be used with a dynamic cryptogram or other domain controls enforced during the transaction, and that recovering the card number from a token alone is not feasible.
On a phone the code is produced in the device. Apple's description of Apple Pay says the bank or its provider creates a device-specific Device Account Number and sends it, with a key, to the phone's Secure Element. That is the certified chip I covered in the hardware wallet deep dive. For each payment the chip produces a dynamic security code from that key. Apple says it does not store the original card number and cannot decrypt the Device Account Number. The bank can also stop that number from working on a magnetic stripe card, over the phone or on a website.
A simplified model shows why a recorded payment cannot be replayed. Treat the code as a function f(key, counter). The key never leaves the chip or the token service, and the counter goes up by one with each payment. Someone who records a payment has f(key, 41). The next payment needs f(key, 42), and without the key there is no way to compute it. The token service knows the key and the last counter it accepted, so it computes f(key, 42) itself, compares, and refuses any counter it has already seen. This is my simplification of what Apple calls a transaction-specific dynamic security code.
The cryptogram covers payments the customer starts. For a subscription renewal the merchant charges the saved token with no customer present, and no cryptogram is needed. The merchant restriction is what protects the token there.
What the networks report
On Visa's network, tokens now carry most online payments. Visa issued its billionth token in 2020 and its 10 billionth in June 2024. As of April 2024, 29% of all the transactions it processed used a token. In October 2026 McInerney put the figure at over 60% of e-commerce transactions and over half of all available credentials. Mastercard said in June 2025 that almost half of its e-commerce transactions in Europe were tokenized, and a year later three in five. Its target is 100% by 2030.
The networks' case for tokens rests on fraud and approvals. The approval rate is the share of payment attempts that the issuing bank approves. A basis point is one hundredth of a percentage point. Visa said in 2024 that tokens had saved $650 million in fraud in a year and generated more than $40 billion in additional e-commerce revenue for businesses. The same release credits tokens with approval rates six basis points higher worldwide and a fraud rate up to 60% lower. Evervault, a payments security company, cites Deloitte figures of a 2.1% average rise in approval rates and a 26% drop in fraud rates, and reports 1% to 4% for its own recurring-payment customers.
The sources disagree on size. Visa's six basis points is 0.06 of a percentage point, and Deloitte's 2.1% is about 35 times that. All of these numbers come from the networks and from vendors, and I have not seen an independent audit of any of them.
Visa's Spring 2026 threats report covers July to December 2025. It found fraud on tokens held in phones and other devices down 9.6% from a year earlier. Enumeration is the automated guessing of card details, and losses from it were down 16%. The same report counts nearly $1 billion in scam-related fraud attempts and says the failures that matter most now happen at the boundaries between institutions.
A token also survives the card being replaced. When a bank issues a new card, the token service updates the link between the token and the new card, and merchants are told in near real time, so a saved token keeps working. On October 30, 2026 Visa turned on by default a service designed to raise the success rate of token requests for saved cards. The change covers the US, Canada, Asia-Pacific, and Central and Eastern Europe, the Middle East and Africa.
Who runs the vault decides
A merchant cannot turn a network token back into a number. That is what makes the token safe to store. It also means that whoever runs the token vault decides who gets a number back and at what price. Three cases show how that control is used.
The FTC and Mastercard's token vault
The Federal Trade Commission, or FTC, is a US regulator that enforces competition law. US law requires every debit card to work on at least two unaffiliated networks, so that a merchant can send a payment over the cheaper one. The FTC alleged that banks issuing Mastercard debit cards nearly always had Mastercard generate the wallet token and keep the account number in its token vault, and that Mastercard would not convert tokens for competing networks on online and in-app payments. Merchants then had no choice of network for those payments. The proposed order of December 23, 2022 requires Mastercard to give a competing network the account number behind a token. These were allegations. A consent agreement is a settlement, so they were never tested at trial.
Token services become a fee on every online sale
In April 2026 Visa changed its Digital Commerce Service Fee so that it applies to online transactions sent for authorization, the consultancy CMSPI reports. Authorization is the step where the issuing bank approves or declines a payment. Visa folded several token services into the fee. One is the check of the token's one-time code. Another is the account updater. That service refreshes saved card details when a card changes. CMSPI estimates that this adds about $122 million to US merchants' costs, and that a parallel change to Mastercard's Digital Enablement Fee adds about $125 million. Both figures are CMSPI's estimates from its own merchant data.
Tokens for AI agents
In November 2026 OpenAI launched ChatGPT Wallet with American Express, Mastercard and Visa for Pro subscribers in the US, The Paypers reports. The user approves each purchase with a face or fingerprint check, the card network then issues a token for it, and neither the AI agent nor the merchant receives the card number. Mastercard calls its version Agentic Tokens and says they keep an agent inside the permissions and limits the user sets. Stripe's Shared Payment Tokens are granted to one seller and carry a maximum amount and an expiration time.
A one-time virtual card is a card number made for a single purchase. Mastercard's chief executive Michael Miebach told analysts on October 29 that such cards are not a long-term way to handle payments by AI agents, American Banker reports. He added that Visa, Mastercard and American Express have all taken the position that tokens are the right technology for the job. A token with a seller, an amount and an expiration time is the card version of a rule from my last deep dive: give automation narrow authority and keep a person on the steps that cannot be undone.
Network tokens take the card number out of the merchant, the processor and everything between them, and a copied token is of little use outside the place it was issued for. They also create one event that matters more than any single payment, which is the moment a token is issued. Part 4 looks at that moment and at the other places the thefts went.
Continue to Part 4: Where the number went