What Is Account Updater? How Card Networks Reduce Involuntary Churn Before It Starts

Account updater (CAU) is a card-network service that pushes updated card credentials, new numbers, expiration dates, and account status, to your payment processor before a charge can fail. It stops involuntary churn at the source, before dunning is ever needed.

Most of what gets written about dunning treats it as a billing problem. It's actually a customer-communication problem with billing as a side effect. Account updater is the part that means some customers never hear from you at all.

Get this layer right and you prevent a whole class of failed payments instead of chasing them after the fact.

Key takeaways

• Turn on account updater to refresh card credentials before a charge can fail.
• About 40% of cardholders replace a card each year, breaking recurring charges.
• Visa and Mastercard each run their own account-updater feed.
• Involuntary churn runs about 0.86% of monthly revenue, a quarter of all churn.
• Account updater is layer one of four in the involuntary churn stack.
• Stripe charges $0.25 per update, so model the cost on cheap plans.

What is account updater?

Account updater is a card-network service that sends your processor a customer's new card details when their card expires or is replaced, before the charge runs. Visa calls its version Visa Account Updater (VAU), and Mastercard calls its Automatic Billing Updater (ABU). 

Both keep the card on file current, so the next charge runs against the customer's live card number.

Behind it is a subscription feed. Banks report card changes to the networks, the networks publish them, and your processor subscribes for you. When a customer's bank issues a new card, the processor writes the new number or expiry date into your stored record.

The charge that would have declined goes through, and nobody emails the customer for a new card.

For a recurring-revenue business, that prevention adds up. Stripe's account updater covers most US-issued Visa, Mastercard, American Express, and Discover cards on its own.

Doist, the team behind Todoist, turned it on and saw authorization rates rise by over 4%. Every declined charge there was a chance to lose a paying customer for good.

Account updater has gaps, though. It skips prepaid cards, many international issuers, and cards whose banks never opted into VAU or ABU. For those customers a card change still breaks the charge, so you fall back to smart retry and a proactive "update your card" email.

How Visa Account Updater and Mastercard ABU work

Both services report three kinds of card change, and each one points to a different action on your side. When the card number or expiry date changes, the network passes the new value to your processor and the next charge goes through. A closed account is different. 

There is nothing to update, so the network returns a "contact cardholder" response and recovery moves to your dunning sequence.

The two networks differ on timing.

Visa's VAU runs in batches, so a reissued card can sit stale in your vault until the next scheduled refresh.

Mastercard's ABU can push updates close to real time through its API, which is how processors like Adyen refresh Mastercard credentials soon after the bank issues them. Either way, a charge made during that gap can still fail, so route it to smart retry before any cancellation.

Why cards keep failing for subscription businesses

According to Stripe, about 40% of cardholders replace a card every year through expiry, loss, or fraud, and each one breaks the next charge. That decline code looks just like insufficient funds or fraud, so your billing system can't tell them apart.

A good customer who plans to keep paying lands in the same bucket as someone whose card had no money behind it.

The deeper damage is behavioral.

The National Bureau of Economic Research found that the months a customer's card is replaced bring much higher subscription cancellation rates. The card change forces an active renewal decision the customer would otherwise never have made.

A choice that used to stay passive is suddenly back on the table.

That gap is the difference between two failure types you have to keep apart.

A soft decline is a temporary failure the network lets you retry, like an insufficient-funds hold or a network timeout. A hard decline is permanent, a fraud-flagged or closed card the network won't let you retry without raising risk.

Retry a hard decline after the window closes and you just raise your dispute risk for a subscriber who is already gone. That is why account updater and smart retry aren't interchangeable, because one prevents failures and the other recovers them.

Where account updater fits in the involuntary churn stack

Account updater runs first among the four layers of the Involuntary Churn Prevention Stack, firing before the charge. Each later layer handles a different failure class as the charge moves from prevention to dispute.

This matters because involuntary churn runs about 0.86% of revenue every month, roughly a quarter of all the churn a typical subscription business sees. No single tool recovers all of it, which is why the layers stack.

The order matters because each layer clears a failure type before handing the rest down, so the tool below it works on a problem it can actually fix. The full stack is covered in the dunning playbook.

Layer 1: Account updater (prevent credential failures)

Account updater fires before the charge and removes the replaced-card failures that would otherwise hit your dunning queue with stale credentials. The fix happens in your vault before the charge runs, so the failure never reaches the later layers at all.

Layer 2: Smart retry (recover soft declines)

Smart retry kicks in right after a soft decline and uses the decline code to decide whether to retry now or wait. A network timeout justifies an immediate retry, and an insufficient-funds decline justifies waiting for a likely payday.

Smart retry doesn't help with card mismatches, though, because those arrive looking like account closures. Retrying the same dead number only burns attempts.

Layer 3: Dunning sequence (email and in-app recovery)

The dunning sequence runs over 7 to 21 days when a retry fails or a card comes back uncollectable. It uses email and in-app messages to ask the customer to act, and it recovers the failures the first two layers couldn't prevent or fix.

Businesses that run a smart sequence recover up to 72% of at-risk subscribers. That recovery rate is why the sequence earns real design effort and a message matched to each failure type.

Layer 4: Chargeback mitigation (last line)

Chargeback mitigation is the last layer, and it triggers only when a customer disputes a charge. Aggressive retries or repeated hard-decline attempts can push a frustrated customer toward a chargeback.

The three layers above exist to fix the problem before it ever reaches this one. For the disputes that do file, tools like Chargeback.io handle the resolution side.

If you're mapping these layers onto your own billing setup, Churn.io handles the recovery stack above dunning.

How to enable account updater on Stripe, Adyen, and Braintree

Turning on account updater takes no code on Stripe, where it's on by default for US-issued cards on the major networks. On Adyen and Braintree, you flip a setting in the merchant portal or set an API flag.

All three charge a per-update fee, and on Stripe that fee is $0.25 per successful update. The barrier is low, which is why leaving it off is such a common miss.

Behind the scenes, your processor subscribes to each network's updater feed and writes new credentials into your vault. Visa and Mastercard run VAU and ABU, and Amex and Discover run their own equivalents.

The subscription happens once, at the account level, so it covers every stored card with no per-customer setup.

At scale the recovered revenue can be large. Postmates turned on CAU through Stripe and recovered $60 million in one year from a 1.72% authorization-rate lift. Returns like that dwarf a modest per-update cost.

That cost isn't free at scale, so check it before you assume it always pays. Compare the update fee to what a saved subscriber is worth, which is your average revenue per account (ARPA) times the months you keep them.

Say a $4-a-month account, where one update costs a few cents against several dollars of recovered revenue. On a base of low-revenue accounts the margin narrows, so model it first.

FAQ

Does account updater prevent all involuntary churn?

No. Account updater only prevents card-change failures, so soft declines and closed-card declines still need smart retry and dunning to recover.

How much does enabling account updater cost on Stripe?

Stripe bills a small fee for each card update, charged only when a card is refreshed. Whether it pays off depends on your ARPA, so the fee is easy to justify on most plans and only tightens on low-revenue accounts.

What is the difference between account updater and network tokenization?

Account updater keeps your stored card number current when it changes, while network tokenization replaces that number with a secure token so you never store it. One keeps credentials current and the other protects them, so many businesses use both.

Do I need account updater if I already use Stripe Smart Retries?

Yes, because account updater and Smart Retries solve different problems. Smart Retries re-attempt a soft decline with better timing, but they can't fix a charge that fails because the stored card number is out of date.