Adyen Fund API

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

✓ Official Vendor SpecPaymentsPayouts 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.

Quickstart

Get started with Adyen Fund 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:
"pay out a marketplace seller balance on Adyen"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Adyen Fund API 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

GET STARTED

Start building with Adyen Fund API API

Explore with Jentic

View OpenAPI Spec

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 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 the Jentic vault, 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 though Jentic?

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

Credential isolation

Adyen X-API-Key credentials are stored encrypted in the Jentic MAXsystem vault. Agents call /payoutAccountHolder, /transferFunds, and balance endpoints through scoped tokens, so the raw API key never enters agent prompts or logs.

Intent-based discovery

Agents search by intent ('pay out a marketplace seller', 'transfer funds between accounts', 'get account holder balance') and Jentic returns the matching Fund API operation with its full request schema.

Time to first call

Direct integration: 3-7 days for auth, payout pipeline, transfer logic, and reconciliation reporting. Through Jentic: under 1 hour per operation — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Adyen Account API

Onboards and manages the account holders that the Fund API moves money between

Use the Account API to create account holders and bank accounts, then use the Fund API to move money on the resulting accounts

Complementary

Adyen Hosted Onboarding API

Generates onboarding links for the same classic platform integration

Use Hosted Onboarding to capture verification details and the Fund API to manage funds for the onboarded accounts

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

Complementary

Adyen Classic Platforms Notifications

Defines the webhook payloads for events on Fund API transfers and payouts

Use the notifications spec to subscribe to and parse webhook events for transfers and payouts triggered through the Fund API

FAQs

Specific to using Adyen Fund API 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 the MAXsystem vault 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. Sign up at https://app.jentic.com/sign-up to get started.

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.