Account updater services automatically refresh expired card numbers and expiration dates on file for recurring billing, working through card-network programs like Visa Account Updater (VAU) and Mastercard Automatic Billing Updater (ABU). They return "closed account" and "contact cardholder" advices when a card can't be refreshed, so merchants know exactly when to stop billing and when to reach out. The direct result is fewer failed transactions and protected recurring revenue. Merchants enroll through their acquirer or processor, not directly with the networks.
TL;DR:
- Account updater services update only the primary account number and expiration date, but do not change billing address or CVV information.
- Visa VAU offers four update channels, including real-time checks during authorization, while Mastercard ABU primarily relies on scheduled bulk file submissions.
- Enrolling in these services involves your acquirer or processor, with typical steps including test exchanges and activation, not direct application to Visa or Mastercard.
- Merchants must apply updates within five business days after receipt and implement targeted retry or contact strategies based on specific network advices.
- These services are most effective when combined with comprehensive retry workflows and customer retention strategies, not as standalone solutions.
Table of Contents
- What Account Updater Services Can (and Cannot) Change
- Visa VAU vs. Mastercard ABU: What Each Program Actually Returns
- Batch vs. Real-Time: Picking the Right Update Cadence
- Getting Enrolled: Who Handles It and What to Expect
- Applying Updates: Timing, Retries, and What to Track
- Why Account Updater Is Just One Piece of a Resilient Billing Stack
- PaySec Helps You Turn Card Updates Into Recovered Revenue
- Key Network Resources for Implementation
- Sources
- FAQ
What Account Updater Services Can (and Cannot) Change
Account updater services exist to solve one narrow but expensive problem: cards on file go stale. A cardholder gets a new card after fraud, a reissue, or a routine expiration cycle, and the old number sitting in your billing system suddenly fails. Visa Account Updater and Mastercard ABU fix this by updating two specific fields and returning status advices when a fix isn't possible.
Here's what actually gets touched:
- Primary account number (PAN): refreshed when a card is reissued with a new number.
- Expiration date: updated when a card is renewed under the same number.
- Closed account advice: tells you the account no longer exists, so you can stop billing it.
- Contact cardholder advice: signals the network can't provide an automatic update and the customer needs to supply new payment details.
What it won't touch: billing address, CVV, or any cardholder-entered verification data. Those fields require direct customer contact, because no card network transmits CVV data through an updater service for security reasons.
Why this matters for your decline rate: a meaningful share of recurring-billing failures trace back to a small set of decline codes tied to expired or reissued cards, including code 54 (expired card) and code 14 (invalid account number). Account updater programs are built specifically to intercept those failures before they hit your authorization stream, which is why they've become close to standard infrastructure for subscription and membership billing.
Visa VAU vs. Mastercard ABU: What Each Program Actually Returns
Both programs solve the same core problem, but they route data differently and expect different integration choices from merchants.
Visa Account Updater offers four distinct channels:
- Batch file processing, where merchants submit a file of stored PANs and get updates back in bulk.
- Acquirer API, for on-demand lookups outside the batch cycle.
- Real Time VAU, which checks and updates account data during the authorization flow itself.
- Push Subscribe Service, which proactively notifies subscribed merchants when a subscribed account changes, without waiting for an inquiry.
All four channels can return account number and expiration updates plus closed account and contact cardholder advices.
Mastercard ABU takes a simpler, more prescriptive approach. Mastercard recommends bulk file submission as the primary method, with an API available as a secondary, on-demand check rather than the main channel. That's a meaningful difference from Visa's more distributed, real-time-capable architecture, and it shapes how you should design your update cadence around each network.
One integration nuance worth flagging early: if you're using a token vault or tokenization service to store card data (rather than raw PANs), confirm with your token provider how updater responses map back to existing tokens. A card tokenization strategy simplifies compliance, but it adds a translation step between the network's update response and your stored token that your integration needs to handle correctly. Enrollment nuances also differ slightly by network. Visa's Push Subscribe requires an explicit subscription step per account, while Mastercard's bulk file model assumes you're submitting your full portfolio on a schedule.
Batch vs. Real-Time: Picking the Right Update Cadence
Batch and real-time updates solve different problems, and most mature billing operations end up running both.
Batch updates work well when you're refreshing a large portfolio ahead of a scheduled billing run. Submit your file a few days before your billing cycle so returned updates have time to land in your system before charges go out.
Real-time updates, particularly Visa's Real Time VAU, work during the authorization flow itself. This removes the pre-authorization gap between when you check an account and when you actually charge it, which matters because a card can change status in that window. Real-time checks are best reserved for high-value transactions or declines you want to retry immediately rather than waiting for the next batch cycle.
A practical hybrid approach looks like this:
- Run a bulk update against your full subscriber file a few days before each monthly billing cycle.
- Use real-time checks on any transaction that declines during authorization, so you can retry immediately with fresh data.
- Reserve ad-hoc API calls for accounts flagged as high-risk or high-value between cycles.
Pro Tip: Time your batch submissions to your billing frequency, not to a fixed calendar. A weekly subscription box needs a tighter update cadence than an annual software license, and matching the two keeps your decline rate consistently low.
Getting Enrolled: Who Handles It and What to Expect
Your acquirer or processor handles account updater enrollment. You don't apply directly with Visa or Mastercard for this. That means your first step is a conversation with whoever processes your payments today, confirming they support VAU and ABU and walking through what they need from you.
Expect to provide:
- Your merchant identification details and processing history.
- A sample file of stored accounts (for batch enrollment) or API credentials setup (for real-time or on-demand access).
- Confirmation of which update channels you want: batch, API, real-time, or push subscribe for Visa; bulk file or API for Mastercard.
The typical path to activation runs through a few checkpoints:
- Enrollment request submitted through your acquirer, specifying which network programs and channels you want.
- Sandbox or test file exchange, where you submit a test batch and confirm the response format matches what your system expects.
- Activation call or confirmation, where your acquirer confirms live enrollment and update schedules.
- First live batch or API integration, monitored closely for the first cycle to confirm updates are landing correctly.
Integration options span bulk file formats (fixed-width or delimited files depending on your acquirer's specs), direct API calls through Visa's VAU Acquirer services or Mastercard's ABU API, and push/subscribe flows for accounts you want monitored continuously. Your acquirer sets the operational SLA for how quickly they forward network responses to you, but the obligation to actually apply those updates sits with you as the merchant. If you're evaluating processors for this, a dedicated merchant account with clear integration support makes this handoff considerably smoother than working through a generic reseller relationship.
Applying Updates: Timing, Retries, and What to Track
Receiving an update is only half the job. Applying it correctly, and on time, is what actually recovers revenue.
Visa sets a firm operational rule here: merchants must apply VAU updates to their customer databases within five business days of receipt. If you're using a token vault through an acquirer-provided token service, it is advised to apply VAU responses promptly to maintain updated tokens. Miss the window and you're back to declines on accounts you already had the fix for.
Once an update lands, route it intelligently rather than just retrying blindly:
- New PAN or expiration date: update your stored record and retry the failed transaction on your next scheduled attempt.
- Closed account advice: route into an automated pause workflow rather than continuing to attempt charges, which reduces chargeback risk.
- Contact cardholder advice: trigger a targeted email or SMS flow asking the customer to update payment details directly, rather than retrying a charge that will fail again.
Pairing updater responses with a structured dunning sequence rather than a flat retry schedule tends to recover meaningfully more revenue, since the update tells you exactly why the original charge failed. Track three numbers monthly: decline rate broken out by reason code, recovery rate in the window after an update is applied, and churn specifically attributable to payment failure rather than voluntary cancellation. Those three metrics together tell you whether your account updater investment is actually paying off.
Why Account Updater Is Just One Piece of a Resilient Billing Stack
Account updater services protect recurring revenue, but they're a safeguard, not a complete strategy on their own. The networks themselves are explicit that these programs work best paired with solid retry and dunning workflows, not as a standalone fix for payment failures.
The merchants who get the most value treat updater responses as an input into a larger system: token lifecycle management, structured retry sequencing, and customer retention strategies that complement payment continuity efforts that tell you where declines actually originate. Some payment processors build account updater support directly into that stack, mapping network advices to token updates and surfacing decline reasons through real-time reporting, rather than treating it as a bolt-on feature. Merchants across SaaS, restaurants, eCommerce, healthcare, and CBD retail rely on that kind of integrated visibility precisely because payment failures hit each vertical differently.
— PaySec Marketing Team
PaySec Helps You Turn Card Updates Into Recovered Revenue
Some providers offer transparent, contract-free processing with no hidden fees, which means the savings from reduced declines aren't offset by surprise charges elsewhere in statements. That combination matters because account updater services only pay off when the rest of your payment stack, pricing included, isn't quietly working against you.
PaySec's real-time reporting dashboards let your team track decline reason codes and recovery rates without waiting on monthly statements, so you can see exactly how updater responses translate into recovered transactions. For merchants running physical locations alongside recurring billing, PaySec's payment terminals integrate with the same reporting layer, keeping online and in-person payment continuity under one view. If you're ready to see how network offset pricing and integrated updater support could reduce your specific decline rate, reach out to your payment processor to discuss your processing setup and get a straightforward quote.
Key Network Resources for Implementation
Merchants implementing account updater should review Visa's VAU FAQs for enrollment and timing rules, and Mastercard's ABU documentation for API and bulk-file specs.
Sources
- Protect recurring revenue with Visa Account Updater | Visa
- Mastercard Automatic Billing Updater (ABU) merchant summary
- VAU Acquirer services (Visa Developer)
FAQ
What Are Visa Account Updater Services?
Visa Account Updater is a network program that automatically refreshes stored card numbers and expiration dates for merchants with recurring billing, and returns closed account or contact cardholder advices when a card can't be refreshed automatically. Merchants access it through batch files, an Acquirer API, Real Time VAU, or Push Subscribe Service, all administered through their acquirer or processor.
How Do I Opt Out of the Visa Account Updater Service?
Opting out is a merchant-side decision made through your acquirer or processor, since Visa doesn't enroll merchants directly. If you're a cardholder wanting your card excluded from a specific merchant's automatic updates, contact that merchant directly and ask them to remove your stored payment method.
How Do I Legally Stop a Merchant From Automatically Charging My Card?
Contact the merchant directly in writing to revoke authorization for future charges, and follow up with your card issuer to confirm the recurring charge has been blocked or disputed if the merchant continues billing after your request. Federal consumer protection rules require merchants to honor a cardholder's revocation of authorization for recurring charges.
How Do I See All My Saved Cards on File With Merchants?
There's no single account updater dashboard for consumers to view every merchant holding their card on file; you'll need to check each subscription service, streaming platform, or retailer individually through your account settings. Reviewing recent statement charges from your card issuer is typically the fastest way to identify which merchants have your card stored.