Official vendor OpenAPI document · agent-readyPaymentsPayment ProcessingapiKey, basic26 EndpointsREST
For Agents
Initiate and authorise online payments across cards, wallets, and local methods, plus refunds, captures, payment links, and recurring billing.
Use for: Process a card payment with 3D Secure authentication, Create a hosted payment link for an invoice, Capture a previously authorised payment, Refund a settled card payment
Not supported: Does not handle balance platform configuration, BIN lookup, settlement reporting, or in-person POS terminals - use for online payment authorisation, modifications, and recurring tokens only.
The Adyen Checkout API is Adyen's primary surface for initiating and authorising online payments - cards (including 3D Secure), mobile wallets, local payment methods, and recurring billing. The 26 endpoints in v70 cover the full payment lifecycle: list available payment methods for a session, create payments, post payment details for redirects and 3DS challenges, capture and cancel authorisations, refund, manage payment links, handle Apple Pay sessions, support recurring stored details, and process orders for partial-method splits and donations.
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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com%2Fadyen-checkout" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com%2Fadyen-checkout" | 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 a payment via POST /payments with card, wallet, or local payment method details
Submit additional payment details (3DS challenge results, redirect returns) via POST /payments/details
Capture, cancel, refund, or reverse an authorised payment using the modifications endpoints
Generate hosted payment links via POST /paymentLinks for invoicing and async checkout flows
Create Apple Pay merchant sessions via POST /applePay/sessions for in-app and web Apple Pay checkouts
Use POST /sessions to launch a Drop-in or Components session that handles payment method selection client-side
Manage stored payment details and recurring tokens for subscription billing
Use Cases
Patterns agents use Adyen Checkout API for, with concrete tasks.
★ Card Checkout with 3D Secure
The classic card-payment flow uses POST /sessions to launch a Drop-in or Components session, then POST /payments and POST /payments/details to handle the 3DS2 round-trip. Adyen returns the resultCode (Authorised, ChallengeShopper, RedirectShopper) and the front end follows the prescribed step. The API handles 135+ payment methods and 100+ currencies with the same surface.
Call POST /payments with paymentMethod.type=scheme, encryptedCardNumber, amount, and merchantAccount, then if resultCode=ChallengeShopper post the 3DS challenge result to POST /payments/details
Hosted Payment Links for Invoicing
When a payment cannot be collected synchronously - invoicing a customer, sending a quote - POST /paymentLinks generates a hosted Adyen-branded URL that the customer can open from email or SMS. The link supports the same 135+ methods, returns a webhook on completion, and can be voided with PATCH /paymentLinks/{linkId} if the invoice is cancelled.
Call POST /paymentLinks with amount, reference, expiresAt, and shopperEmail, then email the returned link.url to the customer
Recurring Subscription Billing
Subscription products tokenize a card on the first payment and reuse the recurringDetailReference for renewals. POST /payments with recurringProcessingModel=Subscription captures the token; subsequent renewals call POST /payments referencing the stored token, with no shopper interaction required. Stored details can be revoked via DELETE on the storedPaymentMethods resource.
Call POST /payments with shopperReference, recurringProcessingModel=Subscription, and storePaymentMethod=true on the first charge, then renewals call POST /payments referencing storedPaymentMethodId
Refunds and Modifications
Operational tools need to capture an authorisation, partially refund a settled payment, or reverse a pending one. The modifications endpoints - POST /payments/{paymentPspReference}/captures, /refunds, /reversals, /cancels - accept a pspReference and an amount, and Adyen handles the corresponding webhook acknowledgement asynchronously.
Call POST /payments/{paymentPspReference}/refunds with the original pspReference and the amount to refund, then track the refund webhook for confirmation
Agent-Driven Checkout via Jentic
A commerce agent can use Jentic to discover the right Checkout operation across 26 endpoints - payments, payment links, captures, refunds, sessions - and execute it with X-API-Key managed in your Jentic One instance. This is the highest-value surface in the Adyen catalogue for agent-driven workflows because of the breadth of operations and the criticality of the credentials.
Use Jentic to search 'process credit card payment adyen', load POST /payments, and execute it for the requested amount and card details
Key Endpoints
26 endpoints — the adyen checkout api is adyen's primary surface for initiating and authorising online payments - cards (including 3d secure), mobile wallets, local payment methods, and recurring billing.
METHOD
PATH
DESCRIPTION
POST
/payments
Initiate a payment
POST
/payments/details
Submit 3DS or redirect details
POST
/sessions
Create a Drop-in/Components checkout session
POST
/paymentLinks
Create a hosted payment link
POST
/cancels
Cancel a pending authorisation
POST
/applePay/sessions
Create an Apple Pay merchant session
POST
/orders
Create a multi-method order
POST
/donations
Process a donation alongside a payment
POST
/payments
Initiate a payment
POST
/payments/details
Submit 3DS or redirect details
POST
/sessions
Create a Drop-in/Components checkout session
POST
/paymentLinks
Create a hosted payment link
POST
/cancels
Cancel a pending authorisation
POST
/applePay/sessions
Create an Apple Pay merchant session
POST
/orders
Create a multi-method order
POST
/donations
Process a donation alongside a payment
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
A
Adyen Checkout API
- Foundational (D+)49/100
59
Foundational Compliance67
Developer Experience & Jentic Compatibility32
AI-Readiness & Agent Experience94
Agent Usability30
Security80
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
59
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: C+Signals: 4
95%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
0%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
42%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
67
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
6%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
62%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
32
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
68%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
27%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
32%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
30
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
30%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
80
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
80%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Adyen Checkout API by hand means handling its X-API-Key or basic auth, targeting the v70 checkout host, and assembling amount, paymentMethod, and reference fields for each payment. Through Jentic you install once, import the Checkout API from the API Directory, store the key once, and your agent calls it.
Permission scoping
This Checkout version takes the payment target in the request body for payments, cancels, and orders rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as processing a payment or creating a payment link. Because you pick the operations, cancels and donations stay out unless you include them.
Credential isolation
Your Adyen X-API-Key and basic auth credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'process a credit card payment' or 'create a payment link', and Jentic returns the matching Checkout operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Stripe Payment Intents covers an equivalent card, wallet, and recurring surface
Choose Stripe when the processor is Stripe rather than Adyen; Payment Intents has different idempotency and 3DS conventions
FAQs
Specific to using Adyen Checkout API through Jentic.
What authentication does the Adyen Checkout API use?
The API supports an apiKey scheme using the X-API-Key header and HTTP basic auth with Customer Area credentials. Through Jentic, the X-API-Key is stored encrypted in the vault and injected at request time, so agents calling POST /payments never hold the raw key.
Can I process refunds with the Adyen Checkout API?
Yes. POST /payments/{paymentPspReference}/refunds accepts the original payment's pspReference and the amount to refund (full or partial). Adyen confirms the refund asynchronously via the corresponding webhook.
What are the rate limits for the Adyen Checkout API?
The OpenAPI spec does not declare programmatic rate limits. Adyen documents per-merchant-account throughput limits in their developer portal - coordinate large surge events with your Adyen account manager and use idempotency keys on POST /payments and modifications.
How do I create a hosted payment link through Jentic?
Search Jentic for 'create adyen payment link', load the POST /paymentLinks operation, and execute it with amount, reference, expiresAt, and the shopperEmail. Jentic returns the structured response containing the link.url.
Can I tokenize a card for subscription billing?
Yes. On the first POST /payments call, set storePaymentMethod=true and pass shopperReference plus recurringProcessingModel=Subscription. Subsequent renewals POST /payments referencing the storedPaymentMethodId without shopper interaction.
How do I capture an authorisation and not just authorise it?
By default, set captureDelayHours appropriately on POST /payments, or call POST /payments/{paymentPspReference}/captures with the amount to capture. Auto-capture and manual-capture behaviour is controlled per merchant account in the Customer Area.
Can I limit what my agent is allowed to do with the Adyen Checkout API?
Yes. Jentic One is self-hosted by you, so your own rules decide which of the 26 Checkout operations and which credentials the agent may use. You can allow only the operations it needs, such as POST /payments to process a payment or POST /paymentLinks to create a hosted payment link, while keeping others like POST /cancels and POST /donations out of reach. Because this Checkout version takes the payment target in the request body rather than a resource id in the URL path, you scope access at the operation level and the agent can only call what you have granted.
GET STARTED