What Is Account Updater? (SaaS Billing Glossary)
Account updater (CAU) is a card-network service that automatically pushes a customer's refreshed card details to your processor when their card expires or is replaced, closing the involuntary-churn gap caused by stale card data.

Account updater (CAU) is a card-network service that pushes a customer's updated card details to your processor when their card expires or is replaced. Those details cover the new card number, expiry date, and account status.
Visa and Mastercard feeds broadcast the changes from issuing banks, so your stored card stays current before the next charge runs.
Key takeaways
- Account updater refreshes stored card details before a recurring charge can fail.
- Visa runs Visa Account Updater and Mastercard runs Automatic Billing Updater.
- About 40% of cardholders replace a card each year, which breaks recurring charges.
- Account updater is layer one of the involuntary churn prevention stack.
- Stripe charges $0.25 per successful card update, so check cheap plans.
What is account updater?
Account updater keeps the card you have on file current, so a recurring charge runs on a customer's live card number even after their bank reissues the card. Visa runs its program as Visa Account Updater (VAU), and Mastercard runs its Automatic Billing Updater (ABU).
It works through a batch feed. Banks report card changes to the networks, the networks pass them to your processor, and your processor writes the new number into your vault. The charge that would have failed on the old card then goes through on the new one.
The scale is what makes this worth turning on. About 40% of cardholders replace a card each year through expiry, loss, or fraud. For a 1,000-subscriber business, that is about 400 card changes a year, most of them caught before they become failed payments.
Account updater has gaps. It skips prepaid cards, many overseas banks outside the VAU and ABU map, and banks that never joined the programs. For those cards a replacement still breaks the charge, and your fallback is an email asking the customer to update their card.
That sets the boundary on involuntary churn, the revenue you lose to a failed payment instead of a customer choosing to leave. Account updater clears only the slice caused by a card change.
Where account updater fits in involuntary churn recovery
Account updater is layer one in the Involuntary Churn Prevention Stack, the only step that fires before a charge is attempted. The later layers, smart retry and the dunning sequence, handle the failures it can't prevent.
Smart retry re-times a charge after a soft decline. The dunning sequence is the run of retries and emails that wins back payments over several days.
Because account updater clears the stale-card failures first, fewer charges reach the retry and dunning queues. Those later layers then spend their attempts on the soft declines they can actually recover.
Use the churn rate calculator to size the involuntary churn revenue at risk before you enable account updater.
The full involuntary churn stack guide sets account updater next to smart retry, dunning, and chargeback recovery, so you can see which failures each one catches.
FAQ
Does account updater work for all cards?
No, but each major network runs its own program, including Visa's VAU, Mastercard's ABU, and equivalents at American Express and Discover. The cards outside those programs are the gap, which is why coverage is never total.
Is account updater the same as network tokenization?
No, account updater refreshes your stored card number when the bank changes it, while network tokenization replaces that number with a token you keep. One keeps the card current and the other removes it from your system, so many businesses run both.
How much does enabling account updater cost on Stripe?
According to Stripe's pricing page, Stripe charges $0.25 per successful card update, billed only when a card is refreshed. Whether it pays off depends on your revenue per account, so it clears on most plans and tightens only on cheap ones.
Do I need account updater if I already use smart retries?
Yes, because the two tools solve different failures. Smart retries re-time a soft decline, but they can't fix a charge that fails on an out-of-date card number.