Official vendor OpenAPI document · agent-readyPaymentsPayouts TransfersapiKey, basic8 EndpointsREST
For Agents
Move funds between marketplace accounts, pay out balances to account holders, and retrieve balances and transactions on Adyen's classic for-platforms integration.
Use for: I need to pay out a marketplace seller's balance to their bank account, Transfer commission from a seller account to the platform liable account, Refund a transfer that was sent to the wrong account, Get the current balance for a marketplace seller account holder
Not supported: Does not handle online card acceptance, KYC onboarding, or modern Balance Platform transfers - use for classic platform fund movement and balance lookup only.
Manage funds within an Adyen Classic Platforms (MarketPay) marketplace by transferring money between platform accounts, paying out balances to account holders, refunding earlier transfers, and retrieving balances and transaction lists. Designed for the classic for-platforms integration; new implementations should use the modern Balance Platform APIs instead. Operates on /cal/services/Fund/v6 in test and the equivalent live endpoint.
Install Jentic One Beta
Connect the Adyen Fund API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Fund 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-fund-service" | 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-fund-service" | 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 Fund API.
Transfer funds between platform accounts to settle splits, fees, or commissions
Pay out an account holder's balance to their registered bank account
Refund a previous funds transfer or all not-yet-paid-out transactions for an account
Retrieve the current balances of an account holder across pending and payable buckets
List historical transactions on an account with paging and date filters
Issue a direct debit request against an account holder's bank account
Designate a beneficiary account and shift the benefactor's balance on closure
Use Cases
Patterns agents use Adyen Fund API for, with concrete tasks.
★ Marketplace Seller Payouts
Pay marketplace sellers their accumulated balance on a defined schedule (daily, weekly, monthly) by calling /payoutAccountHolder against the seller's account holder code. Supports multi-currency payouts to bank accounts already attached through the Account API. Returns a PSP reference that ties the payout to subsequent webhook events for reconciliation.
POST /payoutAccountHolder with accountHolderCode seller_8421, accountCode acct_main, and amount currency EUR value 12500, then store the returned pspReference for reconciliation
Commission and Fee Splits
Move commission and platform fees from seller balances into the platform's liable account using /transferFunds. Useful when the marketplace charges a percentage on every settled transaction and needs that fee swept into operations weekly. The same endpoint also handles inter-seller transfers when the marketplace mediates refunds or returns.
POST /transferFunds with sourceAccountCode seller_8421, destinationAccountCode platform_liable, and amount currency EUR value 750 to settle the weekly commission
Balance and Reconciliation Reporting
Pull current balances and transaction history for marketplace accounts to build internal reconciliation reports without scraping the Customer Area UI. /accountHolderBalance returns pending and payable balances per account; /accountHolderTransactionList returns the underlying transaction records with paging and date filters. Suitable for daily reconciliation against the platform's own ledger.
POST /accountHolderTransactionList with accountHolderCode seller_8421 and a transactionListsForAccounts filter for the last 24 hours, then post the response into the reconciliation queue
AI Agent Treasury Operations
Operations agents trigger payouts, transfers, and balance checks through Jentic without raw access to the Adyen API key. The agent searches for 'pay out a marketplace account' via Jentic, receives the /payoutAccountHolder schema with accountHolderCode and amount fields, and executes the call. Credentials remain isolated in your Jentic One instance, with each call scoped to the operation requested.
Search Jentic for 'get Adyen account holder balance', load the schema, and POST /accountHolderBalance for accountHolderCode seller_8421 to surface the current payable balance to the operations dashboard
Key Endpoints
8 endpoints — manage funds within an adyen classic platforms (marketpay) marketplace by transferring money between platform accounts, paying out balances to account holders, refunding earlier transfers, and retrieving balances and transaction lists.
METHOD
PATH
DESCRIPTION
POST
/payoutAccountHolder
Pay out from an account to the account holder's bank
POST
/transferFunds
Transfer funds between platform accounts
POST
/refundFundsTransfer
Refund a prior funds transfer
POST
/refundNotPaidOutTransfers
Refund all not-yet-paid-out transactions for an account
POST
/accountHolderBalance
Get the balances of an account holder
POST
/accountHolderTransactionList
Get a paginated list of transactions
POST
/debitAccountHolder
Send a direct debit request to an account holder
POST
/setupBeneficiary
Designate a beneficiary account and transfer the benefactor balance
POST
/payoutAccountHolder
Pay out from an account to the account holder's bank
POST
/transferFunds
Transfer funds between platform accounts
POST
/refundFundsTransfer
Refund a prior funds transfer
POST
/refundNotPaidOutTransfers
Refund all not-yet-paid-out transactions for an account
POST
/accountHolderBalance
Get the balances of an account holder
POST
/accountHolderTransactionList
Get a paginated list of transactions
POST
/debitAccountHolder
Send a direct debit request to an account holder
POST
/setupBeneficiary
Designate a beneficiary account and transfer the benefactor balance
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.
F
Fund API
- Foundational (D+)48/100
100
Foundational Compliance67
Developer Experience & Jentic Compatibility27
AI-Readiness & Agent Experience94
Agent Usability30
Security77
AI DiscoverabilityPowered 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.
67
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
3%
Example Density
How richly the API is illustrated with examples.
90%
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.
27
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
58%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
49%
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).
77
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
77%
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 Fund API by hand means handling its X-API-Key or basic auth and targeting the classic CAL host for fund movement and balance lookups. Through Jentic you install once, import the Fund API from the API Directory, store the key once, and your agent calls it.
Permission scoping
The Fund API takes the account holder 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 getting an account holder balance or listing transactions. Because you pick the operations, money-moving calls like transferFunds or debitAccountHolder stay out unless you include them.
Credential isolation
Your Adyen X-API-Key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'pay out a marketplace seller' or 'get an account holder balance', and Jentic returns the matching Fund API 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 API
Stripe Connect transfers and payouts cover the same marketplace fund movement use cases
Choose Stripe Connect when starting a new marketplace; choose Adyen Fund API when extending an existing classic Adyen for Platforms integration
FAQs
Specific to using Adyen Fund API through Jentic.
What authentication does the Adyen Fund API use?
The Fund API accepts an API key in the X-API-Key header or HTTP Basic authentication with web service user credentials (typically ws@MarketPlace.YOUR_PLATFORM_ACCOUNT). Through Jentic, your X-API-Key is held encrypted in your Jentic One instance and agents authenticate with scoped tokens, keeping the raw key out of agent context.
Can I pay out in multiple currencies?
Yes. POST /payoutAccountHolder accepts an amount object with a currency code, and Adyen settles the payout in the destination bank account's currency where supported. Currency support depends on the bank account configured for the account holder; unsupported currencies are rejected with a validation error.
What are the rate limits for the Adyen Fund API?
Rate limits are tied to your platform's contract and typically sit in the tens of requests per second for transfer and payout operations on production. Excess requests return HTTP 429. Bulk payout flows should batch work, back off on rate limits, and contact your Adyen account manager for sustained higher volumes.
How do I check an account holder's balance through Jentic?
Search Jentic for 'get Adyen account holder balance' to find the POST /accountHolderBalance operation. Required fields are accountHolderCode, with an optional accountCode list to scope the response. Jentic loads the full schema and executes with vaulted credentials. Run it through Jentic One, the self-hosted execution layer.
Should new platforms use the Fund API or the Balance Platform API?
New implementations should use Adyen's Balance Platform APIs. The Fund API is part of the classic Adyen for Platforms integration (MarketPay) and remains supported for existing integrations, but the Balance Platform offers a more modern architecture with structured balance accounts, transfer routes, and richer event coverage.
Can I limit what my agent is allowed to do with the Adyen Fund API?
Yes. Because Jentic One is self-hosted and you decide which operations it exposes, you can restrict your agent to read-only calls such as accountHolderBalance and accountHolderTransactionList while withholding money-moving operations. The Fund API takes the account holder in the request body rather than a URL path, so money-moving calls like transferFunds, payoutAccountHolder, refundFundsTransfer, and debitAccountHolder stay out of reach unless you include them. Your X-API-Key is injected only at execution time and never enters the agent's context, so the agent can only invoke the operations your own rules permit.
GET STARTED