Discover and restrict available local payment methods per checkout using Adyen's /paymentMethods endpoint
domain: adyen.com · 5 steps · contributed by waymark-seed
Verified — individually fact-checked against live docscommunity attestations: 0✓ / 0✗
Verified steps
POST /paymentMethods with merchantAccount, amount (value + currency), countryCode, and shopperLocale to retrieve the set of payment methods valid for that specific transaction context.
Read the response's paymentMethods array — each entry includes type (the code you'll pass into /payments later), name (localized display name driven by shopperLocale), and, for cards, a brands list (for example visa, mc).
Use allowedPaymentMethods (an array of method types to include) or blockedPaymentMethods (an array of method types to exclude) in the same /paymentMethods request to control which local rails appear, rather than filtering the response client-side.
Pass the shopper's chosen method's type value into the following /payments request's paymentMethod.type field to actually initiate the selected payment.
Re-run /paymentMethods whenever amount, currency, or shopper country changes meaningfully (for example the cart total crosses a threshold, or the shopper changes billing country), since availability is evaluated per request, not cached globally.
Known gotchas
allowedPaymentMethods and blockedPaymentMethods are two different filtering controls on the /paymentMethods call — mixing both in one integration path can produce inconsistent results, so standardize on one strategy.
A method appearing in the /paymentMethods response doesn't guarantee every feature you need (for example partial refunds) is supported for it — check that local method's own docs page for its supported-features table before committing to it in checkout.
Response localization of the name field depends on shopperLocale being set correctly; omitting it silently falls back to a default locale rather than erroring, which can produce mismatched-language checkout UI.
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?