# Account Updater Service: Stop Losing Revenue to Expired Cards

> An account updater service refreshes stored card details automatically so recurring charges do not fail. Learn how Visa and Mastercard updater programs work and how to enable one.
- **Author**: Ayush Agarwal
- **Published**: 2026-07-21
- **Category**: Payments, Billing, SaaS
- **URL**: https://dodopayments.com/blogs/account-updater-service

---

A customer signs up, pays happily for eight months, then their bank reissues the card after a breach. The card number changes, your stored credentials go stale, and the next renewal fails for a customer who never intended to leave. That silent failure is one of the most common causes of involuntary churn in subscription businesses, and an account updater service exists specifically to prevent it.

If you are searching for "account updater service," the short answer is this: it is a card-network program that automatically refreshes the card details you have on file when a customer's card is reissued, expires, or gets a new number. Instead of chasing customers to re-enter their card, the updated details flow to you behind the scenes so the recurring charge succeeds. Roughly 20-40% of subscription churn at most SaaS companies is involuntary, and stale card data is a large slice of that.

This guide explains what an account updater is, how the Visa and Mastercard programs work, where it fits in your billing stack, and how to turn it on without building integrations against each card network yourself.

## What an Account Updater Service Actually Is

An account updater service is a data-syncing program run by the card networks that keeps merchant-stored card credentials current. When an issuing bank reissues a card, the new details are published to the network's updater database. Merchants enrolled in the program can then query that database and receive the refreshed card number, expiry date, or account status before they attempt the next charge.

The problem it solves is specific to card-on-file billing. Every subscription, every saved-card checkout, and every usage-based product that charges a customer after the fact depends on stored card credentials staying valid. Cards get reissued constantly: expiration, loss, theft, fraud reissues, and portfolio migrations when banks merge. Without an updater, each of those events turns into a failed payment the moment you try to bill again.

The core value is that it moves the fix from reactive to proactive. Instead of waiting for a decline and then running a dunning sequence, the correct card data is already in place before the charge runs.

The three most common responses an updater returns are:

- **A new card number**, when the account was reissued with a fresh PAN.
- **A new expiry date**, when the card was renewed but kept the same number.
- **A closed-account flag**, when the card can no longer be billed at all.

That last response is just as valuable as the updates. Knowing a card is permanently dead lets you stop retrying it and instead prompt the customer for a new payment method, rather than burning retries and triggering fraud flags.

## The Two Major Programs: VAU and ABU

There is no single universal updater. Each card network runs its own, and a good billing provider connects to all of them so you get coverage across your customer base.

| Network | Program name | What it covers |
| --- | --- | --- |
| Visa | Visa Account Updater (VAU) | Reissued and updated Visa cards |
| Mastercard | Automatic Billing Updater (ABU) | Reissued and updated Mastercard cards |
| American Express | Cardrefresher | Updated American Express cards |
| Discover | Discover Account Updater | Updated Discover cards |

Visa Account Updater and Mastercard Automatic Billing Updater are the two that matter most for the average subscription business, simply because those two networks dominate card volume in most markets. The mechanics are similar across all four: enrolled merchants submit their stored card records on a schedule, the network matches them against its database of reissued cards, and it returns updates where they exist.

One important nuance is coverage. An updater can only return data that issuing banks actually publish, and not every bank participates fully in every market. That means an updater will meaningfully reduce failed renewals, but it will not eliminate them. It is one layer of a larger revenue-recovery strategy, not a silver bullet.

## Where the Account Updater Fits in Your Billing Flow

```mermaid
flowchart TD
    A[Stored Card on File] --> B{Renewal Due}
    B --> C[Account Updater Check]
    C -->|New card details| D[Update Stored Credentials]
    C -->|Card closed| E[Prompt Customer for New Card]
    C -->|No change| F[Proceed With Charge]
    D --> F
    F --> G{Charge Result}
    G -->|Success| H[Subscription Continues]
    G -->|Soft decline| I[Retry Logic and Dunning]
```

The updater sits upstream of the actual charge. Before a renewal runs, the stored card is checked against the network databases, credentials are refreshed if needed, and only then does the payment attempt go out. When it works, the customer never sees a thing: the charge simply succeeds on the correct card.

This is why account updater coverage pairs so well with smart retry logic and a structured dunning process. The updater fixes the cause of many failures before they happen; retries and dunning catch the ones that slip through, such as temporary insufficient-funds declines. Together they recover far more revenue than either does alone. If you want the full recovery picture, our guide on [how to reduce payment declines](https://dodopayments.com/blogs/reduce-payment-declines) covers the retry side in depth, and the deep dive on [involuntary churn from failed payments](https://dodopayments.com/blogs/involuntary-churn-failed-payments) explains how these failures compound into churn.

## Building It Yourself vs Using a Provider

You can technically enroll in VAU and ABU directly, but for most teams it is the wrong build. Direct enrollment means qualifying with each network, meeting their data-format requirements, managing submission schedules, storing raw card data (which drags you into full PCI DSS scope), and handling the response files from each program separately.

Doing that in-house has real costs:

- You must hold and process card numbers to submit them, which expands your PCI obligations dramatically.
- You maintain separate integrations for Visa, Mastercard, American Express, and Discover.
- You build the scheduling, matching, and reconciliation logic that decides when to update a stored token.
- You keep all of it working as network file formats and requirements change.

The alternative is to use a payment provider or Merchant of Record that already runs account updater coverage as part of its stored-credential handling. Because the provider tokenizes cards and holds the sensitive data in its own vault, updates get applied to the token automatically, and you never touch a raw card number. This is the same reason [payment tokenization](https://dodopayments.com/blogs/payment-tokenization) matters: the token in your database stays stable while the real card behind it gets refreshed.

Dodo Payments handles this as part of its billing infrastructure. As a [Merchant of Record](https://dodopayments.com/payments/merchant-of-record), Dodo stores cards on its own PCI DSS Level 1 certified vault, keeps credentials current through network updater programs, and pairs that with automatic payment retries and dunning. The [revenue recovery](https://dodopayments.com/pricing) tooling is free to enable, and Dodo only charges on revenue it actually recovers, so keeping cards fresh does not add a fixed line item to your bill. You can see how the recurring side works in the [subscriptions documentation](https://docs.dodopayments.com/features/subscription) and the broader [billing overview](https://dodopayments.com/billing).

## How Much Revenue an Account Updater Recovers

The impact depends on your card mix and renewal frequency, but the mechanism is easy to reason about. If involuntary churn is 30% of your total churn, and stale card data causes a meaningful share of those failures, then closing that gap directly protects recurring revenue you have already earned. For a business at scale, a few percentage points of recovered renewals compounds into a significant annual figure because every recovered subscription keeps generating revenue for its remaining lifetime.

Three factors drive how much you recover:

- **Renewal volume.** More recurring charges means more chances for a stale card to cause a failure.
- **Card reissue rate.** Consumer cards in markets with frequent security reissues benefit more.
- **Issuer participation.** Coverage is strongest where local banks publish updates to the networks.

The point is not to chase a single headline number. It is to recognize that a failed renewal on a still-valid customer is pure avoidable loss, and an account updater removes a large chunk of that loss with zero customer friction. Combined with the retry and dunning strategies in our [subscription dunning recovery guide](https://dodopayments.com/blogs/subscription-dunning-recovery-sequence), it forms the foundation of a healthy retention stack.

## Account Updater vs Manual Card Updates

Some teams try to solve stale cards with email prompts alone: detect the failure, email the customer, and ask them to update their card in a billing portal. That approach still matters as a fallback, but it should not be your first line of defense.

| Approach | When it acts | Customer effort | Recovery rate |
| --- | --- | --- | --- |
| Account updater | Before the charge fails | None | Higher, silent |
| Manual email prompt | After the charge fails | Customer must act | Lower, depends on response |

The manual approach only works if the customer opens the email, cares enough to act, and still wants the product. Many simply do not respond, and you lose them despite them having no real intent to churn. The account updater removes that dependency for every card the networks can refresh, and the manual prompt catches the remainder. Building a [customer billing portal](https://docs.dodopayments.com/features/customer-portal) for self-service updates complements the updater rather than replacing it.

## Getting Started

If you are running any card-on-file billing, the practical path is straightforward:

1. Confirm whether your current payment provider already applies account updater programs to stored cards. Many do not, or charge extra for it.
2. Make sure updates are applied at the token level so you never expand your own PCI scope.
3. Pair the updater with automatic retries and a dunning sequence so the failures it cannot fix still get a recovery attempt.
4. Keep a manual card-update path in your customer portal for closed accounts that no updater can refresh.

You can explore how Dodo Payments combines account updater coverage, tokenization, retries, and dunning into a single recovery layer on the [payments page](https://dodopayments.com/payments), or read the [integration guide](https://docs.dodopayments.com/developer-resources/integration-guide) to see how stored-card billing is set up.

## FAQ

### What is an account updater service?

An account updater service is a card-network program that automatically refreshes the card details a merchant has on file when a customer's card is reissued, renewed, or closed. It lets recurring charges succeed on the correct, up-to-date card without the customer needing to re-enter their payment information.

### How do Visa Account Updater and Mastercard Automatic Billing Updater work?

Both programs maintain a database of reissued and updated cards published by issuing banks. Enrolled merchants submit their stored card records on a schedule, the network matches them against its database, and it returns any new card numbers, new expiry dates, or closed-account flags so the merchant can update credentials before the next charge.

### Does an account updater eliminate all failed payments?

No. An account updater only returns data for cards that issuing banks actually publish, and participation varies by bank and market. It meaningfully reduces failures caused by stale card data, but you should still pair it with retry logic and dunning to recover the declines it cannot fix, such as temporary insufficient-funds errors.

### Do I need to be PCI compliant to use an account updater?

If you enroll directly with the card networks, you must store and submit raw card numbers, which places you in full PCI DSS scope. Using a payment provider or Merchant of Record that applies updates at the token level lets you get the benefit without holding sensitive card data yourself.

### Is account updater coverage worth it for a small subscription business?

Yes, because the cost of a silently failed renewal is high relative to the effort of enabling coverage through a provider. Even a small business loses real recurring revenue when a still-valid customer's card goes stale, and an updater recovers those charges with no customer friction.
---
- [More Payments articles](https://dodopayments.com/blogs/category/payments)
- [All articles](https://dodopayments.com/blogs)