A network token is a substitute card number issued by Visa (Visa Token Service) or Mastercard (Mastercard Digital Enablement Service) that works only for one device, merchant, checkout or AI agent, carries a one-time cryptogram, and is updated automatically when the bank reissues the card. Unlike a merchant or processor token, it travels to the issuing bank, which approves every token and authorizes every payment. Scale is network-wide: Visa had provisioned more than 16 billion tokens by 30 September 2025 and more than 17.5 billion by January 2026, and Mastercard's 2025 10-K says about 40% of its transactions are tokenized, with three in five European e-commerce payments tokenized by June 2026. Mastercard puts the approval gain at 3 to 6 percentage points; Visa reported fraud reduced by up to 60% (2024). Visa's April 2026 rules require active issuers to enable all BINs for card-absent tokens, keep tokens current with the latest card number and expiry, and approve at least 90% of provisioning requests per BIN each month, and they bar issuers from using token data for underwriting or marketing. The payment account reference (PAR) links all of a card's tokens without exposing the number. Click to Pay and payment passkeys (Visa, May 2024; Mastercard's 2030 plan) add authentication, and both networks' agent programs, Mastercard Agent Pay (April 2025) and Visa Intelligent Commerce (April 2025), run on tokens. The EU's final Payment Services Regulation text (April 2026) requires strong customer authentication when a token is created remotely.
PROFILES AND DOCUMENTS ON THIS SITE: Citi · U.S. Bank · NatWest · Santander · ING · Deutsche Bank · Commonwealth Bank · Capital One · Visa · Mastercard · Checkout.com · Stripe · Adyen · N26 · bunq
Visa tokens
16 billion+ at 30 Sep 2025 (10-K); 17.5 billion+ by Jan 2026
Mastercard
About 40% of all transactions tokenized in 2025 (10-K); 3 in 5 Europe e-commerce payments (Jun 2026)
Approvals
Mastercard: +3 to 6 percentage points; Visa: +6 basis points globally (2024)
Issuer rule
Visa active issuers: 90% monthly token provisioning approval rate per BIN
EU
PSR final text (Apr 2026): strong customer authentication when a token is created or replaced remotely
What is a network token, and how is it different from a card number or a merchant token?
A network token is a substitute card number issued by the card network, linked to the real card number (the primary account number, or PAN) and usable only in one place: one phone, one merchant, one checkout service or one AI agent. EMVCo, the standards body the networks own, says EMV Payment Tokenisation removes “the most valuable data to a fraudster, the primary account number (PAN)” and replaces it with “a unique alternative value” that “is constrained in how it can be used. For example, to a specific merchant, device or payment scenario.” Visa's FY2025 10-K describes its version the same way: the Visa Token Service (VTS) replaces “16-digit Visa account numbers with a token that includes a surrogate account number, cryptographic information and other data to protect the underlying account information.” Mastercard runs the equivalent service as the Mastercard Digital Enablement Service (MDES).
The distinction that matters for a bank is between network tokens and the tokens merchants and payment processors already used. Mastercard's April 2026 white paper on network tokenization sets it out: a payment service provider (PSP) token is generated by the PSP for one merchant, is “not sent to the issuer during payment authorization”, and is swapped back to the funding PAN before the card reaches the bank. A network token is issued by the network, travels the whole payment flow to the issuer, carries a one-time cryptogram on customer-initiated payments, and comes with lifecycle management, so it keeps working when the card is reissued. The two are often combined: merchants “will often retain a PSP token which is mapped by the provider to a network token”. The issuer only ever sees, and only ever approves, the network token.
| Credential | Who issues it | Where it works | Does the issuer see it? | Survives a card reissue? |
|---|---|---|---|---|
| PAN (card number) | Issuing bank | Anywhere the card is accepted | Yes | No; the new number must be re-entered or pushed through an updater |
| PSP / acquirer token | Payment service provider or acquirer | One merchant at one PSP | No; the PSP sends the PAN | Only if the PSP runs a card updater behind it |
| Device token | Network token service, at a wallet's request | One phone or wearable | Yes, with a cryptogram | Yes; the network updates it |
| Merchant (card-on-file) network token | Network token service, at a merchant's or PSP's request | One merchant | Yes | Yes |
| Click to Pay token | Network, through its checkout service | Participating checkouts | Yes | Yes |
| Agentic token | Network, for a registered agent (Mastercard Agentic Tokens; Visa Intelligent Commerce credentials) | One authorized agent, within the cardholder's limits | Yes, flagged as agent-initiated | Yes |
This page is about the infrastructure. For how small businesses adopt tokenized, virtual and wallet-first cards, and the networks' SME programs, see SME cards and tokenization; for how the four-party networks work with banks generally, see payment networks and bank partnerships.
Who does what in network tokenization, and what must the issuing bank do?
EMVCo's Technical Framework defines the roles; the networks' rulebooks turn them into obligations. A token requestor (a wallet such as Apple Pay, a merchant or PSP storing cards, a Click to Pay service or, now, an AI agent platform) asks for a token. The token service provider (VTS, MDES, or the American Express Token Service) creates it, keeps the vault and checks every use. The issuer decides whether the token is created, verifies the cardholder, and authorizes each payment. Acquirers and processors must carry the token and its data elements through. Visa's rule on issuer participation is explicit: an issuer using VTS “assumes full responsibility” for validating cardholder identity, “provisioning and maintenance decisions for Tokens”, compliance with terms and conditions, and “performing credential updates associated with Tokens and their underlying Payment Credentials” (Visa Core Rules and Visa Product and Service Rules, 18 April 2026 edition).
The Visa rulebook's token requirements by region (April 2026 edition)
Visa publishes its rules; Mastercard does not publish an equivalent public rulebook section on MDES issuer obligations, so the table below covers Visa only. Visa distinguishes a “Visa Token Service Active Issuer Participant” (the issuer runs its own token decisions) from a “Basic” participant, which Visa enrolls for card-absent transactions and, in several regions, for which Visa manages credential updates if the issuer does not. The approval rate in the table is defined in the rules as “the number of successful Token provisioning requests as a percentage of all eligible Token provisioning requests processed.”
| Region | BIN enablement | Token kept current (PAN and expiry) | Provisioning approval floor | Other |
|---|---|---|---|---|
| US | Active participants: all BINs enabled in VTS for card-absent transactions | An issuer responsibility; optional for Basic participants | 90% per BIN per month (Active) | Basic participants are enrolled by Visa |
| Europe | Active participants: all BINs enabled for card-absent | Required of every issuer | 90% (Active) | Issuers may opt out of Basic participation |
| Canada | All issuers: all BINs enabled for card-absent | Active participants; Visa manages updates for Basic participants that do not | 90% (Active) | — |
| Asia Pacific (most countries) | All issuers: all BINs enabled for card-absent | Active and Basic participants | 90% (Active) | From 18 Apr 2026, Active issuers in listed markets (e.g. Australia, Singapore, Japan) that allow manual provisioning to pass-through wallets must also support in-app provisioning |
| CEMEA | All issuers: all BINs enabled for card-absent | Active participants; Visa manages for Basic | 90% (Active) | Active issuers in listed markets (e.g. UAE, Saudi Arabia, Egypt) must actively offer cardholder-initiated push provisioning to all participating pass-through wallets |
| Latin America and Caribbean | All issuers: all BINs enabled for card-absent | Active participants; Visa manages for Basic | 90% (Active) | Issuers in Argentina, Bolivia, Chile, Paraguay and Uruguay must participate in VTS; from 24 Apr 2027 banking-app step-up authentication methods (online banking URL, app-to-app) |
Two further rules shape what a bank can do with tokens. First, card art: an issuer “must provide Visa with its Card artwork” and consent to Visa sharing it with third-party wallet token requestors, stored-credential token requestors, agentic payment provider token requestors and, from 25 July 2026, third parties using Click to Pay; if it does not, Visa supplies default art. Second, data: unless it has a bilateral agreement with the token requestor, an issuer may use token requestor data only for fraud prevention, token provisioning (“Issuer identification and verification [ID&V]”), transaction decisioning, customer service and operations, and “must not ... Use Visa Token Service data elements for underwriting or marketing purposes, or disclose these elements to any third party.” Device and requestor signals from tokens are for risk decisions, not for credit models or cross-selling.
How do the payment account reference, cryptograms and lifecycle updates work?
Payment account reference (PAR). Because one card can have dozens of tokens, merchants, transit operators and fraud teams need a way to recognize the same account without seeing the PAN. EMVCo describes PAR as “a way to link transactions that use EMV Payment Tokens with the Primary Account Number (PAN)”; in January 2026 it said it is enhancing the PAR data element in the Technical Framework to handle cases such as co-badged cards online and to support “increased adoption of PAR across the ecosystem”, and its April 2026 board update listed that work for the Singapore technical meeting. The Visa rules make PAR universal and restrict it: “A Visa payment account must have an associated Payment Account Reference”; acquirers must be able to deliver PAR to merchants; and acquirers and agentic payment enablers must ensure a PAR is not stored with the full credential, that “a Transaction is not initiated with a PAR”, and that it is used only for customer service, fraud and risk control, opted-in value-added services and legal compliance.
Cryptograms and domain controls. Mastercard's white paper explains that tokenized cardholder-initiated transactions “include a one-time cryptogram, which dynamically validates each transaction”, and that network tokens are “domain-bound”, so a stolen token is of little use outside its merchant or wallet. The PCI Security Standards Council relies on exactly those controls: its FAQ 1326 says payment tokens “must be used in conjunction with a dynamic token cryptogram and/or other sufficient domain controls”.
Lifecycle management. This is where the issuer's work shows up in merchants' revenue. When a card expires or is replaced after fraud, “the network then updates all associated tokens automatically”, Mastercard says, but only “when issuers provide lifecycle management updates on the underlying cards”; it asks issuers to send new expiry dates and reissued PANs through MDES and its Automatic Billing Updater (ABU), which passes account changes to merchants holding stored credentials. Visa writes the same duty into its rules: in every region a participating issuer must ensure a token reflects “the most up-to-date underlying Account Number” and expiry date. A bank that reissues cards without pushing the update to the token service produces the declines, churned subscriptions and call-center traffic that tokens were meant to remove.
| Mechanism | What it does | Issuer's job | Source |
|---|---|---|---|
| Identification and verification (ID&V) | Decides whether a token is created for this requestor and cardholder | Approve, decline or step up each request; keep Visa's 90% approval floor where it applies | Visa Rules, Apr 2026 |
| Provisioning risk score | Visa Provisioning Intelligence rates each provisioning request 1–99 for fraud likelihood | Use the score in the ID&V decision (value-added service) | Visa, Dec 2023 |
| Cryptogram | One-time value proving the token is used by its legitimate requestor | Validate (or rely on the network's validation) at authorization | Mastercard, Apr 2026; PCI SSC |
| PAR | Stable account reference across tokens and the PAN | Assign through the network; never treat as a payment credential | EMVCo; Visa Rules |
| Lifecycle update | Moves new PAN and expiry to every token and to card-on-file merchants (ABU at Mastercard) | Send updates on every reissue and expiry | Mastercard, Apr 2026; Visa Rules |
| Token assurance signal | Visa signal scoring a token's provisioning and behavioral history at each transaction | Consume it in authorization models | Visa, Jun 2026 |
What do Visa and Mastercard disclose about token volumes, approval rates and fraud?
Both networks publish adoption and performance figures, always from their own data and usually without method detail. The table collects them with their dates. Read the approval numbers carefully: Visa's June 2024 release reported a “six-basis point increase in payment approval rates globally” from tokenization, while Mastercard says tokenization grows approvals “by 3-6 percentage points across regions” (November 2024) or a “potential 3-6 percentage-point improvement in approvals on average” (April 2026). The two are not measured the same way, and neither release says what base or transaction mix it uses, so they should not be compared head to head.
| Figure | Network | As of | Source |
|---|---|---|---|
| 10 billion+ tokens issued since 2014 launch; 29% of all Visa-processed transactions tokenized; 8,000+ issuers enabled in 200+ markets | Visa | Apr–Jun 2024 | Visa release, 4 Jun 2024 |
| 16 billion+ tokens provisioned | Visa | 30 Sep 2025 | Visa FY2025 10-K |
| 17.5 billion+ tokens, more than triple the number of physical cards | Visa | Jan 2026 | PYMNTS, fiscal Q1 2026 results |
| Tokenized credentials nearly 60% of global e-commerce transactions | Visa | Fiscal Q3 2026 | PYMNTS, 3 Aug 2026 |
| $40 billion+ incremental e-commerce revenue and $650 million fraud saved in a year; fraud rate reduced “by up to 60%” | Visa | CY2023 data | Visa release, 4 Jun 2024 |
| Token provisioning fraud losses an estimated $450 million globally | Visa | 2022 | Visa release, 13 Dec 2023 |
| 25% of e-commerce transactions globally tokenized, adoption up 50% year on year | Mastercard | Jun 2024 | Mastercard release, 11 Jun 2024 |
| 30%+ of Mastercard transactions tokenized through MDES; India near 100% for e-commerce; up to $2 billion extra merchant sales a month | Mastercard | Nov 2024 | Mastercard release, 13 Nov 2024 |
| Approximately 40% of all Mastercard transactions tokenized | Mastercard | 2025 | Mastercard FY2025 10-K |
| More than half of e-commerce transactions on Mastercard tokenized; tokenized e-commerce volume more than doubled in two years | Mastercard | Apr 2026 | Mastercard white paper |
| Checkout.com merchants: +10.3 points approvals on tokenized transactions, −49% fraud-related chargebacks, +7.2% gross sales | Mastercard / Checkout.com | 2025 | Mastercard white paper, Apr 2026 |
| Three in five Mastercard e-commerce transactions in Europe tokenized; Secure Card on File live in 45 European countries and territories | Mastercard | 1 Jun 2026 | Mastercard Europe release |
The trend line is clear even with mismatched definitions: Visa went from 10 billion tokens (June 2024) to more than 17.5 billion (January 2026), and Mastercard from a quarter of e-commerce transactions (June 2024) to more than half (April 2026). PYMNTS reported that Mastercard's second-quarter 2026 earnings materials showed token penetration above 40%. The Checkout.com figures are one acquirer's portfolio, published by Mastercard in a co-branded paper, not an industry average.
What is not on the record: neither network publishes token approval or fraud figures by issuer, issuers do not report their own tokenized share, and no US bank we track discloses its token provisioning approval rate, even though Visa's rules set a 90% floor for active participants. No regulator publishes fraud rates for tokenized versus untokenized card-not-present payments. For the fraud models that sit on top of tokens, see AI fraud detection.
How do Click to Pay and payment passkeys build on tokens?
A token removes the card number; it does not prove the person paying is the cardholder. The networks pair tokens with two other pieces. Click to Pay is the networks' tokenized guest checkout: Visa's 10-K says it removes “time-consuming key entry” at checkout, and Mastercard calls it “a one-click checkout solution”. Payment passkeys add device biometrics under FIDO standards. Visa launched the Visa Payment Passkey Service on 15 May 2024, saying it “confirms a consumer's identity and authorizes online payments with a quick scan of their biometrics”, deployed it first inside Click to Pay, and said it would partner with issuers to enable both on new cards “from the moment the card arrives”. Its FY2025 10-K adds that Visa Payment Passkey “links the token to the consumer's device passkey information”.
Mastercard set the deadline. On 11 June 2024 it committed to 100% e-commerce tokenization in Europe by 2030, and on 13 November 2024 it extended the goal worldwide: by 2030 it aims “to eliminate the need for manual card entry and one-time or static passwords” and to ensure “every online transaction across its network can be tokenized and authenticated”. The same release named issuers enrolling card portfolios in Click to Pay (Commonwealth Bank of Australia, ING Spain, NatWest, Santander Mexico) and Axis Bank among deployers of the Payment Passkey Service. By 1 June 2026, Click to Pay was available in 32 European markets with enrolments more than doubling and returning customers over 70% of checkouts; NatWest and Tatra Banka were named as new tokenization partners and Capital One UK, Santander UK and Qonto among new Click to Pay partners.
- Token service: Visa Token Service, the Visa Cloud Token Framework and Token Management Service for sellers and acquirers; Mastercard MDES and Secure Card on File. The issuer supplies BIN enablement, ID&V decisions, lifecycle updates and card art.
- Checkout: Click to Pay at both networks. The issuer enrolls its portfolio so cardholders appear without typing a number.
- Authentication: Visa Payment Passkey Service (May 2024); Mastercard Payment Passkey Service and Identity Check (3DS). The issuer offers passkey enrolment in its app and steps up when risk is high.
The fraud has moved accordingly. Visa said in December 2023 that fraudsters “use social engineering and other scams to illegitimately provision tokens”, putting 2022 losses at about $450 million, and launched Visa Provisioning Intelligence, a machine-learning score from 1 to 99 delivered to issuers for each provisioning request. The attack surface for a tokenized card is the moment the token is created, which is why the EU has now written authentication at that moment into law (see below).
What does token-based agentic commerce ask of banks?
Both networks built their AI-agent payment programs on tokens, which means agentic commerce reaches banks as a token provisioning request. Mastercard launched Agent Pay on 29 April 2025 with “Mastercard Agentic Tokens” that build on the tokenization behind contactless, card-on-file and passkeys; agents must be “registered and verified”, and “every player in the value chain, from consumers to issuers and merchants, will be able to recognize the transactions that are facilitated by intelligent agents”. For banks, Mastercard said, tokenized credentials would keep “card issuers at the forefront ... with enhanced visibility, security, and control.” Visa announced Visa Intelligent Commerce the next day, offering “AI-ready cards” that replace card details “with tokenized digital credentials” and confirm “that a consumer's chosen agent is allowed to act on a consumer's behalf”; its 10-K says it “deployed a pilot program that processed live agentic token transactions” in 2025.
| Date | Network | Milestone | Bank-side implication |
|---|---|---|---|
| 29 Apr 2025 | Mastercard | Agent Pay and Agentic Tokens; agent registration and verification | Issuers see agent-initiated transactions flagged |
| 30 Apr 2025 | Visa | Visa Intelligent Commerce: tokenized credentials, consumer-set limits, commerce signals shared with Visa | Issuers receive agent context for authorization and disputes |
| 30 Sep 2025 | Mastercard | Agent Pay usable in ChatGPT Instant Checkout; Citi and U.S. Bank cardholders enabled, all US cardholders by mid-November | US issuers enabled at network level |
| 14 Oct 2025 | Visa | Trusted Agent Protocol, with Cloudflare, so merchants can tell trusted agents from bots | Merchant-side; issuers benefit from verified agent identity |
| 18 Dec 2025 | Visa | Hundreds of controlled agent-initiated transactions; 100+ partners, 30+ building in the sandbox | Pilots, not commercial volume |
| 18 Apr 2026 | Visa | Rulebook adds Agentic Payment Enabler and Provider requirements; wallets may be used in agentic transactions | Agent providers must verify cardholders, obtain consent and use Visa tokens |
| 2 Jun 2026 | Mastercard | All European issuers enabled at network level for Agent Pay; 36 named banks completed live passkey-authenticated agentic transactions | Issuers need passkey authentication ready |
| 10 Jun 2026 | Visa | Token enhancements: richer data on transaction type and payer, and a token assurance signal | New authorization inputs for issuer models |
Visa's April 2026 rules are the most concrete statement of what agentic commerce requires. An agentic payment provider must enroll in Visa Intelligent Commerce and register with Visa, obtain cardholder consent to provision a token and to use “the Cardholder-defined payment instruction”, state when that instruction expires, verify the cardholder's identity before storing a credential, use only the cardholder-defined criteria when buying, and, for stored credentials, “obtain a Token directly from Visa”. It may not run agentic transactions in a card-present environment or aggregate several agentic transactions into one. The provider must keep the cardholder agreement and give it “to the Cardholder or Issuer upon written request”, which is the record a bank will need when a customer disputes something their agent bought.
For the issuing bank, that adds up to four jobs: approve or decline agent token requests with the same ID&V discipline as wallet tokens; make passkey or in-app authentication available, since Mastercard's European transactions used passkeys; feed the new agent flags and token assurance signals into authorization; and set dispute handling for agent purchases. EMVCo formed an Agentic Payments Task Force (April 2026) to examine “consumer intent, trust in agent-initiated transactions and privacy-preserving interaction models” across 3DS, tokenization and Secure Remote Commerce, so the technical standard is still being written. Neither network has published agentic payment volumes. Banks named in pilots are listed on the network partnerships page and in agentic banking.
Which rules govern tokens: PCI DSS, Section 1033 and the EU Payment Services Regulation?
Three regimes touch tokens directly, and none of them mandates network tokenization outright; the mandates that exist come from network rules and, in some markets, central banks. What the public rules do is shrink compliance scope for token users, allow tokens in open banking, and, in the EU, require authentication when a token is created.
| Regime | What it says about tokens | Status (21 Oct 2026) | Source |
|---|---|---|---|
| PCI DSS (PCI SSC FAQ 1326) | An EMV payment token outside the token service provider's environment “is not considered Account Data and is therefore not in scope for PCI DSS”; systems that also touch PANs stay in scope; TSPs face additional requirements | FAQ dated May 2015, still published by the Council | PCI SSC |
| US Section 1033 (CFPB Personal Financial Data Rights rule) | Data providers “permitted to make available a tokenized account number instead of, or in addition to, a non-tokenized account number, as long as the tokenization is not used as a pretext to restrict competitive use” | Final rule published 18 Nov 2024; compliance dates stayed by court order in Oct 2025; reconsideration pending | Federal Register; CFPB |
| EU Payment Services Regulation (PSR) | Strong customer authentication when a payer orders “the creation or replacement of a tokenised payment instrument via a remote channel” (Art. 85); pass-through wallets that tokenize cards are technical services, and “a token cannot be regarded as being itself a payment instrument”; the payer's PSP keeps full liability for a wallet operator's SCA failures | Final compromise text circulated 17 Apr 2026 for agreement; not yet in force | Council of the EU |
| Visa rules (private, published) | BIN enablement, lifecycle updates, 90% provisioning approval floor, PAR, agentic provider duties | 18 Apr 2026 edition | Visa |
PCI DSS. The scope relief is the commercial argument merchants hear most, but it applies to the merchant's token-only systems. The FAQ is explicit that “PCI DSS still applies anywhere Account Data is stored, processed, or transmitted”, and an issuer, which holds the PANs, gets no relief for its own environment. Visa's agentic rules also require agentic payment enablers to comply with PCI DSS.
Section 1033. The 1033 tokens are bank-account tokens (tokenized account and routing numbers for pay-by-bank), not card tokens, but the logic is the same: the CFPB finalized an example allowing a data provider to share a tokenized account number, noted that doing so is optional, and recorded comments from third parties that tokens could be used anticompetitively. With compliance dates stayed and a reconsideration proposal pending (see open finance explained), nothing obliges a US bank to tokenize account numbers today, but the 2024 text shows where supervisors would draw the line.
PSD3 and the PSR. The final compromise text says there is “no consistent understanding” across member states of the SCA requirements for enrolling cards in digital wallets, and that token creation “may give rise to a risk of payment fraud”; the payer's PSP must therefore apply SCA at issuance or replacement of the token and “associate the user and the digitised version of the payment instrument with the respective device.” For an EU issuer, that turns token ID&V from a network rule into a legal obligation, and it applies to agent tokens created remotely as much as to phone wallets.
What should a bank do about network tokenization in 2026?
The direct answer: treat tokens as the default card credential for every digital channel and measure them like a product, because the networks have set 2030 as the date manual card entry ends and agentic commerce arrives as token requests. The list below is built from the obligations and figures above; each item maps to a rule or a disclosed metric.
- Enable every BIN for card-absent tokens. Visa already requires it for active participants in every region; include commercial and prepaid ranges, since Mastercard's Agent Pay examples include a virtual corporate card token.
- Measure the provisioning approval rate per BIN. Visa's floor is 90% a month for active participants. Report it alongside provisioning fraud, which Visa put at about $450 million globally in 2022, so the two are managed together rather than traded off blindly.
- Automate lifecycle updates. Send every reissue and expiry to VTS and MDES (and ABU) the day it happens; a token that still points to a closed card is a decline the merchant blames on the bank.
- Use the network risk signals. Visa Provisioning Intelligence at ID&V; the token assurance signal and agent flags at authorization. Keep token requestor data inside fraud and operations: Visa's rules bar its use for underwriting or marketing.
- Enroll portfolios in Click to Pay and offer passkeys in the app. Mastercard's European agentic transactions were passkey-authenticated, and the EU PSR will require SCA at remote token creation.
- Supply card art and keep it current. Visa shares it with wallets, card-on-file merchants, agent providers and, from 25 July 2026, Click to Pay; without it, cardholders see default art and may not recognize the card.
- Write the agent dispute playbook. Decide how agent-flagged transactions are authorized and disputed, and use the Visa rule that lets an issuer request the cardholder's agent agreement in writing.
- Show customers their tokens. A view in the banking app of which merchants, devices and agents hold a token, with the ability to revoke one without reissuing the card, is the control that makes agent payments acceptable to customers.
Banks that disclose tokenization metrics publicly remain rare, so the best public benchmarks are the networks' own: Visa's nearly 60% of global e-commerce tokenized (fiscal Q3 2026) and Mastercard's three in five in Europe (June 2026). A bank below those shares on its own e-commerce volume is behind its network. Profiles of the networks are at Visa and Mastercard.
What is the difference between a network token and a PSP or merchant token?
A PSP token is created by a payment processor for one merchant and is swapped back to the card number before the payment reaches the bank. A network token is issued by Visa or Mastercard, travels all the way to the issuer with a cryptogram, works across processors, and is updated automatically when the card is reissued.
What must an issuing bank do to support Visa Token Service?
Under Visa's April 2026 rules the issuer is responsible for cardholder verification, token provisioning decisions and credential updates. Active participants must enable all BINs for card-absent tokens, keep each token matched to the current card number and expiry, and approve at least 90% of eligible provisioning requests per BIN each month.
What is a payment account reference (PAR)?
PAR is a non-financial reference that links all the tokens issued for one card with the underlying account, so merchants, transit operators and fraud teams can recognize a customer without the card number. Visa's rules require every account to have one, forbid starting a transaction with it, and limit its use to service, risk and compliance.
How much do network tokens improve approval rates and reduce fraud?
Mastercard says tokenization lifts approvals by 3 to 6 percentage points on average and published Checkout.com data showing a 10.3-point gain and 49% fewer fraud chargebacks in 2025. Visa reported a six-basis-point global approval gain, $650 million of fraud saved and fraud reduced by up to 60% in its June 2024 release.
Do network tokens take a merchant out of PCI DSS scope?
Partly. The PCI Security Standards Council says an EMV payment token outside the token service provider's environment is not account data and is not in PCI DSS scope. Any system that also stores, processes or transmits card numbers, or connects to one that does, remains in scope, and issuers holding PANs get no relief.
How do AI agents use network tokens?
Both networks issue agent-specific tokens. Mastercard Agent Pay (April 2025) uses Agentic Tokens for registered, verified agents, and all European issuers were enabled by June 2026. Visa Intelligent Commerce (April 2025) uses tokenized credentials with consumer-set limits, and Visa's April 2026 rules require agent providers to get consent, verify cardholders and use Visa tokens.
Does EU law require tokenization or authentication for tokens?
It does not mandate tokenization, but the final compromise text of the Payment Services Regulation (17 April 2026) requires strong customer authentication whenever a payer creates or replaces a tokenized payment instrument through a remote channel, such as adding a card to a wallet, and keeps the bank liable for a wallet operator's authentication failures.
Does the US Section 1033 rule involve tokens?
Yes, for bank accounts rather than cards. The CFPB's 2024 Personal Financial Data Rights rule lets banks share a tokenized account number instead of the real one, provided tokenization is not a pretext to restrict competition. The rule's compliance dates were stayed in October 2025 and a reconsideration is pending, so nothing is enforceable today.
- EMV Payment Tokenisation — EMVCo, Jul 11, 2022 (emvco.com)
- Enabling Seamless and Secure Payments in 2026 — EMVCo, Jan 30, 2026 (emvco.com)
- Agentic Payments and Digital Payment Credentials: Highlights from the EMVCo Board of Advisors Meeting — EMVCo, Apr 10, 2026 (emvco.com)
- Visa Core Rules and Visa Product and Service Rules (18 April 2026 edition) — Visa, Apr 18, 2026 (usa.visa.com)
- Visa Inc. Annual Report on Form 10-K for fiscal 2025 — Visa Inc. via SEC EDGAR, Nov 6, 2025 (sec.gov)
- Mastercard Incorporated Annual Report on Form 10-K for 2025 — Mastercard via SEC EDGAR, Feb 11, 2026 (sec.gov)
- Visa Issues 10 Billionth Token, Generating $40 Billion in Incremental E-commerce Globally — Visa, Jun 4, 2024 (usa.visa.com)
- Visa Provisioning Intelligence Launches to Combat Token Fraud — Visa, Dec 13, 2023 (usa.visa.com)
- Visa Reinvents the Card, Unveils New Products for Digital Age (Visa Payment Passkey Service) — Visa, May 15, 2024 (usa.visa.com)
- The Future is Here: Visa Announces New Era of Commerce Featuring AI — Visa, Apr 30, 2025 (usa.visa.com)
- Visa Intelligent Commerce: product drop announcement — Visa, Apr 30, 2025 (corporate.visa.com)
- Visa Introduces Trusted Agent Protocol: An Ecosystem-Led Framework for AI Commerce — Visa, Oct 14, 2025 (usa.visa.com)
- Visa and Partners Complete Secure AI Transactions, Setting the Stage for Mainstream Adoption in 2026 — Visa, Dec 18, 2025 (usa.visa.com)
- Visa Announces New AI, Stablecoin and Token Innovations to Power Intelligent, Programmable Commerce at Visa Payments Forum — Visa, Jun 10, 2026 (usa.visa.com)
- Mastercard reimagines online checkout; commits to reaching 100% e-commerce tokenization by 2030 in Europe — Mastercard, Jun 11, 2024 (mastercard.com)
- Mastercard reinvents checkout with password and number free payments — Mastercard, Nov 13, 2024 (mastercard.com)
- Mastercard unveils Agent Pay, pioneering agentic payments technology to power commerce in the age of AI — Mastercard, Apr 29, 2025 (mastercard.com)
- Making agentic AI commerce a reality with embedded, trusted payments — Mastercard, Sep 30, 2025 (mastercard.com)
- Network tokenization: powering the e-commerce of today and tomorrow (white paper, April 2026) — Mastercard, Apr 1, 2026 (mastercard.com)
- Mastercard Advances Europe's Checkout Transformation on the Road to 2030 — Mastercard, Jun 1, 2026 (mastercard.com)
- Europe is Building the Foundations for Trusted Agentic Commerce — Mastercard, Jun 2, 2026 (newsroom.mastercard.com)
- Visa CEO Says Company Now a Payments 'Hyperscaler' — PYMNTS, Oct 29, 2025 (pymnts.com)
- Visa Credentials Soar as Payments Hyperscaler Eyes Agentic Commerce — PYMNTS, Jan 30, 2026 (pymnts.com)
- Card Networks Push Beyond Payments to Lock In Growth — PYMNTS, Aug 3, 2026 (pymnts.com)
- How does PCI DSS apply to EMVCo Payment Tokens? (FAQ 1326) — PCI Security Standards Council, May 1, 2015 (pcisecuritystandards.org)
- Required Rulemaking on Personal Financial Data Rights (final rule, 89 FR 90838) — Federal Register, Nov 18, 2024 (federalregister.gov)
- Personal financial data rights: compliance resources (compliance dates stayed) — Consumer Financial Protection Bureau, Oct 29, 2025 (consumerfinance.gov)
- Proposal for a Regulation on payment services in the internal market: confirmation of the final compromise text (8221/26) — Council of the European Union, Apr 17, 2026 (data.consilium.europa.eu)
When a bank, network or fintech moves on payments AI, the next morning's brief says so
when one of these regulators moves, the next morning's brief says so · six sourced stories · 7 am PT · free
plus every regulation, bank and agent page update, the morning after · leave any morning