Account Updater
Account updater is a card network service that automatically refreshes stored card credentials when a card is reissued, expired, or replaced.
Key Takeaways
- Account updater is a card network service that automatically refreshes stored payment credentials when a card is reissued, expired, or replaced, preventing failed recurring payments.
- Each major network operates its own program: Visa Account Updater (VAU), Mastercard Automatic Billing Updater (ABU), American Express Cardrefresher, and Discover Account Updater (DAU). These services process updates in batch or in real time.
- Network tokenization is emerging as a more modern alternative that eliminates the need for credential refreshes entirely by replacing card numbers with persistent tokens.
What Is Account Updater?
Account updater is a service provided by card networks that electronically exchanges updated payment credential information between card issuers and merchants who store cards on file. When a cardholder's account number or expiration date changes due to card replacement, expiration, or fraud, the account updater service delivers the new credentials to merchants automatically, so that recurring charges continue without interruption.
Roughly 30% of payment credentials change every year. Without account updater, each of these changes would require the cardholder to manually update their payment information with every merchant that has their card on file. For subscription businesses, this creates a significant source of involuntary churn: customers who intend to keep paying but whose payments fail due to outdated credentials.
Account updater bridges the gap between issuers (who know about card changes) and merchants (who store card credentials). It is a behind-the-scenes service that most cardholders never see, yet it keeps billions of dollars in recurring payments flowing each year.
How It Works
The account updater process involves three parties: the card issuer, the card network, and the merchant (typically through their acquirer or payment processor). There are two primary modes of operation: batch processing and real-time updates.
Batch Processing
The traditional account updater model works through periodic batch inquiries:
- When issuers reissue cards (due to expiration, loss, theft, fraud, or account upgrade), they submit the new credentials to the card network's updater database
- Merchants submit batch files containing their stored card numbers (PANs) to the network through their acquirer or processor, typically on a nightly or monthly cycle
- The network matches each submitted PAN against its issuer database and checks for any credential changes
- The network returns a response file containing updated credentials or status codes for each card
- The merchant updates their card-on-file records with the new information before the next billing attempt
Batch processing typically takes 24 to 72 hours from inquiry submission to response delivery. Visa requires acquirers to forward responses to merchants within two business days.
Real-Time Account Updater
Real-time account updater (RTAU) checks for credential updates during the transaction itself. When a recurring payment is attempted, the system queries the network for any changes before or alongside the authorization request. If an update is available, the payment is retried with the new credentials, all within seconds.
Visa launched Real-Time VAU in Europe and has since expanded it to Asia Pacific markets. RTAU supports Visa, Mastercard, and Cartes Bancaires networks through participating processors. Unlike batch processing, RTAU returns results in under three seconds and does not require merchants to submit credential files in advance.
Push Model
American Express Cardrefresher uses a push model rather than the pull-based batch approach. After a merchant submits their initial stored card list, the system monitors for changes and proactively sends daily electronic files containing any updated credentials. Merchants do not need to resubmit inquiry files: updates arrive automatically.
Response Codes
When an account updater query returns results, each card receives one of several status codes indicating what changed:
| Code | Meaning | Merchant Action |
|---|---|---|
| NAN (New Account Number) | A new card number has been issued | Update stored PAN with new number |
| NED (New Expiration Date) | The expiration date has changed | Update stored expiration date |
| ACL (Account Closed) | The account is permanently closed with no replacement | Suspend billing and contact cardholder |
| CCH (Contact Cardholder) | A change occurred but updated details are unavailable | Reach out to cardholder for new payment info |
An ACL response typically triggers immediate subscription suspension. A CCH response means the merchant must fall back to dunning: contacting the cardholder directly to collect updated payment information.
Network Programs
Each major card network operates its own account updater service:
| Network | Program Name | Model |
|---|---|---|
| Visa | Visa Account Updater (VAU) | Batch, real-time, and push subscribe |
| Mastercard | Automatic Billing Updater (ABU) | Batch (mandatory for issuers) |
| American Express | Cardrefresher | Push (daily files) |
| Discover | Discover Account Updater (DAU) | Batch (based on authorization history or merchant list) |
Visa Account Updater has expanded its platform to support updates from American Express and Discover, enabling cross-network updates through a single integration point. For a deeper look at how these networks operate, see our research on card network economics.
Use Cases
Subscription and Recurring Billing
Subscription businesses are the primary beneficiaries of account updater services. When 10 to 15% of all recurring payments fail on the initial attempt and expired cards account for 25 to 30% of those failures, account updater provides the most direct remedy: silently replacing outdated credentials before the next billing cycle.
Industry data shows that account updater services resolve 15 to 25% of expiration-driven failures without any cardholder interaction. Combined with smart retry logic and dunning workflows, merchants can recover up to 70% of initially failed payments. For more on how modern billing stacks handle this, see our research on subscription billing infrastructure.
E-Commerce Card on File
Online retailers that store customer cards for one-click checkout rely on account updater to keep those credentials current. Card-not-present transactions are especially vulnerable to credential decay because there is no physical card tap or chip read to refresh data at the point of sale.
Digital Wallets and Payment Platforms
Digital wallets, payment apps, and payment gateways use account updater to maintain the cards linked to user accounts. When a cardholder's bank replaces their card, the wallet provider receives the updated credentials and the user's experience remains seamless.
Insurance and Utility Billing
Any business that bills customers on a recurring basis using stored card credentials can benefit from account updater. Insurance companies, utility providers, and membership organizations all face the same challenge: maintaining payment continuity when cards are replaced.
Account Updater vs. Network Tokenization
Network tokenization represents a fundamentally different approach to the same problem. Rather than refreshing stored card numbers when they change, network tokenization replaces the card number entirely with a persistent token issued by the card network. When the underlying card is reissued, the token remains valid: the network's token vault updates the mapping automatically.
| Dimension | Account Updater | Network Tokenization |
|---|---|---|
| Mechanism | Refreshes stored PAN and expiry | Replaces PAN with a persistent token |
| Update latency | 24-72 hours (batch) or seconds (RTAU) | Instant (token vault updates transparently) |
| Security benefit | Maintains payment continuity only | Reduces CNP fraud via domain controls and cryptograms |
| PCI scope | No change (merchant still stores PANs) | Reduced (merchant stores tokens, not PANs) |
| Auth rate lift | Prevents declines from stale credentials | 2-7% authorization rate improvement |
| Best for | Legacy card-on-file databases | New integrations and long-term credential management |
The industry recommendation is to use both together: account updater for existing stored PANs that have not yet been tokenized, and network tokenization for all new card-on-file relationships going forward. For more on how tokenization reshapes payment security, see our research on fraud prevention in digital payments.
Costs
Account updater pricing varies by processor and network. Most pricing models charge per successful update rather than per inquiry, meaning merchants only pay when credentials actually change. Typical per-update fees range from $0.01 to $0.50 depending on the provider, with some processors bundling the service into their standard transaction fees at no additional cost.
For subscription businesses, the return on investment is substantial: the cost of a few cents per update is negligible compared to the lifetime value of a customer who would otherwise churn due to a failed payment. Industry analyses consistently show ROI exceeding 1,000% for businesses with significant recurring revenue.
Risks and Considerations
Incomplete Coverage
Account updater does not cover every card change. Issuer participation varies: while Mastercard ABU mandates issuer participation, other networks rely on voluntary enrollment. Some smaller issuers may not submit updates, and certain card changes (like a switch to an entirely different issuer) fall outside the system. Merchants should not assume that account updater alone will eliminate all credential-related failures.
Timing Gaps
Batch-based account updater introduces a timing gap between when a card is reissued and when the merchant receives the updated credentials. If a billing cycle falls within this window, the payment may still fail. Real-time account updater addresses this for supported networks and processors, but RTAU availability is not yet universal.
Privacy and Cardholder Opt-Out
Some cardholders may not want their updated credentials shared automatically with merchants. Card networks provide opt-out mechanisms, and issuers can use stop-advice services (like Visa's Issuer Stop Advice API) to block updates after fraud detection. Merchants must respect these signals and fall back to direct cardholder communication when updates are blocked.
Dependency on Network Infrastructure
Account updater relies entirely on card network infrastructure. Merchants have no direct access to issuer databases: they depend on their processor and the network to mediate the exchange. If a processor does not support account updater for a given network, those credentials will not be refreshed.
Why It Matters
Account updater addresses one of the largest sources of preventable revenue loss in card-based commerce. With approximately 30% of stored credentials changing every year and 20 to 40% of subscription churn being involuntary, the service acts as critical infrastructure for any business that relies on recurring billing.
As payment infrastructure evolves, the combination of account updater and network tokenization is becoming the standard approach for maintaining payment continuity. Meanwhile, newer payment paradigms built on blockchain rails: such as stablecoin payments and payment channel networks: avoid the credential-refresh problem entirely, since cryptographic addresses and keys do not expire or get reissued by a central authority.
This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.