Adyen Fund API

Name: Adyen Fund API
Brand: Adyen Fund API
Availability: InStock

✓ Official Vendor SpecPaymentsPayouts TransfersapiKey, basic8 EndpointsREST

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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 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

GET STARTED

Start building with Adyen Fund API

Explore with Jentic

View OpenAPI Document

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.

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

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.

Time to first call

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.

Adyen Fund API

Connect the Adyen Fund API to your agent

Capabilities

Start building with Adyen Fund API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs