Adyen Transfers API
Browse all Adyen APIs✓ Official Vendor SpecPaymentsPayouts TransfersapiKey, basic, clientKey9 EndpointsREST
For Agents
Move funds between balance accounts and third-party banks, approve or cancel transfers, return settled transfers, and request capital grants on Adyen's Balance Platform.
Use for: Transfer funds from a balance account to a third-party bank account, Approve a pending dual-control transfer queued for review, Cancel a pending transfer that has not yet executed, Return a recently settled transfer back to the source
Not supported: Does not authorise card payments, manage balance account configuration, or onboard legal entities — use only for moving funds, approving transfers, and requesting capital grants on Adyen's Balance Platform.
The Adyen Transfers API v3 is the Balance Platform interface for moving money between balance accounts, third-party bank accounts, and capital grants. The nine endpoints initiate transfers, approve or cancel pending transfers, return a settled transfer, list and inspect transactions, and request or look up Adyen Capital grants. It is the modern replacement for the deprecated classic Payout API and supports instant payouts, third-party bank transfers, and dual-control approval where required.
Install Jentic One Beta
Connect the Adyen Transfers API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Transfers 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
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 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 Transfers API.
Initiate a transfer from a balance account to a third party or another balance account via POST /transfers
Approve a queued, dual-control transfer via POST /transfers/approve and cancel one via POST /transfers/cancel
Return a previously settled transfer to its source via POST /transfers/{transferId}/returns
List or look up transactions on the Balance Platform via GET /transactions and GET /transactions/{id}
Request a capital grant payout via POST /grants and inspect grants via GET /grants and GET /grants/{id}
Authenticate using API key (X-API-Key), basic auth, or a clientKey scheme as declared in the spec
Use Cases
Patterns agents use Adyen Transfers API for, with concrete tasks.
★ Marketplace Seller Settlement
Marketplaces on Adyen's Balance Platform call POST /transfers to move daily proceeds from the platform's holding balance account to each seller's connected bank account. The Transfers API supports instant rails where the receiving country and bank allow, and falls back to standard rails otherwise. GET /transactions reconciles the resulting movements against the platform's expected ledger.
Call POST /transfers with category=bank, amount.value, amount.currency, counterparty.bankAccount, and balanceAccountId for the seller, then GET /transactions for reconciliation
Dual-Control Transfer Approval
Regulated payout flows require segregation of duties. POST /transfers initiated under a dual-control config returns a transferId in a pending state; a separate user with approval rights calls POST /transfers/approve with the transferId, or POST /transfers/cancel to reject. The classic Payout API equivalent required two distinct API credentials; on the Balance Platform the same control is enforced via Balance Platform users and roles.
Call POST /transfers/approve with the transferId returned from the original POST /transfers call to release the queued transfer for execution
Capital Grant Payouts
Adyen Capital lets eligible merchants take a financing grant repaid from future card receipts. POST /grants requests a grant payout to the merchant's balance account, GET /grants/{id} returns the grant's status and outstanding repayment, and GET /grants lists the merchant's capital account history. This is the integration surface for marketplaces and platforms offering Capital to their sellers.
Call POST /grants with grantOfferId and counterparty.balanceAccount.balanceAccountId to request a Capital grant payout for the merchant
AI Agent Payout Operations via Jentic
An ops agent that processes a daily settlement run searches Jentic for 'send Adyen transfer to bank account', loads the schema for /transfers, and executes per seller from the day's settlement file. Jentic injects X-API-Key from the encrypted vault and the agent never holds the raw secret. The returned transferId is recorded in the operations ledger, and a separate reviewer agent or human approves via /transfers/approve where dual control is configured.
Search Jentic for 'send an Adyen transfer to a bank account', load the transfers schema, then execute one call per seller in the daily settlement file
Key Endpoints
9 endpoints — the adyen transfers api v3 is the balance platform interface for moving money between balance accounts, third-party bank accounts, and capital grants.
METHOD
PATH
DESCRIPTION
POST
/transfers
Initiate a transfer
POST
/transfers/approve
Approve queued transfers
POST
/transfers/cancel
Cancel queued transfers
POST
/transfers/{transferId}/returns
Return a settled transfer
GET
/transactions
List transactions
GET
/transactions/{id}
Get a transaction by ID
POST
/grants
Request a capital grant payout
GET
/grants/{id}
Get a grant by ID
POST
/transfers
Initiate a transfer
POST
/transfers/approve
Approve queued transfers
POST
/transfers/cancel
Cancel queued transfers
POST
/transfers/{transferId}/returns
Return a settled transfer
GET
/transactions
List transactions
GET
/transactions/{id}
Get a transaction by ID
POST
/grants
Request a capital grant payout
GET
/grants/{id}
Get a grant by ID
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Adyen API keys, basic-auth credentials, and clientKey values are stored encrypted in the Jentic vault as separate entries. Agents receive scoped access tokens at execution time — the raw X-API-Key value never enters the agent context, preserving any dual-control configuration on top.
Intent-based discovery
Agents search by intent (e.g., 'send a transfer to a bank account' or 'request a capital grant') and Jentic returns the matching /transfers or /grants operation with its full input schema, so the agent picks the right Balance Platform endpoint without crawling the docs.
Time to first call
Direct Adyen Transfers v3 integration: 3-5 days for Balance Platform onboarding, transfer state machine handling, and webhook reconciliation. Through Jentic: under 1 hour — search, load, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Adyen Transfers API through Jentic.
What authentication does the Adyen Transfers API v3 use?
The spec declares ApiKeyAuth (X-API-Key header), BasicAuth, and a clientKey scheme. In production the X-API-Key model is the standard server-side choice; the clientKey is used for client-side flows where applicable. Through Jentic, credentials are stored encrypted in the vault and only a scoped execution token is exposed to the agent.
Can I send a transfer to a third-party bank account with the Transfers API?
Yes. POST /transfers accepts a counterparty.bankAccount object describing the destination IBAN or account number, plus amount, balanceAccountId, and category. Adyen routes the transfer over the appropriate rail (instant where supported, standard otherwise) and returns a transferId for tracking.
How do I approve or cancel a pending transfer?
When dual control is configured, POST /transfers returns a transferId in a pending state. A reviewer with the right role calls POST /transfers/approve with that transferId to release the transfer, or POST /transfers/cancel to reject it. Both endpoints accept a list of transferIds for batch approval or rejection.
How do I send a transfer with the Adyen Transfers API through Jentic?
Search Jentic for 'send an Adyen transfer to a bank account', load the transfers schema, then execute with category=bank, amount, counterparty.bankAccount, and balanceAccountId. Jentic injects X-API-Key from the encrypted vault. Get an account at https://app.jentic.com/sign-up.
What are the rate limits for the Adyen Transfers API?
Adyen does not publish a fixed numeric rate limit in the spec; throughput is provisioned per balance platform and risk profile. If 429 responses appear in production, contact Adyen support to review the platform's transfer quota.
Should I use Transfers v3 or v4 for new integrations?
Adyen recommends the latest major version for new integrations; v4 adds GET /transfers list and GET /transfers/{id} alongside refinements to existing endpoints. Use v3 only when an existing integration is already on it; new integrations should target v4.
GET STARTED