Enable network tokenization in your Adyen merchant account settings; Adyen acts as a token requestor and automatically attempts to provision a network token when a card is stored via the Adyen vault (shopper token)
When a stored recurring charge is processed, Adyen uses the network token and generates the appropriate cryptogram per transaction, improving authorization rates over raw PAN use
Adyen also participates in Visa VAU and Mastercard ABU; when stored card details change, Adyen updates the underlying token and fires a RECURRING_CONTRACT notification (verify the exact notification type in current Adyen docs)
Subscribe to Adyen's account-updater webhook notifications in your Adyen Customer Area; implement a handler that updates your internal recurring schedule when a card is replaced or cancelled
For closed accounts, trigger your subscription cancellation flow and notify the customer; for updated expiries or replacements, silently update the stored credential and continue billing
Test using Adyen's test token values and notification simulator in the Customer Area sandbox before enabling in production
Known gotchas
Adyen's network tokenization availability depends on the card BIN and issuer participation; not all stored cards will receive tokens — Adyen falls back to PAN-based processing for non-eligible cards
The RECURRING_CONTRACT notification structure may differ between Adyen Checkout API versions; always test the notification payload against your parser after an API version upgrade
Adyen account-updater processing runs on a schedule set by Adyen and the networks; do not rely on real-time updates before attempting a charge — build a retry path for declined-due-to-credential-change scenarios
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