Adyen Checkout API

Name: Adyen Checkout API
Brand: Adyen Checkout API
Availability: InStock

✓ Official Vendor SpecPaymentsPayment ProcessingapiKey, basic26 EndpointsREST

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.

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 | sh

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 instance

Jentic 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

GET STARTED

Start building with Adyen Checkout API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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.

Time to first call

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.

Adyen Checkout API

Connect the Adyen Checkout API to your agent

Capabilities

Start building with Adyen Checkout API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs