The card on file just expired. Update it before the customer notices.
Card credentials change constantly — expirations, replacements, fraud reissues, network-wide reissues after a breach. For merchants running subscriptions or recurring billing, a single outdated card means a failed transaction, a churned customer, and a support ticket. Automatic Account Updater solves it silently in the background.
The problem is bigger than most realize
Up to 33% of payment credentials change annually. For merchants with recurring revenue, that is not a minor inconvenience — it is a direct hit to cash flow and retention. Every failed payment creates friction: support tickets, manual outreach, and the real risk that the customer cancels rather than updates.
The cost shows up in three places that finance teams rarely connect.
Hard revenue loss. A subscription that fails on a card update and never gets recovered is recurring revenue gone. Industry data routinely puts involuntary churn from card failures at 20-40% of total churn — half of which is recoverable.
Support burden. Every failed transaction triggers an email cycle, a customer phone call, and a billing-team queue item. At scale this is a real headcount cost.
Brand damage. "Your card on file failed" is the worst-timed message a customer can receive. They are not actively shopping; you are reminding them they are paying you. That is a churn risk every time.
A correctly running account updater removes all three at once.
How automatic account updater works
The card networks run a service that lets enrolled merchants ask: "this card on file is stale — has the issuer reissued it?" If the answer is yes, the network returns the new credential directly from the issuer, the merchant updates their vault, and the next recurring charge runs against current data.
Each major network operates its own variant of this service.
- Visa Account Updater (VAU) — the Visa-network service that returns updated credentials for Visa cards reissued by the customer's issuing bank.
- Mastercard Automatic Billing Updater (ABU) — Mastercard's equivalent service, sometimes referred to in older docs as "Mastercard ABU".
- Discover Account Updater — Discover's network service for cards in their network.
- American Express Cardholder Account Update — Amex's service, run directly with the issuing function inside Amex.
A merchant enrolled with one provider — Fluid Pay, in this case — covers all four through a single integration. There is no per-network signup, no separate vendor relationship, no separate billing thread.
Batched cycles — how the network services actually work
The four network updater services are batch services. Enrolled vaulted cards are submitted to the network on a recurring cycle, the network returns updates from the issuers, and the gateway applies the updates to the vault before the next scheduled charge. This is how every well-run recurring billing program in the industry operates.
Some providers market a "real-time" account updater as a layer on top of the batched services. Fluid Pay does not run a real-time variant today; we run the standard batched updater services the networks publish.
For the use cases that matter most — monthly subscriptions, weekly recurring, daily recurring, scheduled invoices — the batched cycle catches credential changes well before the next scheduled charge runs. The pattern that benefits least from batch is the one where a card vaulted today is charged the same day after that card was reissued between the vaulting and the charge; in practice that is a narrow band of transactions for most recurring portfolios. When you are evaluating providers, the question worth asking is whether your specific recurring cadence puts material volume in that narrow band, or whether the standard batched updater covers what you actually run.
Credential refresh rates — what to expect, and what claims to ignore
"Highest refresh rate" is a marketing claim that should be read carefully. The actual rate depends on:
- The issuer's participation in the network's account updater program.
- The completeness of the merchant's enrolled vault data.
- The recency of the cards in the vault — older expired cards return updates less often than recently-expired ones.
- How aggressively the merchant retries cards the updater could not recover.
Headline refresh rate numbers from vendors usually cherry-pick the subset of these variables that flatters them. The honest answer for a well-run program is that the updater service successfully returns a new credential for 80-90% of cards that have actually changed and that the issuer chose to expose. The remaining 10-20% are typically cards the issuer chose not to publish through the updater service — accounts closed without replacement, fraud cases the issuer is restricting, or issuers that are not participating fully in the network program for that card product.
Those remaining cases are where adaptive dunning takes over. The updater is the first line of defense; targeted retry and customer outreach is the second.
Pricing — pay only when a card updates
The pricing model is the part most partners are most surprised by.
You pay per update returned. Not per enrolment. Not per card looked up. Not a flat monthly fee whether or not anything was actually updated. If the network returns nothing, you owe nothing.
That alignment is deliberate. Every other updater pricing model — flat monthly subscription, per-card-on-file fee, per-attempt fee — pays the vendor whether or not the merchant got value. Pay-per-update only pays when something useful happened. For partners pricing the service to their merchants, it makes the math simple: charge the merchant a multiple of the per-update cost, and every update is positive contribution.
For high-velocity recurring portfolios, the absolute spend on updater fees clears easily against the recovered subscription revenue. A typical mid-market SaaS or fitness-membership portfolio sees the updater pay for itself in the first month and run as pure margin protection thereafter.
Stripe vs alternatives — choosing an account updater
This page is occasionally found via searches like "Stripe alternatives for account updater" or "who offers a real-time account updater" — so let us address the question directly.
Stripe runs a good account updater for businesses already on Stripe. The trade-off is that the updater is bound to the Stripe vault and the Stripe processing relationship. If your roadmap includes leaving Stripe — for residual ownership, partner economics, or vault portability — the updater leaves with it. For ISVs and resellers that need to control the merchant relationship, Stripe is rarely the right home.
Authorize.Net runs an updater, but the developer experience, the dashboard, and the latency around stored credentials reflect the platform's age. It works; it does not feel modern.
Other gateway updaters vary. The questions to ask any of them: which networks are covered under one enrolment? What is the pricing model — pay-per-update, flat fee, or per-card-stored? Is the vault portable if you ever leave? Does the implementation handle the small share of stored cards the networks decline to return through the batched service?
Fluid Pay runs the standard batched updater across Visa, Mastercard, Discover and Amex under one workflow, charges only when a card actually updates, and runs the updater against a vault that is portable by design. We do not run a real-time variant today; we do run the same batched services that the major networks themselves publish, which is what the vast majority of recurring portfolios rely on. We are the right choice for portfolios that need brand, vault and economics under partner control rather than under a processor's.
Where account updater sits in the Fluid Pay stack
Account updater is not a standalone product; it is wired into the vault that powers everything else.
- The Customer Vault is the data layer. Cards saved here are automatically eligible for the updater workflow.
- Recurring Billing is the highest-value beneficiary. Subscription transactions hit the updater path automatically before each scheduled charge.
- The Tokenizer reduces PCI scope by replacing PANs with platform tokens in your integration surface; the updater works against those vaulted tokens transparently.
- WatchDog fraud rules consume the updater signal as one input — repeated updater failures on a card can be a signal worth scoring.
This is the structural advantage of running the updater inside a gateway rather than as a third-party add-on. The vault, the recurring engine, and the updater share the same data and the same merchant configuration; there is nothing to wire up between them.
Why this matters for your portfolio
| Benefit | Impact |
|---|---|
| Protect recurring revenue | Fewer failed payments means uninterrupted subscription and membership billing |
| Reduce support burden | Eliminate "please update your card" calls and emails |
| Lower PCI exposure | No human handling of sensitive card data during updates |
| Strengthen merchant loyalty | When payments just work, merchants trust your platform |
What to do next
If you are running recurring billing portfolios and the updater is not currently turned on, book a partner demo and we will walk through the enrolment and the expected savings against your existing volume. The math is usually one of the easier ROI conversations in payments.
Frequently asked questions
Who offers a real-time account updater?
A handful of providers market a real-time variant that triggers an on-demand network lookup at transaction time. Fluid Pay does not run a real-time updater today — we run the standard batched updater services that the card networks themselves publish (Visa Account Updater, Mastercard Automatic Billing Updater, Discover, American Express). The underlying network services are batch by design, and for the vast majority of recurring billing schedules — monthly, weekly, daily — the batched cycle catches credential changes well before the next charge. If your specific workload depends on a real-time path that bypasses the batched cycle, that is a constraint worth raising in evaluation; for the much more common monthly-or-weekly recurring use case, the batched updater is what most well-run programs rely on.
What is account updater for credit cards?
Account Updater is a service the card networks run that lets merchants refresh expired, reissued or replaced card credentials without contacting the customer. Visa calls it Visa Account Updater (VAU). Mastercard calls it Automatic Billing Updater (ABU). Discover and Amex run their own equivalents. When a card on file becomes stale — expired, lost, fraud reissue, network reissue — the updater service returns the new credential to the merchant directly from the issuer. The customer never sees a failed payment, never gets a "please update your card" email, and the recurring revenue never breaks.
Which networks does Fluid Pay account updater cover?
All four major US networks. Visa Account Updater (VAU), Mastercard Automatic Billing Updater (ABU), Discover, and American Express. A single update workflow inside Fluid Pay covers all of them — you do not enrol separately, you do not pay separately per network.
Is account updater the same as network tokens?
No. Network tokens replace the underlying card number with an issuer-managed token so the actual PAN never travels in the transaction; the issuer keeps the token current as the underlying card changes. Account Updater refreshes a stored PAN when the underlying card changes. Fluid Pay supports the account updater path; we do not currently support network tokens. For most recurring portfolios the updater path is what actually drives recovered revenue against expired and replaced cards — network tokens are a complementary security primitive that solves a different problem.
What is the typical credential refresh rate?
Industry data shows up to 33% of stored card credentials change every year — expirations, lost cards, fraud reissues, network-wide reissues. The successful refresh rate on the updater pass depends heavily on issuer participation and on how complete the enrolled vault data is, but well-run merchants see 80–90% of changed credentials returned through the updater service rather than via a hard decline. The headline number partners care about is not the raw refresh rate; it is the involuntary churn the updater prevents.
How much does account updater cost?
You only pay when a card is actually updated. No per-enrolment fee. No charge for cards that did not change or that the network could not return a new credential for. The pricing model is the same one we apply across the partner stack: when our software produces a measurable result for the merchant, we get paid for the result. The math clears the per-update cost easily for any portfolio with meaningful recurring revenue.
Do I need to call my customers to update cards?
No. That is the entire point. A correctly running account updater removes the "please update your card on file" customer outreach. The next scheduled charge runs against current credentials and the customer never sees a payment failure. For the small percentage of credentials the updater cannot recover — cards closed entirely, fraud accounts with no replacement, accounts the issuer chose not to expose — adaptive dunning takes over and the customer outreach is targeted only at the cases that actually require it.
Stripe vs alternatives for account updater — how do they compare?
Stripe runs a competent account updater for merchants on the Stripe platform, and for businesses already deep in Stripe Connect it is a reasonable choice. The trade-off is that the vault and the updater are bound to Stripe; if you ever migrate off, the updater stops and the vault is hard to leave with the data intact. Authorize.Net runs an updater but the customer experience around stored credentials is markedly older. Fluid Pay runs the standard batched updater across all four major US networks, against the same vault that holds the rest of your merchants' tokens, and the vault is portable by design. The right choice depends on where the rest of your stack lives; we are the right choice for partners that need brand and vault control.