canonical: https://jentic.com/apis/adyen.com/adyen-fund-service

# Adyen Fund API

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.

## For AI agents

Move funds between marketplace accounts, pay out balances to account holders, and retrieve balances and transactions on Adyen's classic for-platforms integration.

## Scope

Does not handle online card acceptance, KYC onboarding, or modern Balance Platform transfers - use for classic platform fund movement and balance lookup only.

## Capabilities

- 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

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

Example prompt: 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

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

## Key resources

- **Account Holder Balances** — Pending and payable balances per account under an account holder
- **Transactions** — Historical transaction records with type, status, and PSP reference
- **Payouts** — Funds movements from marketplace accounts to account holder bank accounts
- **Funds Transfers** — Inter-account transfers within the marketplace, including refunds and reversals
- **Beneficiaries** — Designated successor accounts that inherit the balance of a closed account

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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

- **Adyen Account API** — Onboards and manages the account holders that the Fund API moves money between
- **Adyen Hosted Onboarding API** — Generates onboarding links for the same classic platform integration
- **Stripe API** — Stripe Connect transfers and payouts cover the same marketplace fund movement use cases
- **Adyen Classic Platforms Notifications** — Defines the webhook payloads for events on Fund API transfers and payouts

## FAQ

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