Your code calls a different version
How you'll know: A field that worked in the Explorer is ignored or rejected when your server sends it.
Fix: Set the version explicitly in the URL or the library config, and make it the one you tested against.
You want to see exactly what a /payments request expects before anyone writes the code for it. Adyen's API Explorer, at docs.adyen.com/api-explorer, is the reference for every Adyen API and webhook, one version at a time, with example requests and the option to send your own against a test account. It tells you what a call looks like. Whether your checkout should sit on Drop-in, Components, the API on its own or the Terminal API is a separate choice, and it's the one that costs the most to undo.
Pick the API, then the version. The version is part of the URL you'll call, and Checkout's newest is v72. Match the version your code or library actually uses, not just the newest one.
API Explorer › Checkout API › v72Open the endpoint. Each one lists its fields, marks the required ones, such as merchantAccount, amount and reference, and shows sample requests and responses.
Send it with a test key. Use an API key from your test Customer Area at ca-test.adyen.com. Test and live keys are never interchangeable.
Webhooks are listed too. Each webhook set has its own entry with the payload your handler will receive.
Each layer sits on the Checkout or Terminal API underneath. What changes is how much of the payment page Adyen draws for you.
The Explorer shows one API version at a time. A library or an older part of your integration may call a different one, and fields are added, renamed or retired between versions.
Watch for: the version comparison in Adyen's docs. It lists what changed from one version to the next.
Swap the sample merchantAccount for your test merchant account name and use a payment method that's set up on it. A perfectly formed request still fails for a method the account doesn't have.
Adyen's server libraries for Node, Java, PHP, Python, .NET and other languages wrap the same fields as typed objects. Each library release targets particular API versions, so check its release notes against the version from step one.
Take the webhook's payload from its Explorer entry and parse that, then let a real test payment send you one so you see the actual event, not the sample.
Nothing created in test carries over. Live credentials, webhooks and the prefixed live URL all come from the live Customer Area.
How you'll know: A field that worked in the Explorer is ignored or rejected when your server sends it.
Fix: Set the version explicitly in the URL or the library config, and make it the one you tested against.
How you'll know: Checkout calls succeed, while a Management or platform call is refused as forbidden.
Fix: Add the role to the credential in the Customer Area, or give that API its own credential with only the roles it needs.
How you'll know: The handler breaks on its first real webhook, because a field the sample left out turns up, or one it showed is missing.
Fix: Treat optional fields as optional, log any event you couldn't process, and replay it once the handler's fixed.
How you'll know: A method you tried in test doesn't appear for live shoppers.
Fix: Payment methods are enabled per account and environment. Request them on the live account too before launch.
Adyen's interactive API reference at docs.adyen.com/api-explorer. It covers Checkout, Terminal, Management, platform and other APIs, plus their webhooks, version by version, with example requests and responses. Adyen built it on its OpenAPI specs so you can try requests as well as read them.
You can do either. Adyen publishes server libraries in languages including Node, Java, PHP, Python and .NET, and the REST API works from any language that can send HTTPS requests. Front-end checkout comes from the Adyen Web library, which holds Drop-in and Components.
Taking in-person payments on Adyen terminals. Your POS sends the terminal a payment request and gets the result back, either over the local network or through Adyen's cloud. It has its own section in the API Explorer, apart from the Checkout API that online payments use.
From the Customer Area: test at ca-test.adyen.com, live at ca-live.adyen.com, under Developers and then API credentials. Each credential holds a server-side API key, a client key for the browser, and the roles that decide which APIs it can call.
Yes. Adyen's test environment has its own Customer Area, credentials and endpoints, and no real money moves. Adyen also publishes Postman collections, which suit teams that would rather script their test calls than send them from the browser.
n-frames writes the server side once the request shape is known: the webhook handler that sets each order's real status, refunds and disputes passed back to your order system, and settlement data posted to your accounting system. It also moves a checkout from Drop-in to Components when the design outgrows it.