Network Tokens for Online Stores: Fewer Declines on Saved Cards
Learn how network tokenization in ecommerce keeps saved cards working after reissues, can cut declines, and how to check if your processor uses it.
Photo: Pixabay
On this page 7 sections
- Gateway Tokens vs. Network Tokens: The Difference That Matters
- Why Saved Cards Fail After a Customer Gets a New Card
- Approval Rate and Fee Benefits of Network Tokenization in Ecommerce
- Card-on-File Tokenization and Consent Rules for Repeat Buyers
- Questions to Ask Your Processor About Token Support
- Moving Saved Cards When You Switch Processors
- Next Steps for Your Store
Key takeaways
- Gateway tokens protect stored card numbers. Network tokens also update themselves when a customer's bank reissues a card.
- Network tokens can raise approval rates on saved cards and repeat charges, and some programs may lower fraud costs or fees. Confirm the current terms with your processor.
- Card-on-file transactions require clear customer consent and correct tagging, whether or not you use tokens.
- Ask about token portability before you switch processors so saved cards and subscriptions don't break.
Saved cards keep repeat customers coming back to an online store. They also break quietly. A customer's bank reissues a card after a data breach, the old number stops working, and the next reorder or subscription renewal declines. This guide explains how network tokenization in ecommerce keeps saved cards working after reissues, where it can help with approvals, fraud and fees, what consent rules apply to stored cards, and how to find out whether your processor actually uses network tokens.
Gateway Tokens vs. Network Tokens: The Difference That Matters
Most online stores already use tokens, but not always the kind this article is about. When a customer saves a card at checkout, your platform or gateway usually swaps the real card number for a token, so your systems never store the card itself.
There are two common types.
Gateway (Processor) Tokens
Your gateway or processor creates a gateway token. It points to the real card number, which sits in the provider's secure vault. When you charge the saved card, the gateway looks up the real number and sends it to the card network.
Gateway tokens are good for data security. However, they are only as current as the card number behind them. If the bank reissues the card, the token still points to the old, dead number.
Network Tokens
A network token is issued by the card network itself, such as Visa or Mastercard, working with the customer's bank. It replaces the card number across the whole transaction, not only inside your gateway. Network tokens are usually tied to a specific merchant, so a stolen token is far less useful to a fraudster. Each transaction also typically carries a one-time cryptogram that proves the request is legitimate.
The most important difference for merchants is lifecycle management. When the bank reissues a card with a new number or expiration date, the network can update the token automatically. Your saved card keeps working without the customer doing anything.
| Feature | Raw Card Number | Gateway Token | Network Token |
|---|---|---|---|
| Who creates it | Card issuer | Your gateway/processor | Card network with issuer |
| Hides card data from your systems | No | Yes | Yes |
| Updates after card reissue | No | Only with a separate updater service | Generally yes, automatically |
| Useful to a thief if stolen | Yes | Limited | Very limited (merchant-bound) |
| Portable between processors | Yes, if stored securely | Depends on provider | Depends on setup; often complex |
Many stores use both types. The gateway token is what your platform stores, and behind it the gateway holds a network token instead of the raw number.
Why Saved Cards Fail After a Customer Gets a New Card
Card numbers change more often than most merchants expect. Common causes include:
- Expiration. Every card eventually expires and gets a new date, and often a new security code.
- Fraud or breach reissues. Banks reissue cards in bulk after a compromise, even when the customer did nothing wrong.
- Lost or stolen cards. The customer reports the card and gets a new number.
- Product changes. The bank upgrades or converts the account to a different card product.
When the stored number is out of date, the charge declines. In a saved card checkout, the customer sees an error and may re-enter a card or leave. In a recurring or subscription charge, the customer may not see anything at all. The renewal fails in the background, and you lose revenue you thought you had.
These failures are a big reason good customers get turned away. Our guide to false declines and why good customers' cards fail at checkout covers the other common causes.
Account Updater vs. Network Tokens
Before network tokens became common, the main fix was an account updater service. Your processor periodically asks the networks for new card details and refreshes your stored cards. Updaters still help, but they typically work in batches, may cost extra per update, and depend on the issuer taking part. Network tokens update continuously as part of the token itself. Many processors offer both, and the two can work together.
Approval Rate and Fee Benefits of Network Tokenization in Ecommerce
Network tokens are not a cure-all, but they address several problems that affect repeat buyers.
Higher Approvals on Stored Cards
Tokens that stay current mean fewer declines for expired or replaced cards. Issuers may also trust tokenized transactions more, because the merchant-bound token and cryptogram make it harder for a fraudster to reuse the credentials. That can mean fewer good orders declined as suspicious.
Illustrative example: A small online coffee roaster sells monthly bean subscriptions to a few hundred customers. After a bank reissues cards in a region, a batch of renewals fails on stale card numbers. With network tokens, many of those cards would update before the renewal date, and the charges would go through as usual. The roaster would spend less time emailing customers to update payment details. (This scenario is hypothetical; your results depend on your customers, card mix and processor.)
Lower Fraud Exposure
A stolen network token is generally useless outside the merchant it was issued for, and the cryptogram changes with each transaction. If your systems or a vendor's are breached, tokenized credentials carry less value to attackers than raw card numbers. Tokens may also help reduce your PCI DSS scope. They do not remove your compliance obligations, so confirm your requirements with your processor or a qualified assessor.
Possible Fee and Pricing Advantages
Card networks have at times offered incentives or different pricing for tokenized card-not-present transactions. Fewer fraud-related chargebacks and fewer retried declines can also lower your total costs. These programs change, and whether you see any benefit depends on your processor and your pricing model.
On flat-rate pricing, you usually won't see network-level savings at all. On interchange-plus, cost changes are easier to spot on your statement. Our article on interchange-plus vs. flat-rate ecommerce pricing explains when switching makes sense. Ask your processor which incentives currently apply and whether they pass them through to you.
Faster One-Click Checkout With Saved Cards
One-click checkout with saved cards only works if the saved card works. Network tokens keep stored credentials current, which protects the fastest checkout path you offer repeat customers.
Card-on-File Tokenization and Consent Rules for Repeat Buyers
Card-on-file tokenization changes how a card is stored. It does not change your responsibility to get permission to store and charge it. Card networks have rules for stored credentials, and your processor passes those rules on through your merchant agreement.
In general terms, those rules expect you to:
- Get clear consent when storing the card. Tell the customer you're saving the card, what it will be used for (future one-off purchases, a subscription, installment payments), and how they can remove it.
- Disclose the terms of recurring charges. For subscriptions, show the amount, frequency, and how to cancel before the customer agrees.
- Flag transactions correctly. The first transaction that stores the card, later purchases the customer starts, and charges you start on your own (like renewals) are tagged differently in the payment message. Your gateway usually handles this, but only if your platform is set up correctly.
- Notify customers of changes. If the price, billing date or terms change, tell customers before charging the stored card.
- Honor removal and cancellation requests promptly. Delete stored cards and stop charges when customers ask.
Subscription sellers also face state automatic renewal laws, which add their own disclosure and cancellation requirements. See our automatic renewal laws compliance map for subscriptions for an overview.
Network rules and state laws change. This section is general information, not legal advice. Confirm current requirements with your processor and a qualified attorney.
Questions to Ask Your Processor About Token Support
Many providers say they "tokenize cards," and that usually means gateway tokens. Use these questions to find out what your setup actually does:
- Do you request network tokens for saved cards, or only gateway tokens?
- Which card networks' token services are you enrolled in? Visa's token service and Mastercard's equivalent are the ones merchants ask about most. Ask about American Express and Discover too.
- Is network tokenization on by default, or do I have to enable it? Some providers make it an add-on, or turn it on only for certain plans or platforms.
- Does it cost extra? Ask about any per-token or per-update fees.
- Do you also run an account updater service, and how does it work with tokens?
- Does my ecommerce platform or plugin support it? Shopify, WooCommerce, BigCommerce and other carts connect to gateways differently. Confirm the token path works with your exact setup.
- Are my existing saved cards converted, or only new ones?
- Can you show me reporting on token-based approvals and updates?
- Are any network incentives for tokenized transactions passed through to me?
- If I leave, can my stored card data be exported?
Get answers in writing where possible. If your current provider can't answer these clearly, that alone is worth noting. Our broader ecommerce payment processing setup guide covers other gateway features worth checking.
Moving Saved Cards When You Switch Processors
Saved cards are often the hardest thing to move when you change providers. Plan for them before you sign anything new.
What Usually Moves and What Doesn't
- Gateway tokens generally don't work at a new provider, because they only mean something inside the old provider's vault.
- The underlying card data can often be moved through a secure, PCI-compliant transfer between providers. Your old provider sends encrypted card data directly to the new one, which issues fresh tokens.
- Network tokens are tied to the party that requested them. Depending on the setup, the new provider may need to request new network tokens using the transferred card data.
A Migration Checklist
- Read your current agreement for data export terms and any fees.
- Ask the old provider to confirm in writing that it will release stored card data to a PCI-compliant recipient.
- Confirm the new provider can receive the data and will request network tokens for the migrated cards.
- Map tokens to customer records. Your platform must link each new token to the right customer and subscription.
- Test before you switch. Run a small batch of renewals or reorders before moving everyone.
- Keep the old account open briefly to handle refunds, chargebacks and stragglers.
- Have a fallback. Prepare a simple email asking customers to re-enter cards if some records don't transfer cleanly.
Never ask customers to send card numbers by email or phone to rebuild your records. That creates the exact security risk tokenization is meant to remove.
Next Steps for Your Store
Start by finding out which kind of tokens protect your saved cards today. Then decide whether network tokens, an account updater, or both would reduce failed reorders and renewals. If you sell subscriptions, review your consent language at the same time.
If you're comparing providers, MannyPay offers online payment processing for ecommerce stores and payment gateways, with integrations for platforms including Shopify, WooCommerce and BigCommerce, and options for low-risk ecommerce businesses. Request a free quote, and a MannyPay specialist will respond within one business day to review your current setup and answer your token questions.
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.
