Up to a third of stored card credentials change every year — expirations, lost cards, fraud reissues. For any business billing cards on file (gyms, subscriptions, SaaS, utilities), each changed card is a failed rebill and a customer to chase. Visa Account Updater (VAU) and Mastercard's Automatic Billing Updater (ABU) solve this by pushing fresh card details to participating merchants automatically. The service costs money per update — and Mastercard quietly penalizes you if you bill stale credentials without it.
What VAU and ABU do: the credential refresh loop
The mechanics are simple. You enroll through your processor or gateway. Before each billing run, your stored credentials are checked against the networks' update databases; changed cards come back with fresh numbers and expiry dates. No customer action needed — cardholders are enrolled by their issuers (major banks auto-enroll all cards), and the update costs the cardholder nothing.
Well-run merchants recover 80–90% of changed credentials through the updater instead of eating a hard decline. That's the number that matters: not the refresh rate, but the involuntary churn it prevents.
What updates cost: the pricing models
| Model | How you're billed | Watch for |
|---|---|---|
| Pay per update | Charged only when a card actually changes; nothing for unchanged or unmatchable cards | The per-update rate varies by provider — get it in writing |
| Per inquiry / scheme request | Charged per lookup request sent to the network | You pay even when nothing changed |
| Bundled | Updater included in gateway or platform pricing | Confirm it's actually enabled, not just "available" |
The pay-per-update model is the fairest structure: the provider only gets paid when it produces a measurable result. Per-inquiry pricing bills you for asking, whether or not the card changed — fine at small scale, wasteful on large vaults with low churn.
The hidden penalty: Mastercard's Credential Continuity Fee
Here's the fee nobody tells you about. Mastercard assesses a $0.03 Credential Continuity Fee on every recurring transaction billed with an outdated credential — when the issuer reported a card update to the ABU database at least 10 days earlier and you billed the old details anyway.
Three cents is trivial in dollars. It's significant as a signal: the network is watching stale-credential billing and pricing it. The fee exists to push merchants onto the updater. If you're seeing this line item on your statement, it's the network telling you your vault is going stale — fix the updater enrollment, not the fee.
Worked ROI — 500-subscriber membership at $40/month ($20,000/month recurring): ~33% annual credential churn means ~14 cards go stale each month. Without an updater, assume half are lost to failed rebills: 7 × $40 = $280/month in involuntary churn. An updater recovering 80% saves ~$224/month. Even at $0.30 per update on 14 updates ($4.20/month), the return is roughly 53-to-1. The updater isn't a cost — it's the highest-ROI line item in recurring billing.
Choosing and configuring: the checklist
- Enroll through your gateway first. Most gateways offer updater as an add-on — it's cheaper and better integrated than a third-party bolt-on.
- Demand pay-per-update pricing. No per-enrollment fees, no charges for unchanged cards. If the provider can't quote a per-update rate, keep shopping.
- Time the refresh before billing. Run the updater pass a few business days before your billing run — updates need time to propagate, and same-day refreshes miss.
- Watch for the $0.03 line item. Credential Continuity Fees on your statement mean stale billing is happening — treat it as an enrollment alarm, not a cost of doing business.
- Don't confuse updater with network tokens. Updater refreshes a stored card number; network tokens replace the number with an issuer-managed token. They solve different problems and complement each other.
A note on steps: this is a fee explainer with a decision framework, not a repair procedure — the checklist above is the actionable part. Enrollment flows differ by gateway and processor, so there's no single settings path.
FAQ
Do my customers have to opt in to card updates?
No. Issuers auto-enroll cards in VAU/ABU, and updates flow to participating merchants without cardholder action. The programs cost cardholders nothing.
Does the updater work for all cards?
Only for participating issuers and merchants on Visa and Mastercard rails. Coverage is broad among major banks but not universal — some credentials will still come back unmatchable.
Is the updater worth it for a small subscriber base?
Run the math above with your numbers. At pay-per-update pricing, the cost scales with actual changes, so even small portfolios usually clear the ROI bar — the churn it prevents is worth far more than the per-update fee.