Tokenization and digital wallets: payment tokens and enrollment

What Tokenization Replaces

First, let's be precise about the problem tokenization solves. A merchant needs the card number for two things: collecting this payment, and being able to collect again next period. Both require it to store the card number: and storing the number is itself the risk.

Tokenization works like this: instead of the card number, the merchant stores a token. Within the merchant's and processor's systems, that token can be used to charge, but the merchant can't reverse it back to the card number: even if the token leaks, whoever has it can't use it anywhere else.

Network Tokens vs. Processor Tokens

Tokens aren't all the same: the issuer determines how capable they are:

“Updates with the card” on the right is the most practical takeaway below.

A processor token is like “I keep the card number in my safe and hand you a key that opens only this locker.” A network token goes further: it's issued by the card network, so the network knows which card the token corresponds to and can proactively push new card details to merchants when the card changes.

The Card in Your Phone Isn't That Card

When you add a card to a digital wallet like Apple Pay or Google Pay, what the wallet stores isn't your card number: it's a device account number:

• When you add the card, the card network generates an alternate account number for that device (DPAN);
• The real card number (FPAN) lives only at the card network and the issuing side: it's never sent to merchants;
• When you pay, the merchant receives the device account number and a one-time dynamic cryptogram;
• So even if the transaction data is intercepted, what's captured isn't your card number.

This answers a common question: the card number inside a wallet isn't the number you see outside it. That's not a bug: it's the design. The whole point of a wallet is to keep the real card number out of the transaction chain. For how the issuing side integrates with wallets, Stripe Issuing's digital wallet documentation is a good reference.

The Hidden Benefit of Network Tokens

The most practical capability of a network token is card number updating:

1. Your card is replaced due to expiry, a new card, or risk-control reasons, so the number and expiry date change;
2. If the merchant holds a network token, the card network can push the updated details to it;
3. Without any action from you, the next cycle's charge already uses the new details;
4. If the merchant stored the card number itself, it keeps using the old one until the charge fails.

This is why after a card replacement, some subscriptions sail through without a hitch while others start failing immediately: the difference isn't the card, it's whether the merchant holds a token or the raw number. That's also tokenization's most tangible value in scenarios with recurring charges.

Two Side Effects of Tokens

Tokens aren't a cure-all; they come with a few costs you should know about:

Remember the second one especially: a token rescues you from “new card” but not from “card closed.”

Tokenization Changes Storage, Not Risk Itself

Let's boil the concepts down into a few actionable judgments:

• Tokenization addresses the consequences of a leak at the storage stage; it doesn't fix card numbers being intercepted during entry;
• It also doesn't change how merchants judge card category, MCC, or transaction type: the same card sits behind the token, and what would be declined still gets declined;
• For cardholders, the most tangible benefit of tokenization is that some subscriptions renew automatically after a card replacement;
• For scenarios with recurring charges, you still need to check that each binding is still valid after a card change.

Cards on this platform can be added to mainstream digital wallets (subject to support from the issuer and the wallet provider), and the card numbers are valid long-term, making them suitable for recurring billing. Let's be clear about the boundary: whether a merchant uses network tokens and whether they auto-update on card replacement depends on how the merchant and its processor implement it: it's neither in our hands nor something we promise. Actively checking every binding after a card change is the only reliable approach.

Once tokenization is understood, only one practical task remains: going through each binding after a card change. Card issuance and replacement are both handled in the Help Center.

FAQ

Further reading