Payments

What Is Payment Tokenization And How Does It Work?

November 18, 2026 11 min read
This blog explains how payment tokenisation works, how network tokens differ from PCI tokens, and what tokenisation means for PCI DSS scope, authorisation rates, and fraud risk. It also explores how Apple Pay, Google Pay, and Click to Pay use tokens, and what businesses should consider when choosing a tokenisation solution.
post thumbnail

Payment tokenisation replaces a primary account number (PAN), or the 16-digit number on a card, with a non-sensitive substitute called a token. This allows businesses to store and reuse payment credentials without retaining the underlying card data.

According to Visa’s third-quarter 2026 earnings call, tokenised transactions accounted for nearly 60 per cent of its global e-commerce transactions.

Key takeaways

  • Payment tokenisation replaces a card’s PAN with a token, allowing merchant systems to store and reuse payment credentials without retaining the real card data.
  • PCI tokens are created by PCI DSS-certified payment processors, while network tokens are issued by card networks like Visa and Mastercard.
  • Visa reported a 4.6 per cent increase in card-not-present authorisation rates and a 30 per cent reduction in fraud for tokenised transactions.
  • Tokenisation can reduce the systems and processes within PCI DSS scope, but it doesn’t prevent non-fraud chargebacks, friendly fraud, or declines caused by insufficient funds.
  • Mastercard has announced plans to introduce fees for certain non-tokenised card-on-file transactions in Europe from 1 January 2027. Merchants should check the applicable markets, transaction types, and fee arrangements when assessing the business case for network tokenisation.

What is payment tokenisation?

Payment tokenisation replaces a card’s PAN with a substitute value known as a token. Unlike encryption, tokenisation doesn’t scramble the original card number. It replaces it with a separate value generated by a tokenisation system. The mapping between a token and its PAN sits in a secure token vault run by either the payment provider or the card network’s token service provider (TSP), so a stolen token is of little use on its own.

Stored card numbers are valuable targets for attackers, so protecting them creates significant security and compliance responsibilities for businesses. At the same time, customers expect to make repeat purchases without re-entering their card details. 

Merchants therefore need a way to retain a reusable payment credential without keeping the underlying card number. Tokenisation addresses this need by enabling merchants to store and reuse a payment credential without retaining the underlying sensitive information.

Token vs PAN

A token and a card number typically have the same format to ensure compatibility with payment systems. For instance, a PAN of 4000 0012 3456 7899 might be replaced by a token of 4382 0087 6543 2105.

However, the token is a separate value, and not an encrypted or altered version of the PAN. So, someone who sees the token can’t work out the PAN from it.

Payment tokenisation vs data tokenisation

Tokenisation protects different types of sensitive information. In data tokenisation, a sensitive value, such as a national identifier or account number, is replaced with a substitute value, while the original is protected in a secure vault.

Payment tokenisation applies the same principle to payment credentials, particularly card PANs. It operates within the payment ecosystem and is subject to relevant technical standards, card-network requirements, and security rules.

Tokenisation vs encryption

Encryption transforms data into ciphertext using a cryptographic algorithm and key. The original data can be recovered by decrypting the ciphertext with the appropriate key. Tokenisation replaces the original value with a substitute. In a conventional vaulted system, the relationship between the token and the original value is stored separately and can be retrieved through an authorised tokenisation process.

Tokenisation and PCI DSS compliance

The Payment Card Industry Data Security Standard (PCI DSS) sets security requirements for entities that store, process or transmit payment account data, as well as systems that can affect the security of the cardholder data environment.

Tokenisation can reduce the number of systems that handle or store the primary account number (PAN), potentially reducing the scope of a merchant’s PCI DSS assessment. However, it does not automatically remove the merchant from scope or eliminate its validation obligations. The outcome depends on how the tokenisation solution is designed, where the PAN is handled, and whether the merchant’s systems can access or recover it.

How does payment tokenisation work?

A payment token is created during an initial enrolment or payment process, and can then be stored and reused for subsequent transactions.

  1. The customer enters their payment details. This usually happens through a payment provider’s hosted fields, hosted checkout page, or SDK, so the PAN goes directly to the provider without passing through the merchant’s own servers.
  2. The token requestor sends a token request. The requestor sends the necessary card and requestor information to the relevant TSP.
  3. The card and request are verified. The TSP coordinates the identification and verification (ID&V) process, which may involve the issuer, to establish that the card and token requestor are eligible for tokenisation.
  4. The token is issued. The TSP generates the token and makes it available to the authorised requestor or device. The token may have restrictions governing where and how it can be used.
  5. The merchant or payment provider stores the token. The token can be retained for future payments without storing the original PAN in the merchant’s systems.
  6. The token is used for subsequent payments. For applicable token transactions, the payment request includes a transaction-specific cryptogram or other security data. The network and issuer process the tokenised transaction under the relevant scheme rules, and the issuer makes the authorisation decision.

The token lifecycle

After a token is provisioned to the relevant environment, such as a merchant’s payment system, a mobile wallet, or another authorised device, its status can change throughout its lifecycle. When a card is replaced, reissued, or renewed, the TSP may update or provision the associated token, depending on the issuer’s support and the applicable scheme rules.

Types of tokens

The two main types of tokens are network tokens and PCI tokens. Network tokens are issued and managed by a card network. It is recognised by the issuer and can be subject to usage controls, such as restrictions to a merchant or device.

PCI tokens are also referred to as vault or gateway tokens. They are substitute credentials generated by a PCI DSS-certified payment processor to protect stored card data. They allow a merchant to reference a payment credential without storing the PAN directly.

A payment provider can store or manage a network token on behalf of a merchant, while also providing a gateway-level reference through which the merchant accesses that credential.

Benefits of payment tokenisation

#1 Higher approval rates

According to Visa, card-not-present transactions using network tokens achieved a 4.6 per cent increase in authorisation rates compared with transactions using card numbers.

Network tokens support higher approval rates because issuers can recognise the tokenised credential and use associated information, including transaction-specific cryptographic data, when assessing a payment. Additionally, token lifecycle management helps keep stored credentials current.

#2 Lower fraud

Visa reported a 30 per cent lower fraud rate for token-based transactions compared with transactions using PANs.

Depending on the implementation, domain restrictions can limit where a token is used, while transaction-specific cryptograms provide additional security for eligible payments, thereby reducing the risk associated with compromised payment credentials.

#3 Fewer declines from expired and reissued cards

When a customer receives a replacement card or their existing card expires, stored payment details can become outdated. This can cause recurring payments and card-on-file transactions to fail.

Network token lifecycle management helps address this problem by updating or maintaining the payment credential when the underlying card changes. This reduces the need for customers to enter their card details again, and can prevent some avoidable declines.

For more on the reasons card payments fail, read our guide.

#4 Recurring billing and one-click checkout

Tokenisation allows merchants to retain a reusable payment credential without storing the original PAN in their systems. This supports card-on-file transactions, including subscriptions, instalments, and repeat purchases.

Customers can make subsequent payments without entering their card details each time. Network tokens can make these transactions more resilient by supporting credential lifecycle updates and applying additional security controls.

For businesses that rely on subscriptions or repeat billing, this can reduce payment interruptions and make checkout more convenient.

#5 Portability and less vendor lock-in

Gateway tokens are generally managed within the payment provider’s tokenisation environment. If a merchant changes providers, transferring those credentials may not be possible, potentially requiring customers to re-enter their card details.

Network tokens are issued through a card network’s token service provider rather than being generated solely within a gateway’s vault. This can provide more flexibility when a merchant changes payment providers.

The token requestor arrangement, scheme rules, and the providers involved determine whether tokens can be transferred, re-provisioned, or continued under a new processing relationship. Merchants should confirm these arrangements with their existing and prospective providers before assuming that stored credentials can move between them.

#6 Lower breach impact and PCI burden

Tokenisation reduces the need for merchant systems to store or handle actual card numbers. If a system holding only tokens is compromised, the attacker may have less access to sensitive card data than if the system stored PANs directly.

It can also reduce PCI DSS scope by limiting the number of systems that store, process, or transmit PANs. The extent of the reduction depends on the tokenisation architecture, the provider’s responsibilities, and whether merchant systems can access or recover the original card data.

Tokenisation does not eliminate breach risk or PCI DSS obligations. Merchants must still protect the systems involved in payment processing, manage third-party providers, and complete the appropriate compliance validation.

Tokenisation in digital wallets and Click to Pay

Digital wallets and Click to Pay both use technologies that can support tokenised card payments, but they differ in how payment credentials are provisioned, where they are used, and how customers authenticate.

How Apple Pay and Google Pay use tokens

When a customer adds a card to Apple Pay, a Device Account Number (DAN) is created and provisioned for that device. According to Apple, the DAN is encrypted and stored in the device’s Secure Element, a dedicated security chip. It replaces the card number during supported payments.

Google Pay also supports tokenised device payments, but uses two authentication methods:

  • PAN_ONLY: Refers to card details stored in the customer’s Google Account
  • CRYPTOGRAM_3DS: Returns a device token associated with a card stored on the Google Wallet app, together with a 3D Secure cryptogram generated on the device.

According to Google, CRYPTOGRAM_3DS is supported on Android devices and Android mobile web or WebViews, while desktop web and iOS use PAN_ONLY.

What is Click to Pay?

Click to Pay is a consumer-facing online checkout experience based on EMV Secure Remote Commerce (SRC), a standard developed by EMVCo. It provides a consistent way for customers to use enrolled payment cards across participating merchants, devices, and digital channels.

A customer enrols an eligible card through a participating issuer or Click to Pay solution. At a participating checkout, the customer can select the payment card associated with their profile and complete the payment without manually entering the full card number.

Click to Pay can work with network tokenisation and transaction-specific security data, but it is not itself a token or a particular authentication method. Depending on the implementation and transaction, the checkout may use a one-time passcode, a passkey, 3D Secure, or another supported verification method.

Read more about Click to Pay and how it works.

Card networks are expanding tokenisation and modern checkout services across e-commerce.

In June 2026, Mastercard reported that:

  • Click to Pay was available in 32 European markets
  • Enrolments had more than doubled over the previous year
  • Returning customers accounted for more than 70% of Click to Pay checkouts
  • Three in five Mastercard e-commerce transactions in Europe were tokenised.

Mastercard has also set a target of reaching 100% e-commerce tokenisation in Europe by 2030.

Tokenisation, card declines, and chargebacks

Tokenisation can help prevent some payment declines and reduce certain types of fraud, but its impact depends on the reason for the decline or dispute.

Declines

Network tokens can help address credential-related problems, particularly when a stored card expires or is replaced. Lifecycle management may allow the token to remain usable or be updated when the underlying card changes, reducing some avoidable declines in recurring and card-on-file payments.

Tokenisation can also provide issuers with additional information to assess a transaction. However, it cannot resolve every reason for a decline. Insufficient funds, issuer risk decisions, account restrictions and other payment issues can still result in a declined transaction.

Chargebacks

Tokenisation can reduce exposure to stolen card numbers and help prevent some unauthorised transactions. However, a chargeback is also assessed based on its reason code, the evidence submitted, and the applicable card-network rules.

Liability protection may apply to eligible fraud disputes when a transaction meets the requirements of a relevant authentication or tokenised-payment programme. For example, certain Google Pay Android device-token transactions can qualify for liability shift under Visa and Mastercard rules. This protection is conditional and shouldn’t be confused with a universal liability shift for all wallet or tokenised transactions.

Tokenisation does not resolve non-fraud disputes, such as goods not received or goods not as described. Merchants still need order records, delivery evidence, clear refund policies, and effective customer support.

See our guide to how chargebacks work for more on reason codes, representment evidence, and response deadlines, and how merchants can respond to these disputes.

Friendly fraud

Tokenisation does not prevent first-party misuse, sometimes called friendly fraud. This occurs when a cardholder or an authorised user makes a purchase and later disputes the transaction, for example by claiming they don’t recognise it.

The token may help establish that a valid payment credential was used, but it does not by itself prove who made the purchase or whether the cardholder received the goods or services.

Merchants should retain appropriate transaction, authentication, account-access and fulfilment records.

What tokenisation does not do?

  • It does not prevent non-fraud chargebacks, such as disputes over goods not received or services not provided.
  • It does not replace 3D Secure or other applicable authentication requirements.
  • It does not remove PCI DSS validation obligations.
  • It does not prevent declines caused by insufficient funds, account restrictions, or other issuer-side decisions.
  • It does not guarantee liability shift for every tokenised or digital-wallet transaction.

Choosing a tokenisation solution

The right solution depends on where payment credentials are captured, how many providers and acquirers a business uses, and which card networks it accepts. A merchant processing Visa and Mastercard through one acquirer has different requirements from a marketplace operating across several providers and regions.

Before choosing a tokenisation provider, merchants should assess the following:

  • Scheme coverage: Which networks support tokenisation through the provider? Check availability of Visa, Mastercard, American Express, and Discover in the markets where the business operates.
  • Vault portability: Can stored credentials be transferred or re-provisioned if the merchant changes providers? Understand what can be migrated and what requires customer re-enrollment.
  • PCI DSS scope: Does the provider hold a current Attestation of Compliance (AOC)? Which merchant systems can be excluded from scope, and what responsibilities remain?
  • Lifecycle management: Does the solution support network-token lifecycle updates and account updater services?
  • Authentication: How does the provider support 3D Secure, wallet authentication, and transaction-specific cryptograms?
  • Multi-acquirer support: Can the same tokenisation arrangement support the merchant’s different acquirers and processing routes?
  • PAN fallback: What happens when a card or issuer cannot be tokenised? Is there an alternative payment route?
  • Token requestor identity: Who controls the token requestor relationship and associated identifiers, the merchant, the PSP or another provider?
  • Reporting: Can the merchant compare token provisioning, token coverage, authorisation rates, declines, and fraud outcomes against non-tokenised payments?

Migrating existing card-on-file

Cards stored before tokenisation was introduced do not automatically become network tokens. Merchants generally need to submit eligible stored credentials for token provisioning through their payment provider or token requestor arrangement.

Older records may contain expired card details, which can prevent a token request from succeeding. Some network services can help address this problem by obtaining updated expiry information during token provisioning.

A global financial infrastructure provider like Unlimit simplifies business operations across regions by bringing card tokenisation and over 1,000 alternative payment methods into one payment integration. In October 2025, Unlimit achieved the Mastercard and Visa Token Service Provider certification in India, allowing it to manage the full token lifecycle for merchants.

FAQ

What is a token vault?

A token vault is a secure system that stores the mapping between a token and the original PAN. When a payment provider uses vaulted tokenisation, it stores this mapping and retrieves the corresponding payment details when an authorised transaction requires them. Some tokenisation systems use vaultless approaches, generating or validating tokens through cryptographic processes rather than relying on a conventional stored mapping for every token.

What is the difference between a network token and a PCI (gateway) token?

A network token is issued through a card network’s tokenisation service and can be recognised within the network’s payment infrastructure during authorisation. A gateway token is a substitute credential generated by a payment gateway or provider’s vault to represent a stored card. A gateway token can reduce the merchant’s exposure to PAN data, while a network token can provide additional controls and benefits for eligible card transactions. Some payment arrangements use both, but the exact architecture depends on the provider and integration.

Is tokenisation the same as encryption?

Encryption transforms data into ciphertext that can be recovered using the appropriate cryptographic key. Tokenisation replaces the original data with a substitute value that is resolved through a tokenisation system or, in some implementations, a cryptographic process.

Does tokenisation make a business PCI compliant?

Tokenisation can reduce the number of systems that handle or store PANs, and may reduce PCI DSS scope when implemented correctly. However, merchants still need to meet the requirements that apply to their environment. The effect on scope depends on how card data is captured, stored, transmitted and accessed. Merchants should confirm their obligations with their acquirer or qualified security assessor.

What happens to a token when a card expires or is replaced?

A network token may be updated through the card network’s lifecycle management services when the underlying card is renewed, replaced, or changed. This can help recurring payments and stored credentials continue working, provided the issuer, network, and token requestor support the relevant updates. A gateway token generally continues to represent the stored credential in the provider’s vault. Keeping the underlying card details current may depend on account updater services or other provider-supported processes.

Join Unlimit newsletter and get the highlights of upcoming events, fresh articles & special offers
You can unsubscribe in any time.
Read our Privacy Notice.