Adyen Checkout API
Browse all Adyen APIs✓ Official Vendor SpecPaymentsPayment ProcessingapiKey, basic26 EndpointsREST
For Agents
Create payment sessions, generate payment links, capture or refund authorised payments, and manage stored payment methods on Adyen with cards, wallets, and local payment methods.
Use for: I need to charge a customer's credit card with 3D Secure, Create a payment link for a one-off invoice, Capture a previously authorised payment, Refund a settled card transaction
Not supported: Does not handle marketplace account onboarding, KYC verification, or in-person terminal payments — use for online payment authorisation, modification, and payment links only.
Initiate and authorise online payments through Adyen's unified Checkout API, covering cards with 3D Secure, mobile wallets such as Apple Pay and Google Pay, and local payment methods like iDEAL and Sofort. The API exposes payment sessions, payment links, recurring tokens, donations, and modification operations (capture, cancel, refund) on a single integration. Version 71 of the API is reached via /v71/payments and related endpoints, with separate test and live environments.
Install Jentic One Beta
Connect the Adyen Checkout API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Checkout API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Adyen Checkout API.
Initiate card, wallet, and local payment method payments via /payments and /sessions
Generate hosted payment links with /paymentLinks and update their status when paid or expired
Capture, cancel, refund, or reverse authorised payments with the /captures, /cancels, /refunds, and /reversals modifications
Tokenise card details for recurring billing and disable stored payment methods on demand
Run 3D Secure 2 authentication flows including PaRes submission and result handling
Process donation transactions and look up active donation campaigns for charitable round-ups
Use Cases
Patterns agents use Adyen Checkout API for, with concrete tasks.
★ E-Commerce Card Checkout
Accept card payments on a web or mobile checkout with 3D Secure 2 authentication and automatic fallback to 3DS1 where issuers require it. The Checkout API drives the full flow: create a /sessions object for the Drop-in component, handle additional details via /payments/details, and capture or refund the resulting payment. Integration through the Drop-in takes one to two days for a standard card flow.
Create a /sessions object for amount 4999 EUR with returnUrl set to the merchant return page, then poll the resulting paymentPspReference for authorisation status
Hosted Payment Links
Generate sharable payment links to collect payment without building a full checkout, useful for invoices, phone orders, and ad-hoc charges. The /paymentLinks endpoint returns a hosted URL that supports cards and local payment methods, with status updates available via GET /paymentLinks/{linkId}. Setup takes under a day because no front-end work is required.
POST /paymentLinks with amount 25000 EUR, reference INV-2026-0421, and expiresAt 24 hours from now, then return the resulting url to the caller
Recurring and Subscription Billing
Tokenise a card on first payment and charge the stored token on each subsequent billing cycle without re-prompting the cardholder. The Checkout API exposes recurring tokens via /payments with shopperReference and storePaymentMethod, and disables them on cancellation through the /storedPaymentMethods endpoint. Suitable for SaaS, content subscriptions, and metered services that need scheduled charges.
Authorise a payment with shopperReference cust_8421 and storePaymentMethod true, then on the renewal date charge the recurring token via /payments with the stored payment method ID
AI Agent Checkout Automation
AI agents process and reconcile payments through Jentic without holding raw Adyen API keys. An agent searches for 'process a card payment' via Jentic, receives the /payments operation schema with required amount, paymentMethod, and reference fields, and executes the call. Captures, refunds, and status checks follow the same search-load-execute pattern, keeping credentials isolated in the Jentic vault.
Search Jentic for 'capture an authorised Adyen payment', load the schema, then call /payments/{paymentPspReference}/captures with the amount and reference for an existing pending authorisation
Key Endpoints
26 endpoints — initiate and authorise online payments through adyen's unified checkout api, covering cards with 3d secure, mobile wallets such as apple pay and google pay, and local payment methods like ideal and sofort.
METHOD
PATH
DESCRIPTION
POST
/sessions
Create a checkout session for the Drop-in or Components
POST
/payments
Authorise a payment with a payment method
POST
/payments/details
Submit additional payment details such as 3DS results
POST
/paymentLinks
Create a payment link
POST
/payments/{paymentPspReference}/captures
Capture an authorised payment
POST
/payments/{paymentPspReference}/refunds
Refund a captured payment
POST
/payments/{paymentPspReference}/cancels
Cancel an authorised payment
POST
/applePay/sessions
Get an Apple Pay merchant session
POST
/sessions
Create a checkout session for the Drop-in or Components
POST
/payments
Authorise a payment with a payment method
POST
/payments/details
Submit additional payment details such as 3DS results
POST
/paymentLinks
Create a payment link
POST
/payments/{paymentPspReference}/captures
Capture an authorised payment
POST
/payments/{paymentPspReference}/refunds
Refund a captured payment
POST
/payments/{paymentPspReference}/cancels
Cancel an authorised payment
POST
/applePay/sessions
Get an Apple Pay merchant session
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adyen X-API-Key credentials are stored encrypted in the Jentic MAXsystem vault. Agents call /payments and modification endpoints through scoped tokens, so the raw API key never lands in prompts, logs, or agent context.
Intent-based discovery
Agents search by intent ('process a card payment', 'capture a payment', 'create a payment link') and Jentic returns the matching Checkout operation with its full request schema, including amount, paymentMethod, and reference fields.
Time to first call
Direct Adyen Checkout integration: 3-10 days for auth, Drop-in wiring, webhook handling, and 3DS resolution. Through Jentic: under 1 hour for server-side flows — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Stripe offers comparable card, wallet, and local payment processing with PaymentIntents
Choose Stripe when you want a developer-first API and broad framework ecosystem; choose Adyen for stronger international acquiring and unified processing
FAQs
Specific to using Adyen Checkout API through Jentic.
What authentication does the Adyen Checkout API use?
The Checkout API accepts an API key in the X-API-Key header or HTTP Basic authentication with web service user credentials. Generate the key in your Adyen Customer Area. Through Jentic, the X-API-Key value is stored encrypted in the MAXsystem vault and agents call the API with scoped tokens, so the raw key never enters the agent context or logs.
Can I run 3D Secure authentication through the Checkout API?
Yes. Submit the initial authorisation through POST /payments with the cardholder's payment method. If the issuer requires 3DS, the response returns an action object that the front end resolves, then you complete the flow by POSTing the result to /payments/details. Both 3DS2 native and redirect flows are supported on v71.
What are the rate limits for the Adyen Checkout API?
Adyen applies per-endpoint rate limits tied to your merchant account contract, typically into the hundreds of requests per second for /payments on production. Test environment limits are lower. Exceeded limits return HTTP 429 with a retry hint, and Adyen's account team raises limits on request for high-volume merchants.
How do I capture an authorised payment through Jentic?
Search Jentic for 'capture an Adyen payment' to find the POST /payments/{paymentPspReference}/captures operation. Required fields are the original pspReference in the path plus an amount object and merchantReference in the body. Jentic loads the full schema and executes the call. Sign up at https://app.jentic.com/sign-up to get started.
Does the Checkout API support payment links and Apple Pay?
Yes. Payment links are created with POST /paymentLinks and return a hosted URL covering cards and local methods. Apple Pay sessions are negotiated server-side via POST /applePay/sessions, returning the session payload that the iOS or web Apple Pay button needs to present the sheet to the shopper.
How do I refund a captured Checkout payment?
Call POST /payments/{paymentPspReference}/refunds with the captured amount and a merchantReference. Partial refunds are supported by passing a value lower than the captured total. The refund pspReference returned in the response is the identifier for matching webhook notifications and reconciliation entries.
GET STARTED