Adyen Checkout API
Adyen Checkout API
Adyen Checkout API is the modern payments API for new integrations — pairs with frontend drop-in components, auto-adapting to 250+ payment methods.
Frontend component auto-adapts to user region, showing correct payment methods
Still requires an Adyen contract (not open PaaS)
POST /v71/sessions to create a checkout session; render the drop-in component via web/iOS/Android SDK; after completion, GET /payments/result for final status.
Uptime · 30-day window
About this API
Adyen launched Checkout API in 2018 to compete with Stripe Checkout — the goal was easier integration. The core difference vs. Classic Payments API is integration complexity: Checkout API ships frontend drop-in components that auto-display the right payment methods based on user IP/language (Dutch users see iDEAL, Germans see Sofort, Brazilians see Boleto) — no per-method integration. The backend just creates a session and verifies results; 3DS2/SCA flows are handled by Adyen. For new projects this is the default choice. Underneath, it still uses Adyen's compliance and fraud engine.
What you can build
- 1Standard e-commerce checkout
- 2Subscription checkout (with SCA/3DS flows)
- 3Single integration for multiple local payment methods
- 4In-app payments for mobile
Strengths & limitations
Strengths
- Frontend component auto-adapts to user region, showing correct payment methods
- Built-in SCA/3DS2 flows — handles EU compliance
- More modern/cleaner than Classic Payments API
Limitations
- Still requires an Adyen contract (not open PaaS)
- Drop-in component has UI customization constraints
Example request
curl https://www.adyen.help/hc/en-us/community/topics/<endpoint>Getting started
POST /v71/sessions to create a checkout session; render the drop-in component via web/iOS/Android SDK; after completion, GET /payments/result for final status.
FAQ
Can I fully customize the drop-in component's CSS?+
You can theme colors, fonts, spacing — but layout structure is constrained; you can't fully replace component DOM.
Does Checkout API cover all Classic Payments functionality?+
Day-to-day cases: yes. A few specialized scenarios (some token operations) require falling back to Classic.
Technical details
- Auth type
- unknown
- Pricing
- unknown
- Protocols
- REST
- SDKs
- java, python, javascript, typescript, php, ruby, csharp, go
- Response time
- 635 ms
- Last health check
- 5/12/2026, 7:36:31 AM
More from Adyen
Adyen Balance Control API moves funds between merchant accounts within Adyen — for centralized fund management and reconciliation.
Adyen BIN Lookup API returns card info from the first 6-8 digits of a PAN (BIN) — issuing bank, country, card type (debit/credit), product type.
Adyen Checkout Utility API provides auxiliary operations for Checkout API — originKey generation, payment methods listing, status queries.
Adyen Data Protection API handles GDPR/privacy operations — right-to-be-forgotten, PII deletion, shopper data export.
Adyen Payments API is its flagship payment-processing API — authorize, capture, and refund across cards, local payment methods, and wallets.
Adyen Payouts API moves funds from a merchant account out to external bank accounts or cards — supports multiple local clearing rails.
Adyen Recurring API manages subscription card tokens — store, look up, and reuse tokens for subsequent card-not-present payments.
Adyen Test Card Service API generates test card numbers for sandbox payment testing — covers various issuer response scenarios.