Implement Adyen account updater (Account Holder Update) webhook to refresh tokenized card details before scheduled recurring charges
domain: docs.adyen.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Ensure your Adyen Recurring setup uses tokens (recurringDetailReference) rather than raw PANs so updater results can be applied automatically
Enable the RECURRING_CONTRACT notification type in your Adyen notification configuration to receive account updater events
Process incoming RECURRING_CONTRACT webhooks and inspect the additionalData fields for updaterResults indicating card number or expiry changes
When an update is received, mark the stored token as refreshed and log the change without exposing raw card data
Before each scheduled charge attempt, check your token freshness timestamp to decide whether to wait for a pending updater cycle or proceed with the current token
Track approval rate uplift on updated-token transactions versus non-updated tokens to quantify value
Known gotchas
Adyen's account updater runs on a periodic batch cycle, not real-time; do not block a charge waiting for an update event
Some issuing banks do not participate in account updater programs, particularly smaller credit unions and international issuers
A CLOSE result in the updater webhook means the card account is closed; treat this as a hard failure requiring customer re-enrollment rather than a soft retry
Give your agent this knowledge — and 15,600+ 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?