Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Payments / Adyen / Adyen Payout API
Adyen Payout API logo

Adyen Payout API

Browse all Adyen APIs
53
AI ReadinessFoundational (C-)53/100
See full scorecard
Official vendor OpenAPI document · agent-readyPaymentsPayouts TransfersapiKey, basic6 EndpointsREST

For Agents

Submit, confirm, decline, and store details for third-party payouts on Adyen's classic platform, plus run instant card payouts.

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.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Adyen Payout API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Payout 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-payout" | sh
2

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-payout" | 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 Payout 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

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

Use Cases

Patterns agents use Adyen Payout 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

Key Endpoints

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

POST

/submitThirdParty

Submit a payout for review

POST

/confirmThirdParty

Approve a queued payout

POST

/declineThirdParty

Reject a queued payout

POST

/storeDetail

Tokenise recipient details

POST

/storeDetailAndSubmitThirdParty

Tokenise and submit in one call

POST

/payout

Run an instant push-to-card payout

POST

/submitThirdParty

Submit a payout for review

POST

/confirmThirdParty

Approve a queued payout

POST

/declineThirdParty

Reject a queued payout

POST

/storeDetail

Tokenise recipient details

POST

/storeDetailAndSubmitThirdParty

Tokenise and submit in one call

POST

/payout

Run an instant push-to-card payout

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 Payout API

- Foundational (C-)
53/100
100
Foundational Compliance
70
Developer Experience & Jentic Compatibility
33
AI-Readiness & Agent Experience
94
Agent Usability
30
Security
75
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

70

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
5%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

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.

33

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
70%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

17%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

44%

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).

75

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Adyen Payout API by hand means handling its X-API-Key or basic auth, targeting the classic PAL host, and preserving the submitter and reviewer dual-control roles yourself. Through Jentic you install once, import the Payout API from the API Directory, store each role credential once, and your agent calls it.

Permission scoping

The Payout API takes the payout details in the request body rather than a resource id in the URL path, so you limit the agent to the operations it needs, such as submitting a third-party payout. Because you pick the operations, confirm and decline stay out unless you include them, which lets you keep the two roles separate.

Credential isolation

Your Adyen submitter and reviewer credentials are stored once, encrypted, as separate entries 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 'submit a third-party payout' or 'confirm an adyen payout', and Jentic returns the matching Payout 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

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

Alternative

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

Complementary

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

Complementary

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

FAQs

Specific to using Adyen Payout 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 through Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Adyen Payout API?

Yes. Because you run Jentic One yourself, you choose exactly which of the six Payout operations the agent can call, so you can allow POST /submitThirdParty and POST /storeDetail while leaving POST /confirmThirdParty and POST /declineThirdParty out. Since this API takes the payout details in the request body rather than a resource id in the URL, the operations you select are the boundary the agent works within. That lets you keep the submitter and reviewer roles separate under your own rules, with each credential injected only for the operations you permit.

GET STARTED

Start building with Adyen Payout API

Explore with Jentic One
View OpenAPI Document