Most involuntary churn happens because cards expire, get reissued, or get lost — not because customers wanted to leave. Two card-network features fix a large chunk of this before your dunning system ever needs to fire.
Almost every subscription business we audit has one of them on and the other off, or neither.
# What network tokens actually are
When a customer enters card 4242 4242 4242 4242 · 12/28, that PAN (primary account number) is what you traditionally tokenize and store. If the physical card is reissued — expired, lost, stolen, upgraded — your token is dead. The next charge fails.
A network token is a card credential issued by Visa, Mastercard, Amex, or Discover that survives reissuance. The card network updates the token behind the scenes when the underlying card changes. Your tokenized reference stays valid.
For subscription businesses, this means:
- Expiration-driven failures drop 60–80%.
- Reissuance-driven failures (lost/stolen replacement) drop 40–60%.
- Overall failure rate on saved cards drops 15–30% in most portfolios.
# How to enable it
Stripe, Adyen, and Braintree all support network tokens. On Stripe, it's on by default for eligible cards as of 2024, but only when you're using PaymentMethod (not raw Source or Card objects). If you're on legacy Stripe integrations, migrating is the single biggest churn win available.
// New charges use PaymentMethod — network tokens flow automatically.
const intent = await stripe.paymentIntents.create({
amount,
currency,
customer: customerId,
payment_method: paymentMethodId,
off_session: true,
confirm: true,
});Nothing else to do. Stripe surfaces payment_method_details.card.network_token.used: true on successful charges — track that percentage as a health metric.
# What account updater does
Even with network tokens, some card changes don't flow through the token layer — particularly customer-initiated updates and cards issued outside the token-eligible programs.
Account Updater (Visa Account Updater, Mastercard ABU, Amex CardRefresher) is a batch service that lets you submit stored PANs and get back updated PAN/expiry data when the issuer participates. It's a covering fire for the cases network tokens miss.
Most billing platforms expose this. Stripe's Card Account Updater runs automatically on saved cards. Adyen exposes AutoRescue with Account Updater as a component. Braintree has CreditCardVerification + updater.
Turn it on. There's essentially no reason not to.
# The measurement to add today
Track these three metrics as leading indicators of recovery health, before dunning even runs:
- % of active saved cards backed by a network token. Target: 70%+.
- % of expiring cards auto-updated in the last 90 days. Target: 50%+.
- Failure rate on network-tokenized charges vs. raw PAN charges. The gap is your ROI proof.
# Common gotchas
- Cross-processor migrations lose tokens. If you migrate from Stripe to Adyen (or vice versa), you generally cannot bring network tokens with you without a network-level provisioning agreement. Plan for a temporary failure spike.
- BIN sponsor limits. Some smaller issuers don't participate in Account Updater. Those customers still need dunning outreach for card changes.
- Regional coverage varies. Network tokens have excellent coverage in North America and Europe, patchy coverage in parts of LATAM and Africa. Don't expect uniform lift.
# The one-line takeaway
Turn on network tokens. Turn on account updater. Everything else in this blog is downstream of doing those two things right.