What Are Network Tokens? Higher Approvals for Stored Cards | MannyPay
Payments Glossary

What Are Network Tokens? Higher Approvals for Stored Cards

What are network tokens? See how Visa and Mastercard tokens keep stored cards current, cut failed renewals and differ from your gateway's own tokens.

On this page 6 sections
  1. What Are Network Tokens and Who Issues Them
  2. Network Tokens vs. Gateway Tokens: The Difference Most Merchants Miss
  3. How Network Tokens Stay Current When a Card Is Reissued
  4. What Network Tokenization Does for Approvals and Fraud
  5. Example: A Subscription Box Renewal That Doesn't Fail
  6. How to Turn on Network Tokenization With Your Gateway

What are network tokens? They are stand-in card numbers issued by the card networks themselves, such as Visa and Mastercard, through each network's own token service. You store and charge the token instead of the customer's real card number. The network and the card-issuing bank both know about the token, so it keeps working after the bank reissues the card with a new number or expiration date. Token transactions can also carry a one-time code that the issuer can verify. For subscription, membership and one-click-reorder businesses, the result is fewer renewals declined because of stale card data.

Most merchants hear "tokenization" and assume they already have it. Usually they have a different kind of token, one that protects card data but does nothing when a card changes. The difference decides whether next month's renewals go through.

What Are Network Tokens and Who Issues Them

Every card has a primary account number, or PAN, which is the long number printed on the front. A network token is a different number in the same format. The network creates it to stand in for the PAN in one specific setting.

The cardholder doesn't ask for the token. A "token requestor" does. For most small and midsize merchants, the requestor is the payment gateway or processor acting on their behalf, though large merchants can sometimes register directly. The network ties each token to its requestor, so a token stolen from your systems is worthless anywhere else.

The network and the issuing bank both keep the link between the token and the real card. That shared record makes network tokens useful for stored cards. When the bank changes something about the card, it can update the link, and you don't have to do anything.

Network Tokens vs. Gateway Tokens: The Difference Most Merchants Miss

If your checkout already "tokenizes cards," you are almost certainly using gateway tokens. A gateway token is a reference number created by your gateway's vault. Your website or billing software stores the token, and the gateway keeps the real card number locked away. This keeps raw card data out of your systems and shrinks your PCI DSS scope, as our explainer on how payment tokenization protects card data describes.

The limitation shows up when you charge the card. With only a gateway token, the gateway looks up the real PAN and sends that PAN to the network. The issuing bank sees an ordinary card-not-present charge on a card number. If that card expired last month, the charge declines.

Gateway tokenNetwork token
Created byYour gateway or processor's vaultThe card network's token service
Who can read itOnly that gatewayThe network and the issuing bank
What reaches the issuerThe real card numberThe token, often with a one-time cryptogram
Updates when the card is reissuedNoYes, when the issuer participates
Main jobKeep card data out of your systemsKeep stored cards current and trusted

Many setups use both. Your store keeps a gateway token, and your gateway maps it to a network token, which it sends when it charges the card. You rarely see the network token yourself.

Portability is the detail to check. Gateway tokens stay with the gateway that created them, so switching processors usually means a card-data migration between providers. Network tokens are bound to whoever requested them. If your gateway is the requestor, a new provider may need to request fresh tokens. Find out how that works before you need to switch.

How Network Tokens Stay Current When a Card Is Reissued

Cards change all the time. They expire. Banks replace them after a fraud alert or a data breach, and sometimes upgrade the cardholder to a new product. Each event can bring a new expiration date, a new card number or both, while the customer's account stays open and in good standing.

When a bank reissues a token-linked card, it updates the network's record so the existing token points to the new card details. Your stored token stays the same. The next renewal goes out on that token and reaches the new card. Networks also send lifecycle notices to the token requestor. A notice can refresh the expiration date your customer sees in their account. It can also flag a closed account so you stop retrying a card that will never work.

Account updater services reach a similar result by a different route. Your processor sends your stored card numbers to the network's updater program, usually in batches, and gets back any new details the issuer has reported. Updater is still worth having, and many processors charge for it under their own pricing. Network token updates happen at the network level when the issuer makes the change. They don't depend on a batch run finishing before your billing date.

Neither method covers every card, because coverage depends on which issuers participate. That's why many card-on-file merchants run both.

What Network Tokenization Does for Approvals and Fraud

Network tokenization raises approvals in two ways. The first is fewer declines from outdated card details, which is the reissue problem above. The second is trust. Token transactions can carry a cryptogram, a one-time code generated for that payment. The cryptogram shows the issuer that the charge came from the requestor the token belongs to. Requirements differ by transaction type. A purchase your customer starts, like a one-click checkout, typically includes one. A recurring charge you start on your own schedule may not, depending on network rules and your gateway's setup. Either way, an issuer that can trace where a card-not-present charge came from has one less reason to decline it.

Both Visa and Mastercard promote tokens as a way to raise authorization rates. Your own lift will depend on your issuer mix, the card types your customers carry, and how many of your stored cards actually have tokens. Measure your own results and don't borrow a headline figure. If good customers are being turned away for other reasons, our guide to why false declines happen covers the rest of the list.

On fraud, the clearest gain is breach protection. A thief who copies your vault gets tokens bound to your requestor, not usable card numbers. Network tokens won't stop card testing at checkout, though. Testers submit freshly stolen card numbers that have never been tokenized, so you still need velocity limits, CAPTCHA and your other checkout defenses.

Costs can fall too, mostly because fewer charges fail. Every declined retry costs you something, and networks can charge fees on certain declined and retried transactions, as our coverage of Mastercard's decline fee increase explains. Ask your processor whether any network fee or interchange difference applies to tokenized card-not-present charges, and whether your pricing passes it through to you. On flat-rate pricing, you probably won't see the difference on your statement.

Tokens don't change one rule. You still need the cardholder's consent to store the card and the correct stored-credential flags on every charge. Our guide to card-on-file rules for one-click reorders walks through both.

Example: A Subscription Box Renewal That Doesn't Fail

Picture a hypothetical subscriber whose bank replaces her card after a fraud alert. She updates her streaming services from memory and forgets your subscription box. Without a network token, your next charge declines, and she gets a "please update your card" email she may never open. With a network token, the issuer has already linked her new card to the token, and the renewal goes through.

To see the effect across a subscriber base, apply the same logic to a made-up shop. Every number below is illustrative. These numbers were chosen to make the arithmetic easy to follow. They are not network data or MannyPay data.

Assumptions: 100 subscribers have a card that changed since their last renewal. Your retries and reminder emails win back 4 of every 10 renewals that decline. In the second scenario, 80 of the 100 cards have network tokens, and issuers have pushed updates for 60 of those 80.

  • Gateway tokens only: All 100 renewals decline. Dunning saves 40, and 60 subscribers lapse.
  • Network tokens on most stored cards: The 60 updated cards renew on schedule. The other 40 decline, dunning saves 16, and 24 subscribers lapse.

That's 24 lost subscribers instead of 60 from the same group of changed cards. At $40 a month, the gap repeats every billing cycle, and each lapsed subscriber also takes their future months with them.

You control two inputs here. One is token coverage, meaning the share of your stored cards that have network tokens. The other is how quickly your gateway acts on lifecycle notices. Ask your provider to report both. For the declines that remain, a solid dunning management process does the rest.

How to Turn on Network Tokenization With Your Gateway

For most merchants, network tokenization is a setting or service your gateway or processor provides, not something you build. If you sell on a hosted cart, such as a Shopify store's payment setup, ask whoever processes your payments. If you run a custom online payments setup, ask your gateway directly. Cover these points:

  1. Brands covered. Confirm the gateway is a token requestor with Visa and Mastercard, and find out which other card brands it supports.
  2. Backfill. Ask whether it will request tokens for cards already in your vault or only for cards saved from now on. Most of the early benefit comes from backfill.
  3. Fallback. Make sure that when a token can't be issued, or an issuer doesn't support tokens, the charge falls back to the card number instead of failing.
  4. Lifecycle updates. Check that issuer updates reach your billing system, so new expiration dates and closed-account flags show up where your team works.
  5. Pricing. Get any per-token or per-update fees in writing. These are the processor's pricing, not a network rule. Ask too whether account updater should stay on alongside tokens.
  6. Exit terms. Learn what happens to your tokens and the underlying card data if you change providers.
  7. Reporting. Request recurring approval rates split by tokenized and untokenized cards.

Before you make any calls, pull your recent recurring-charge declines and sort them by reason code. Expired-card and invalid-account declines are the pool network tokens target, and that count tells you what this is worth to your business. If you're comparing payment gateways for recurring billing, MannyPay works with gateways including Authorize.net and NMI. You can request a free quote, and a MannyPay specialist will respond within one business day.

About the author

Adrian Reyes

Adrian Reyes is Senior Payments & Fintech Editor for Beyond the Swipe, covering credit card processing, merchant accounts, payment technology and processing fees.

This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.

Related reading