Enroll your merchant account in VAU through your acquirer and in Mastercard ABU through your Mastercard-certified processor; each network has its own enrollment process and file format requirements.
Submit a batch inquiry file containing the stored PANs and expiry dates you want to check — format differs per network but generally requires the PAN, current expiry, and a merchant reference.
Parse the response file: update records may include a new PAN, new expiry, a closure indicator (account closed), or a contact cardholder indicator; apply each update type to your vault accordingly.
For real-time updates, configure your processor to request VAU/ABU checks at authorization time — some processors support inline updater calls that return updated card data in the authorization response when the stored credential fails.
After receiving updated card data, re-attempt declined recurring charges using the new PAN or expiry within the window allowed by your processor's retry policies.
Purge or flag records that return a closure or contact cardholder response to avoid continued retry attempts on permanently closed accounts.
Known gotchas
VAU and ABU are opt-in for issuers — not all issuers participate, so updater responses will not cover the full portfolio of stored cards.
Account Updater data is governed by network rules; you may only use the updated credentials for the same cardholder and merchant, not share them or use for new account enrollment.
Batch submission windows and file delivery SLAs vary by acquirer and network; factor in processing time when planning retry logic so updated credentials are available before the next billing cycle.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp