Skip to content

Card tokenization explained: gateway tokens vs network tokens, encryption, and PCI scope

Tokenization swaps a card number for a token. Compare gateway and network tokens, see how they cut PCI scope, and learn when tokens lift approval rates.

Tokenization replaces a card number with a token that is useless to a thief outside the system that issued it. Gateway tokens work only inside the gateway or processor that created them. Network tokens are issued by the card networks, work across processors, update when a card is reissued, and can lift authorization rates.

This guide compares the two token types, explains how tokenization differs from encryption, shows how tokens shrink PCI scope, and lists the steps to move to network tokens. It reflects card network, Apple, and PCI Security Standards Council pages as of November 2026.

Key takeaways

  • A token stands in for the card number. It maps back to the card only inside the tokenization system.
  • Gateway tokens are tied to one provider. Moving them means a vault migration.
  • Network tokens come from Visa, Mastercard, and other networks. They work across processors and update when the card changes.
  • Visa reported a 3% increase in approval rates and a 28% reduction in fraud rates for payments made with its tokens (Visa, 2022).
  • Tokens reduce PCI scope. They do not end PCI duties.

What is tokenization?

Tokenization is the practice of replacing sensitive card data with a substitute value called a token. Verifi, a Visa company, defines it as "a security measure that replaces sensitive account and card information with a non-sensitive token" (Verifi).

The card number is formally the primary account number, or PAN. The real PAN sits in a secure store, often called a vault. Your systems keep the token and use it wherever they used to use the card number: to charge a returning customer, to issue a refund, or to look up an order.

A stolen token is of little use. Verifi notes that a token "can only be traced back to the original account or card data with a master key" that is part of the tokenization system. Without access to that system, the token is just a string.

This article is about payment card tokenization. It is unrelated to tokenizing assets on a blockchain, which records ownership of an asset as a digital token.

What is the difference between gateway tokens and network tokens?

The difference is who issues the token and where it works.

A gateway token is created by your payment gateway or processor when a customer first pays. The provider stores the card in its vault and gives you a token. The token works only with that provider. If you change providers, the stored cards have to be exported from one vault and imported into another.

A network token is created by the card network, such as Visa or Mastercard, at the request of a merchant or its provider. The network keeps the link between the token and the card. Because the network sits above every processor, the token is designed to work across them. When the issuer replaces the card, the network updates the link and the token keeps working.

Raw card numberEncrypted numberGateway tokenNetwork token
What it isThe PAN itselfThe PAN, scrambled with a keyA stand-in issued by your gatewayA stand-in issued by the card network
Can it be turned back into the PAN?It is the PANYes, with the keyOnly inside the gateway's vaultOnly inside the network's token system
Portable across processorsYesOnly if the key moves tooNo, needs a vault migrationYes, by design
Updates when the card is reissuedNoNoOnly through an account updater or the customerYes, by the network
PCI scope impact for the merchantFull scope wherever it is stored or sentIn scope, with key management dutiesReduced scope for systems holding only tokensReduced scope for systems holding only tokens

Many merchants use both. The gateway token is the handle your systems store. Behind it, the provider holds a network token and sends that, not the PAN, to the network.

How is tokenization different from encryption?

Encryption transforms the card number with a key. The result looks random, but it still contains the number, and the right key reverses it. Anyone who gets both the encrypted data and the key gets the card.

A token contains nothing. It is a reference, and the mapping lives in a separate system. There is no key that turns a token into a card number outside that system.

The two work together. Card data is usually encrypted while it travels from the checkout to the provider and while it rests in the vault. Tokens are what the merchant's own systems hold afterward. Encryption protects data you must handle. Tokenization lets you avoid handling it.

How do tokens reduce PCI scope?

The Payment Card Industry Data Security Standard (PCI DSS) applies to systems that store, process, or transmit cardholder data. A system that holds only tokens does not hold cardholder data, so it carries a lighter compliance load. The PCI Security Standards Council publishes the standard.

The largest reduction comes from never touching the card number at all. If your provider collects the card in a hosted page or in hosted fields inside your page, the PAN goes straight to the provider and you receive a token. The Council's guidance on iframes and SAQ A explains when a merchant can use the shortest self-assessment questionnaire.

Three limits are worth knowing.

  • Scope shrinks. It does not vanish. You still validate compliance, and the page that loads the payment fields still matters.
  • Some data can never be stored, tokenized or not. After authorization, a merchant must not keep the card security code or full magnetic stripe data.
  • Your provider's vault is fully in scope. You are relying on its compliance, so ask for its attestation.

The PCI DSS compliance guide covers levels, questionnaires, and scope in detail. Confirm your own scope with your acquirer or a qualified assessor.

How do tokens work in wallets such as Apple Pay?

Device wallets are network tokenization at consumer scale. When a customer adds a card to Apple Pay, a device-specific Device Account Number is created and stored in the phone's Secure Element, according to Apple's platform security guide (Apple, 2024). Apple states that full card numbers are not stored on the device or on Apple Pay servers.

At checkout, the wallet pays with the device token, not the card number. Apple's guide says that neither Apple nor the device shares the full card number with the merchant. The merchant gets a credential it can authorize without ever seeing the PAN.

For the merchant, a wallet payment arrives already tokenized. There is no card number to protect, and the customer has approved the payment on the device.

Do network tokens improve authorization rates?

Visa's own numbers say yes. In an August 2022 release, Visa said its analysis "across more than 8,600 issuers and 800,000 merchants" showed that Visa tokens "have led to a 28 percent reduction in fraud rates and a 3 percent increase in approval rates" (Visa, August 24, 2022).

Two mechanisms explain the lift. First, the credential stays current. A reissued card does not turn into an expired-card decline, because the network updated the token. Second, issuers can trust a tokenized payment more, since a token is typically limited to one merchant or device and travels with a one-time code.

Results vary by issuer and country, so measure your own approval rate for tokenized and non-tokenized payments. Why card payments get declined covers the other causes of declines.

Account updater services solve part of the same problem without tokens. Visa Account Updater and Mastercard's Automatic Billing Updater supply new card numbers and expiry dates for stored cards. Subscription businesses often use both, as recurring card payments explains.

How do you migrate to network tokens?

Most merchants get network tokens through their gateway or processor. The work is mostly configuration and testing.

  1. Ask your provider what it supports. Confirm which card networks it tokenizes with and whether tokens are requested for you automatically.
  2. Decide what your systems store. Keep storing the provider's token as your handle, and let the provider manage the network token behind it.
  3. Provision tokens for cards already on file. Providers can request network tokens in bulk for stored cards. Expect some cards to be ineligible.
  4. Keep a fallback. If a tokenized authorization fails for a technical reason, your provider should be able to retry with the card number.
  5. Handle lifecycle updates. Subscribe to your provider's notifications for updated, suspended, and deleted tokens, and reflect them in your records.
  6. Check your authentication flow. Tokens and cardholder authentication work together. 3D Secure 2 explained covers the authentication step.
  7. Measure the result. Compare approval rate, expired-card declines, and fraud rate before and after, by issuer.

If you plan to change processors, ask both providers how stored cards move. Network tokens ease the switch, but each provider must still request its own tokens for your merchant account.

Sources

What to do next

Ask your provider whether your stored cards already have network tokens, then compare approval rates for tokenized and non-tokenized payments. For the full payment path, read how card payments work. BlindPay does not issue cards. It accepts card payments as one payin method through a card frame that returns a single-use token, so card data never touches your servers or BlindPay's, per the card payins docs.

This article is general information, not legal, tax, or financial advice.

FAQ

One API.
Multiple payment rails.

Blind Pay, Inc. (“BlindPay”) is a United States-based financial technology and payments infrastructure company, incorporated in the State of Delaware on May 2, 2024. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000277566153. BlindPay is not a state-licensed money transmitter and does not, in its own capacity, engage in regulated money transmission services. All such regulated activities are conducted exclusively through, and under the licenses of, duly authorized financial institution partners. BlindPay's role is limited to providing financial technology, virtual account management, payment processing, and related payments infrastructure services that facilitate payment flows and account functionalities. These services are provided in coordination with its licensed partners and in compliance with applicable federal MSB requirements and relevant state regulatory frameworks.

Blind Pay, LLC (“BlindPay”) is a Delaware limited liability company formed on June 24, 2025. BlindPay is duly registered as a Money Services Business (“MSB”) with the Financial Crimes Enforcement Network (“FinCEN”) under registration number 31000318334247 and is listed in the Nationwide Multistate Licensing System (“NMLS”) under NMLS ID #2745309.

BLIND PAY SOCIEDADE PRESTADORA DE SERVIÇOS DE ATIVOS VIRTUAIS LTDA. (“BlindPay”) is a Virtual Asset Service Provider (“VASP”) operating in Brazil. The company is presently completing the regulatory adaptation process required of Virtual Asset Service Provider Companies (SPSAV) under Central Bank of Brazil Resolution No. 520/2025, and remains subject to the transitional regime set forth in Article 88 of that Resolution. Registered address: Avenida Princesa Isabel, nº 15, Sala 1405, Edifício Martinho de Freitas, Centro, Vitória/ES, 29010-361.

BlindPay is a stablecoin API that enables individuals and businesses to move money worldwide.