Payments FAQ
These are the questions that keep coming up when someone is choosing a payment service provider or building a checkout for the first time. Each one gets its own page, with the short answer at the top and the detail underneath, so you can stop reading as soon as you have what you came for.
They are written from the merchant side, by someone who has sat through the RFPs and the integrations, so the answers cover what actually costs you time later rather than only what the documentation says.
What is the difference between Drop-in and Components?
One ready-made checkout against a set of parts you assemble yourself. What each one costs you, what happens to saved cards, and why the two have very different upgrade bills.
What changed in Adyen Web v6?
The generic create() factory is gone, so every payment method needs its own class. What that means for a Components upgrade, and the fallback that hides a broken checkout.
locale vs countryCode: what is the difference?
One sets the language, the other decides which payment methods appear. Why setting one does not imply the other, and why changing locale needs a whole new component.
Coming next
The list grows as the playgrounds do. These are the ones being written now:
- Hosted checkout or embedded checkout, and how to choose
- What a payment webhook is, and why the retries are not a bug
- Stripe Checkout against Stripe Elements
A question that is not answered here?
Send it over. If it is a good one, it becomes the next page.
Personal project by Elie Joseph. Not affiliated with, endorsed by, or officially connected to any payment service provider. All product and company names, logos and brands referenced on this site are property of their respective owners. Playgrounds run against test environments only. No real payments are processed. Use only test data. Never enter real card numbers, real personal information, or any genuine payment details on this site or in any linked test environment.