For Agents
Submit, confirm, decline, and store details for third-party payouts on Adyen's classic platform, plus run instant card payouts.
Get started with Adyen Payout API in minutes using your preferred integration method.
# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
"jentic": {
"url": "https://api.jentic.com/mcp",
"auth": "oauth"
}
}
# Then ask your agent:
"submit an Adyen third-party payout"
# → Jentic returns the GET /events tool with parameter schema, agent executes.What an agent can do with Adyen Payout API API.
Store payout recipient details for later use via POST /storeDetail and combined store-and-submit via POST /storeDetailAndSubmitThirdParty
Submit a third-party payout for review via POST /submitThirdParty using a stored recipient
Approve a queued payout from a second credential via POST /confirmThirdParty
Reject a queued payout from a second credential via POST /declineThirdParty
GET STARTED
Use for: Store payout details for a marketplace seller's bank account, Submit a third-party payout to a stored recipient for $250, Approve a queued payout that another user submitted, Decline a payout that failed compliance review
Not supported: Does not authorise card payments, manage account holders, or handle disputes — use only for submitting, reviewing, and disbursing classic-platform payouts.
The Adyen Payout API is the classic-integration surface for storing payout details, submitting third-party payouts, and confirming or declining them with a separate review credential, plus running instant card payouts. The six endpoints implement the dual-credential flow Adyen requires for payouts: one credential stores details and submits a payout, a second credential confirms or declines it. Adyen has deprecated this API for new integrations and recommends the Transfers API for instant bank payouts and richer webhook signalling; the Payout API remains available for existing classic integrations.
Run an instant push-to-card payout via POST /payout when supported on the network and BIN
Use distinct API credentials for the submission and review steps to enforce dual control
Patterns agents use Adyen Payout API API for, with concrete tasks.
★ Marketplace Seller Payouts with Dual Control
Marketplaces operating on Adyen's classic platform use POST /submitThirdParty to queue a payout to a stored recipient, then a separate operator with the review credential calls POST /confirmThirdParty to release the funds or POST /declineThirdParty to reject it. This satisfies segregation-of-duties controls common in regulated payouts. Recipient bank details are stored once via POST /storeDetail and reused across submissions.
Call POST /submitThirdParty with recurringDetailReference, amount, and merchantAccount, then from a reviewer credential call POST /confirmThirdParty with the originalReference
Instant Push-to-Card Payouts
When a recipient needs funds in minutes rather than days, POST /payout runs a push-to-card payout against eligible debit networks. This is suitable for gig-economy daily settlement, insurance disbursement, and rebate payouts when the recipient's debit BIN supports the network. The classic Payout API supports this single-call model alongside the dual-control third-party flow.
Call POST /payout with card details, amount, recurring.contract, and merchantAccount to run a push-to-card payout
Recipient Detail Tokenisation
Storing recipient bank or card details once means subsequent payouts only carry a recurringDetailReference rather than raw account data. POST /storeDetail tokenises the details and returns a recurringDetailReference; POST /storeDetailAndSubmitThirdParty does both in one call, which is convenient when a new recipient onboards and immediately needs a payout. This reduces PII handling on the integrator side.
Call POST /storeDetail with bank account or card details and shopperReference to receive a recurringDetailReference for future payouts
AI Agent Payout Operations via Jentic
An operations agent that processes daily seller settlements searches Jentic for 'submit an Adyen third-party payout', loads the schema for /submitThirdParty, and executes per seller from the day's settlement file. A second agent or human reviewer with the review credential confirms each payout via /confirmThirdParty. Jentic isolates the two credentials so neither the submitter nor the reviewer ever sees the other's secret.
Search Jentic for 'submit an Adyen third-party payout', load the submitThirdParty schema, then execute one call per seller in the daily settlement file
6 endpoints — the adyen payout api is the classic-integration surface for storing payout details, submitting third-party payouts, and confirming or declining them with a separate review credential, plus running instant card payouts.
METHOD
PATH
DESCRIPTION
/submitThirdParty
Submit a payout for review
/confirmThirdParty
Approve a queued payout
/declineThirdParty
Reject a queued payout
/storeDetail
Tokenise recipient details
/storeDetailAndSubmitThirdParty
Tokenise and submit in one call
/payout
Run an instant push-to-card payout
/submitThirdParty
Submit a payout for review
/confirmThirdParty
Approve a queued payout
/declineThirdParty
Reject a queued payout
/storeDetail
Tokenise recipient details
/storeDetailAndSubmitThirdParty
Tokenise and submit in one call
Three things that make agents converge on Jentic-routed access.
Credential isolation
Both the submitter and reviewer credentials for Adyen Payout are stored encrypted in the Jentic vault as separate entries. Agents receive scoped tokens for one role at a time; raw API keys never appear in the agent's context, preserving the dual-control model.
Intent-based discovery
Agents search by intent (e.g., 'submit a third-party payout' or 'confirm an Adyen payout') and Jentic returns the matching submitThirdParty or confirmThirdParty operation with its input schema, so the agent picks the right endpoint without reading the deprecated-API documentation.
Time to first call
Direct Adyen Payout integration: 2-4 days for two-credential setup, payout state reconciliation, and recipient tokenisation. Through Jentic: under 1 hour — search, load, execute the flow.
Alternatives and complements available in the Jentic catalogue.
Adyen Transfers API
Modern Adyen payout surface that supersedes the deprecated Payout API
Choose Transfers API for any new payout integration; it covers more rails, instant bank payouts, and richer webhooks
Adyen Transfers API v3
Earlier major version of Transfers API that already supersedes Payout
Use when an integration is on Transfers v3 and not yet upgraded to v4
Adyen Payment API
Source of funds that the Payout API later disburses
Use Payment API to collect funds from buyers, then Payout API to settle to sellers on the same classic platform
Adyen Fund API
Move funds between platform accounts before payout
Use Fund API to consolidate or split balances on the classic platform before submitting payouts via Payout API
Specific to using Adyen Payout API API through Jentic.
What authentication does the Adyen Payout API use?
The API supports an API key in the X-API-Key header (ApiKeyAuth) and HTTP Basic auth (BasicAuth). Adyen requires two distinct credentials in production: one for storing and submitting payouts, another for confirming or declining them. Through Jentic, both credentials are stored encrypted and exposed only as scoped tokens at execution time.
Can I run an instant payout to a debit card with the Adyen Payout API?
Yes. POST /payout supports push-to-card payouts where the recipient's debit BIN and network allow it. Pass the card details, amount, and recurring.contract in the request. For broader instant payout coverage including bank rails, Adyen recommends migrating to the Transfers API.
Is the Adyen Payout API still recommended for new integrations?
No. Adyen has marked the Payout API as deprecated for new integrations and points to the Transfers API for richer payout state, instant bank payouts, and consolidated webhooks. Existing classic integrations continue to be supported, and this enrichment covers the v68 surface for those integrations.
What are the rate limits for the Adyen Payout API?
Adyen does not publish a fixed numeric rate limit for Payout in the spec; throughput is provisioned per merchant account through your contract and risk profile. If 429 responses appear, contact Adyen support to review the merchant account's payout limits.
How do I submit a third-party payout with the Adyen Payout API through Jentic?
Search Jentic for 'submit an Adyen third-party payout', load the submitThirdParty schema, then execute with recurringDetailReference, amount.value, amount.currency, and merchantAccount. From a separate reviewer credential, call confirmThirdParty with the returned pspReference. Get an account at https://app.jentic.com/sign-up.
Why does the API require two API credentials?
The dual-credential model implements segregation-of-duties: the credential that submits a payout cannot also confirm or decline it, which is a regulatory requirement for many payout flows. POST /submitThirdParty must be called from the submitter credential; POST /confirmThirdParty and POST /declineThirdParty must be called from a distinct review credential.
/payout
Run an instant push-to-card payout