The currency in the request is wrong
How you'll know: A local method shows in testing for one market and never for another.
Fix: Local methods are tied to their currency. Send the shopper's currency in amount, not your home currency.
A customer in Amsterdam emails to ask why there's no iDEAL at checkout, when you're sure it was switched on. On Adyen, a method only appears when three things agree: your account has it, the checkout request describes a shopper it works for, and your front end renders it. Here's each layer, starting with which methods matter where.
Cards and wallets such as Apple Pay and Google Pay travel well. These are the local methods shoppers in each market look for. Confirm in Adyen's payment method docs what your account can offer.
Search for the methods you want and add several at once. Some go live directly; others open a case with Adyen first. You need the Change payment methods role to do this. The Management API can request methods too.
Watch for: the request is asynchronous. A method you asked for this morning may not be active yet.
Each method's settings in the Customer Area include the countries or regions it's available in. Narrow it there if a method should only ever appear in one market.
Your server calls /paymentMethods with your merchantAccount, the shopper's countryCode, the amount (currency plus value in minor units), the channel (Web, iOS or Android) and shopperLocale. Adyen returns only the methods that fit that shopper. On the Sessions flow, the same details go on the /sessions request.
Watch for: allowedPaymentMethods and blockedPaymentMethods. They let one request show or hide methods by type, which is how per-market or per-basket rules get applied.
Drop-in shows the whole returned list in one block. With Components you mount one method at a time, in the order and layout you choose.
How you'll know: A local method shows in testing for one market and never for another.
Fix: Local methods are tied to their currency. Send the shopper's currency in amount, not your home currency.
countryCode is missing or set from the wrong fieldHow you'll know: Every shopper sees the same short list.
Fix: Pass the shopper's country, usually from billing or shipping address or a country picker, rather than your company's country.
How you'll know: It's listed in the Customer Area but never comes back from /paymentMethods.
Fix: Check whether the request opened a case that's waiting on you or on Adyen. Methods with their own onboarding stay off until it finishes.
How you'll know: The API response includes it, but the page doesn't.
Fix: Look for a blockedPaymentMethods list, an old allowedPaymentMethods list, or front-end config that filters methods after the response.
How you'll know: Testers on Windows or Android never see it.
Fix: That's expected: Apple Pay appears only where the browser and device support it. For it to work live on the web, each domain also has to be verified with Apple's domain association file.
/paymentMethods or your session.Both come from Adyen Web, so this is a front-end choice. What decides which methods are offered is still the request your server sends.
Request it in the Customer Area like any other method. For the web, you can use Adyen's Apple Pay certificate or your own Apple merchant identifier, and each live domain has to be verified by hosting the domain association file at /.well-known/apple-developer-merchantid-domain-association. A test account doesn't need the file.
Yes. Klarna is among the buy now, pay later methods you can request through the Customer Area, and like several methods it may go through its own onboarding before it's live. Once it is, it comes back from /paymentMethods for shoppers in the countries and currencies it supports.
Yes. Adyen already filters by the countryCode and currency you send, and you can limit a method's countries in its Customer Area settings. For rules Adyen doesn't know about, like hiding a method on low-value baskets, send allowedPaymentMethods or blockedPaymentMethods on each request.
Adyen Web is the JavaScript library. Drop-in is one way of using it: a single block that renders every method Adyen returns. Components are the other way, mounting one method at a time for more control over layout.
Each transaction carries a processing fee plus a fee for the payment method used, and that fee differs by method. Cards are priced on interchange++. Adding a method doesn't cost anything until it's used, but your blended rate shifts with the mix, so check Adyen's pricing page for the methods you plan to offer.
Adyen's payment method docs list each method with its countries and currencies, and the Management API returns the countries a method is available in for your account. For a live answer per shopper, call /paymentMethods with their country and currency.