27 APIs across 4 product groups.
What agents get from Jentic-routed access to this vendor.
Setup
Wiring Adyen by hand means handling API key or basic auth for each surface, targeting the right test or live host per API, and threading identifiers such as companyId, accountHolderId, and pspReference through a large operation set. Through Jentic you install once, add the Adyen APIs you need from the Jentic API Directory, store the key once, and your agent calls them.
Permission scoping
Because you run Jentic One yourself, your own rules decide which Adyen operations and credentials the agent may use. Many APIs carry the resource id in the URL path, so a rule can pin the agent to one company, account holder, or transfer, while high-impact operations such as initiating transfers, issuing cards, or generating API keys stay off the agent's list unless you add them.
Credential isolation
Specific to using Adyen APIs through Jentic.
Which Adyen APIs should I use for a new integration?
For new online payments use the Checkout API rather than the classic Payment API. For platform money movement use the Transfers API v4 rather than the deprecated Payout and Fund APIs. For onboarding and verification on the modern Balance Platform use Legal Entity Management and the Configuration API rather than the classic Account and Hosted Onboarding APIs. The classic surfaces remain available for existing integrations that already target them.
Does one API key work across all of Adyen's APIs?
The APIs share the same authentication model, an API key in the X-API-Key header or HTTP Basic auth, but the key must be generated with the roles for each surface. Balance Platform APIs such as Transfers and Configuration also accept a clientKey for client-side flows. In practice you generate a key in the relevant Customer Area and grant it the roles the operations require.
What is the difference between the classic and Balance Platform APIs?
The classic for-platforms APIs, including Account, Fund, Payout, and Hosted Onboarding, model marketplaces the original way. The modern Balance Platform, including the Configuration, Legal Entity Management, and Transfers APIs, models the same concepts as legal entities, account holders, balance accounts, and transfers. New platform integrations should build on the Balance Platform surface.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.
For Agents
Across Adyen's APIs an agent can create and modify online and in-person payments, onboard and KYC-verify legal entities, provision balance accounts and issue cards, move funds and run payouts, defend or accept disputes, and configure merchant accounts, terminals, and webhooks. It can also parse Adyen webhook payloads to react to payment, transfer, configuration, and report events.
Adyen exposes online payments, physical terminals, and the full Balance Platform for marketplaces and platforms behind one processor and one credential model, so a business can onboard sellers, hold and move their funds, issue cards, and take payments across channels without stitching together separate acquiring, banking, and KYC providers. The classic server-to-server APIs coexist with the modern Balance Platform surface, so both legacy and greenfield integrations are covered.
Use for: Automating online and in-person card, wallet, and local payment method transactions; marketplace and platform onboarding, KYC, fund movement, card issuing, payouts, dispute response, and account and webhook configuration on Adyen
Not supported: banking license, fraud risk scoring, tax filing, accounting ledger, customer support desk
Credentials: Most Adyen APIs authenticate with a single API key in the X-API-Key header or HTTP Basic auth, though the key must be generated with the roles for each surface and some Balance Platform APIs also accept a clientKey for client-side flows.
All 27 Adyen OpenAPI specs are vendor-official and indexed by Jentic, kept validated and agent-ready.
Adyen is a single payments platform that spans online checkout, in-person terminals, marketplace and platform money movement, KYC and legal entity verification, and account configuration. Its APIs let a business authorise and modify card, wallet, and local payment method transactions, drive point-of-sale terminals, onboard and verify sellers on Adyen for Platforms, move funds between balance accounts and bank accounts, respond to chargebacks, and configure merchant accounts, stores, and webhooks from one integration.
| I want to... | Use | Why |
|---|---|---|
| Take an online card, wallet, or local payment method payment | Adyen Checkout API | Checkout is the current unified online payment surface with sessions, payment links, and modifications; PaymentService is the older classic server-to-server card interface |
| Authorise a card payment on the classic server-to-server integration | Adyen Payment API | Use only when an existing classic integration targets it; new online integrations should use CheckoutService-v71 |
| Configure merchant accounts, stores, terminals, and webhooks | Adyen Management API (v3) | v3 is the actively maintained Management surface with Android app uploads; ManagementService v1 is the earlier version kept for existing integrations |
| Move funds between balance accounts and to bank accounts | Adyen Transfers API | Transfers v4 is the current Balance Platform money-movement surface; PayoutService and FundService are the deprecated classic-platform payout paths |
| Pay out balances on a marketplace | Adyen Payout API | Classic for-platforms payout surface, superseded by TransferService-v4 for new Balance Platform integrations |
| Onboard and verify a seller or business | Adyen Legal Entity Management API | Legal Entity Management handles KYC and KYB on the modern Balance Platform; AccountService and HopService cover the classic for-platforms onboarding model |
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen APIs, 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com" | shStep 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" | 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.
Once connected, ask your agent something like: “automate payments and payouts on Adyen”.
Each workflow spans multiple Adyen APIs. Jentic routes each operation to the right API automatically.
Onboard a marketplace seller and pay them out
Verify a new seller as a legal entity, provision their balance account and payment instrument, then move their settled proceeds to a bank account. Legal Entity Management runs the KYC and KYB checks, the Configuration API creates the account holder, balance account, and any issued card, and the Transfers API moves funds once verification clears.
Create the legal entity and check verification errors via LegalEntityService, create the account holder and balance account via BalancePlatformService, then initiate the payout via TransferService-v4 once verification clears
Adyen Legal Entity Management API + Adyen Configuration API + Adyen Transfers API
Configure a merchant account then take payments
Provision a merchant account with its payment methods and webhook subscriptions, then process online payments against it. The Management API v3 configures the merchant account, payment methods, and webhooks, and the Checkout API authorises and captures the resulting payments.
Create the merchant account, configure payment methods, and add a webhook subscription via ManagementService-v3, then create a session and authorise the payment via CheckoutService-v71
Adyen Management API (v3) + Adyen Checkout API
Process a payment and defend the resulting chargeback
Authorise a payment, listen for the dispute webhook, then respond to the chargeback with evidence. Checkout authorises and captures the payment, the Management Webhooks spec signals when a dispute arrives, and the Disputes API retrieves defense reasons and submits the response.
Capture the payment via CheckoutService-v71, parse the dispute event from ManagementNotificationService-v1, then retrieve defense reasons and defend the dispute via DisputeService-v30
Adyen Checkout API + Adyen Disputes API + Adyen Management Webhooks
Run one payment stack across web and physical store
Take online payments and in-person terminal payments for the same merchant while managing the terminal fleet. Checkout handles card-not-present web and app payments, the Terminal API drives in-person transactions, and POS Terminal Management assigns and reassigns terminals across stores.
Provision terminals to stores via TfmAPIService, take online payments via CheckoutService-v71 and in-person payments via TerminalAPI-v1, and reconcile both at close of business
Adyen Checkout API + Adyen Terminal API + POS Terminal Management API
Your Adyen 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 the Jentic directory by intent such as 'take a payment on Adyen' or 'send an Adyen transfer to a bank account', and Jentic returns the matching Adyen operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Can I handle online and in-person payments through Adyen?
Yes. The Checkout API covers online card-not-present payments across cards, wallets, and local payment methods, while the Terminal API drives in-person payments on Adyen-supplied point-of-sale terminals. POS Terminal Management provisions and assigns the terminal hardware. Using both lets one merchant run a single payment stack across web, app, and physical store.
How do webhooks fit into the Adyen APIs?
Several REST APIs pair with a webhook specification that describes the events they emit. The Management, Configuration, Transfer, and classic platform webhook specs let an agent parse the payloads Adyen sends when payments, transfers, configuration, or reports change, so a workflow can react asynchronously to actions taken through the REST APIs.
Does Adyen support marketplaces and card issuing?
Yes. Adyen for Platforms lets a marketplace or platform onboard sellers as legal entities, hold their funds in balance accounts, issue physical and virtual cards as payment instruments, apply transaction rules, and move money with the Transfers API. The Configuration and Legal Entity Management APIs together model the full platform structure.
All 4 are in the Jentic catalogue with the same one-credential, intent-search pattern.