Use Worldpay's Account Updater to refresh stored Visa, Mastercard, and Discover card credentials before recurring billing
domain: docs.worldpay.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Submit stored card details — either raw card data or an existing Access Worldpay token URI — to the Account Updater request flow ahead of the customer's next billing date.
For tokenized cards, expect a replacement token URI in the response for any account the networks report as updated, and update your stored reference to the new URI.
Handle each update category distinctly: new account number, new expiration date, cross-network migration (for example Visa to Mastercard), account-closed notification, and contact-customer notification.
Do not rely on Account Updater for billing address or AVS changes — it explicitly does not support those — and refresh that data through a separate process instead.
Re-attempt the recurring charge only after the stored credential has actually been updated, to avoid an authorization failure caused by stale card data.
Known gotchas
Account Updater does not cover address or AVS changes at all — don't expect it to resolve AVS mismatches caused by a customer moving.
This is a request/response, pull-style update mechanism tied to Access Worldpay's own tokens — its shape differs from push-webhook account-updater models used by other processors, so don't port webhook-handling code from another provider's integration onto this one.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?