Digital Wallet Tokenisation: Architecture, Security and Challenges

How digital wallet tokenisation replaces card numbers with device-bound tokens — network versus PSP tokens, the standards behind them, and what breaks in practice.

2026-11-16 · 8 min read

Key takeaways

  • Tokenisation swaps the card number for a device-bound token that only the token service provider can resolve
  • Network tokens travel end to end and carry domain restrictions, while PSP tokens stay inside one provider's vault
  • PCI DSS scope shrinks only where PAN is provably unrecoverable and the systems are segmented
  • Adoption is limited less by cryptography than by provisioning friction, token lifecycle operations and portability between providers

What a digital wallet token actually is

A card number — the primary account number (PAN) — is reusable. Anyone who captures it can attempt a payment with it, in any channel, for as long as the card stays valid. Digital wallet tokenisation breaks that property: the PAN is exchanged for a substitute value that is bound to a specific device, merchant or channel and has no usable meaning outside the environment it was issued for.

Visa describes its version of the technique as replacing the card account number with a token that only the network can unlock (Visa Token Service factsheet).

It is worth being precise about what a token is not. It is not encryption — encryption is reversible with a key, and a token is resolved through a lookup at a service that can choose to refuse. It is not hashing — a hash cannot be routed through card rails. A token is closer to a pointer plus a policy: an identifier that a specific service can map back to an account, under conditions it controls.

The EMVCo Payment Tokenisation Specification defines the roles around that idea (EMVCo Payment Tokenisation):

  • Token requestor — the wallet, merchant app or PSP that asks for a token.
  • Token service provider (TSP) — generates the token, keeps the mapping and returns it when a valid payment request arrives.
  • Token user — initiates a payment using a token it received.
  • Payment account reference (PAR) — a non-sensitive value that lets issuers, fraud systems and loyalty programmes link all the tokens for one account without exposing the PAN.

Tokens usually keep the PAN's length and format, so terminals, acquirers and switches need no changes to carry them. That format preservation is deliberate: it let the industry deploy tokenisation across an installed base that already understands card numbers.

How a token gets into a wallet

Provisioning is where most implementation work sits. A typical flow looks like this:

  1. The cardholder adds a card inside a wallet app or a merchant app. That app registers as a token requestor.
  2. The request goes to a TSP — in practice a scheme token service, an issuer-side service, or a combination of both.
  3. The issuer authenticates the cardholder before the credential is created. In the EU, the European Banking Authority has confirmed that enrolling a card into a digital wallet creates a digitised version of that card and therefore requires strong customer authentication (SCA) under PSD2, because the action carries fraud risk (EBA press release).
  4. The TSP returns a token bound to the device and to an intended use, together with metadata such as a token assurance level and the PAR.
  5. The wallet stores the token in secure hardware or an operating-system keystore. Payment cryptograms are generated on the device with keys that are not extractable in practice.
  6. Each transaction carries the token plus a fresh cryptogram. The issuer or TSP checks that the token matches the requesting domain and that the cryptogram is genuine and unused before authorising.

The practical consequence for a product team: a token captured from a merchant's logs is not a card number. Replaying it in another channel or with another acquirer should fail, provided the domain restrictions are enforced end to end.

Network tokens and PSP tokens are not the same thing

Two families of tokens dominate wallet and card-on-file work, and they behave very differently when something goes wrong.

Aspect Network token PSP / merchant token
Issued by Scheme or issuer-side token service provider The PSP or merchant vault
Travels across schemes Yes — end to end to the issuer No — resolved only inside that provider's stack
Domain restrictions Yes, enforced by the token service provider Limited, usually implemented by the provider itself
Lifecycle updates Card replacement, expiry changes and account updates flow through Merchant or PSP must handle updates itself
Portability Portable across acquirers and channels Not portable; migrating means re-capturing card data

Network tokens carry token domain restriction controls, which EMVCo describes as one of the features that distinguishes EMV payment tokens from other forms of tokenisation (EMVCo quick reference guide, PDF). A token issued for e-commerce can be constrained so that it is not accepted in a different environment.

PSP tokens are cheaper to adopt and useful for reducing card data inside one platform, but they solve a narrower problem. We compared the two models in detail in Payment Card Tokenisation: Network Tokens vs PSP Tokens.

What the schemes report

The commercial case is largely built on scheme-published data.

Visa says it has issued more than 10 billion tokens since launching the service in 2014, that more than 8,000 issuers and 200-plus markets are enabled, and that tokenised transactions generated over USD 40 billion in incremental e-commerce revenue while saving USD 650 million in fraud in a single year (Visa announcement).

Mastercard reported that nearly 40% of all transactions switched across its network were tokenised as of December 2025, according to its annual shareholder letter, and has committed to 100% tokenisation of e-commerce payments in Europe by 2030 (Mastercard shareholder letter, 2024 European commitment). Mastercard also notes that there are now more tokens enabled for digital payments than physical cards in circulation — a direct consequence of one PAN spawning a separate token per device, merchant and channel (Mastercard explainer).

Treat these as vendor-reported figures. They are directionally strong, but tokenised volumes are not separately broken out in interchange or fraud disclosures, so independent benchmarking is difficult.

The standards layer that underpins it

EMVCo

The EMVCo Payment Tokenisation Specification — Technical Framework provides the role model, the domain restriction concept and the PAR, and EMVCo runs registration programmes so that token service providers and BIN controllers are uniquely identifiable (technical framework). The specifications are royalty-free, but EMVCo does not test implementations — that is left to schemes, issuers and assessors.

PCI DSS and scope reduction

The PCI Security Standards Council's Tokenization Guidelines Information Supplement is the document to read before promising anyone a smaller audit (information supplement, PDF). Its core messages:

  • All parts of a tokenisation system — including de-tokenisation and PAN storage — remain in the cardholder data environment and stay in scope.
  • Components that hold only tokens can fall outside scope, but only if the PAN is not recoverable from the token, if they are segmented from anything that can de-tokenise, and if earlier card data has been securely deleted.
  • Tokenisation does not remove the obligation to maintain and validate PCI DSS compliance.

PCI DSS itself requires stored account data to be rendered unreadable, and tokenisation is one accepted route (PCI SSC document library).

Strong customer authentication in the EU

The EBA has also clarified that the token can function as a possession element for SCA purposes, precisely because it is bound to a trusted device with domain restrictions applied (EBA Q&A 2019_4827). Two consequences matter operationally: initiating a payment with a digitised card generally requires SCA unless an exemption applies, and the issuer remains responsible for SCA compliance even when the provision and verification of elements are outsourced to a wallet provider.

Outside the EU, SCA is not a general legal mandate, so tokenisation adoption in markets such as the US is driven mainly by fraud economics and scheme incentives rather than by a supervisory requirement.

Where adoption still breaks down

Provisioning friction

Adding a card is the weakest point in the funnel. It needs issuer involvement, often a step-up authentication, and it can fail for reasons the user cannot see — mismatched cardholder data, issuer rules, device checks. Drop-off at enrolment is a commercial problem, not a security one, and it is where most wallet programmes lose volume.

Portability and lock-in

Tokens held in a PSP vault are not portable. Moving to another provider can mean re-collecting PANs from customers, which is both a cost and a conversion risk. Network tokens largely avoid this because the mapping sits with the scheme or issuer, not the PSP.

Engineering and lifecycle cost

A production tokenisation programme needs provisioning APIs, device binding, cryptogram validation, webhook handling for lifecycle events, reconciliation of multiple tokens per account, and certification with each scheme. Card reissues, device replacements and suspended tokens all generate support tickets, and each failure looks to the customer like a broken card.

Uneven assurance

Not all tokens are equivalent. Token assurance levels and the strength of the underlying identification differ by wallet, issuer and use case, which makes it risky to treat "tokenised" as a single risk category in a fraud engine.

Card-on-file beyond wallets

Tokenising credentials stored by merchants and subscription billers is a larger and messier project than wallet provisioning. Merchant-initiated transactions and recurring billing depend on the token surviving renewals, and the SCA exemptions available for them differ by market.

Risks and costs

  • False scope reduction. Assuming tokens automatically remove systems from a PCI DSS assessment is the most common and most expensive mistake. The vault, keys and de-tokenisation paths remain in scope and are examined.
  • Provider concentration. Provisioning, lifecycle updates and payment authorisation can depend on a single token service provider. Outages, rate limits or programme policy changes affect payments directly.
  • Migration cost. PSP-vaulted tokens have no portable equivalent, so switching providers can require re-capturing card data from customers.
  • Operational failure modes. Expired, suspended or device-bound tokens fail in ways that are hard to diagnose, producing declines and support load.
  • Residual fraud exposure. A token that can initiate a payment is still worth stealing; domain restrictions reduce but do not eliminate misuse, particularly where keys or validation logic are compromised.
  • No protection against authorised push payment fraud. When the customer is manipulated into approving a payment, tokenisation is irrelevant — the transaction is correctly authorised.
  • Cost transparency. Token service, provisioning and certification costs are usually bundled into PSP or scheme pricing rather than itemised, which makes comparing providers on total cost of ownership harder than it looks.

Bottom line

Tokenisation is not a single control you switch on; it is a scoping and lifecycle discipline. The security gains are real and measurable at scheme level, and the standards work — EMVCo for the architecture, PCI DSS for the controls, PSD2/SCA in the EU for enrolment and initiation — is stable enough to build against.

For product and engineering teams, the deciding questions are practical ones: which party can de-tokenise, what happens to the token when the card is replaced or the device is lost, and whether the token portfolio can be moved without asking customers to re-enter their card details. Teams that answer those before go-live tend to get the approval-rate and fraud benefits. Teams that treat tokenisation as a checkbox inherit the support queue.

This article is for information and education only. It is not investment advice and does not take into account your personal situation. Read the full disclaimer.

Follow the shortlist

Following payments, banking and market-infrastructure change? Our global ETF and stock research watchlist is tracked daily. Premium members get the full list, the reasoning behind every entry and updates when entries change.

See premium access

Information and education only, not investment advice.

Related