Adyen Transfers API
Browse all Adyen APIs✓ Official Vendor SpecPaymentsPayouts TransfersapiKey, basic, clientKey11 EndpointsREST
For Agents
Initiate, list, look up, approve, cancel, and return transfers between balance accounts and third-party banks on Adyen's Balance Platform.
Use for: Transfer funds from a balance account to a third-party bank account, List all transfers initiated in the last 24 hours, Look up the details and status of a specific transfer, Approve a pending dual-control transfer queued for review
Not supported: Does not authorise card payments, manage balance account configuration, or onboard legal entities — use only for moving funds, listing transfers, approving them, and requesting capital grants on Adyen's Balance Platform.
The Adyen Transfers API v4 is the current major version of the Balance Platform interface for moving money between balance accounts, third-party bank accounts, and capital grants. The 11 endpoints initiate transfers, list and look up transfers and transactions, approve or cancel pending transfers, return a settled transfer, and request or inspect Adyen Capital grants. v4 adds GET /transfers list and GET /transfers/{id} on top of v3, enabling self-service reconciliation without polling individual transactions.
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
List transfers with filters via GET /transfers and look up a specific transfer via GET /transfers/{id}
Approve queued dual-control transfers via POST /transfers/approve and cancel queued transfers via POST /transfers/cancel
Return a 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 Settlement with Self-Service Reconciliation
Marketplaces on Adyen's Balance Platform call POST /transfers to move daily proceeds from the platform's holding balance account to each seller's bank account. With v4, GET /transfers returns the list of transfers initiated for the platform, filtered by date or status, so reconciliation can be done without iterating transactions. GET /transfers/{id} returns the latest state of any transfer for incident response.
Call POST /transfers per seller with category=bank, amount, counterparty.bankAccount, and balanceAccountId, then GET /transfers with createdSince filter for end-of-day reconciliation
Dual-Control Transfer Approval
Regulated payout flows enforce segregation of duties. POST /transfers initiated under a dual-control config returns a transferId in a pending state; a reviewer with the appropriate Balance Platform role calls POST /transfers/approve with that ID to release the transfer, or POST /transfers/cancel to reject it. Both endpoints accept a list of transferIds for batch operations, making it efficient to clear a batch of pending settlements after compliance review.
Call POST /transfers/approve with transferIds=[list of pending transfer IDs] to release queued transfers in a single batch
Refunds and Returns of Settled Transfers
When a transfer settled to the wrong destination or needs to be reversed, POST /transfers/{transferId}/returns creates a return that moves the funds back to the source balance account. Adyen handles the rail-level mechanics; the integration only needs the original transferId and the amount to return. GET /transfers/{id} confirms the state of the original transfer before and after the return.
Call POST /transfers/{transferId}/returns with amount.value and amount.currency to return a previously settled transfer to its source
AI Agent Settlement Operations via Jentic
An ops agent that processes a daily seller settlement run searches Jentic for 'send Adyen transfer to bank account', loads the schema for /transfers, and executes once per seller from the day's settlement file. After all transfers are queued, the agent calls GET /transfers with a date filter to confirm every transfer reached the executed state, and escalates any in failed or rejected states. Jentic injects X-API-Key from the encrypted vault.
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 and verify with GET /transfers
Key Endpoints
11 endpoints — the adyen transfers api v4 is the current major version of 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
GET
/transfers
List transfers with filters
GET
/transfers/{id}
Look up a transfer by ID
POST
/transfers/approve
Approve queued transfers
POST
/transfers/cancel
Cancel queued transfers
POST
/transfers/{transferId}/returns
Return a settled transfer
GET
/transactions
List transactions
POST
/grants
Request a capital grant payout
POST
/transfers
Initiate a transfer
GET
/transfers
List transfers with filters
GET
/transfers/{id}
Look up a transfer by ID
POST
/transfers/approve
Approve queued transfers
POST
/transfers/cancel
Cancel queued transfers
POST
/transfers/{transferId}/returns
Return a settled transfer
GET
/transactions
List transactions
POST
/grants
Request a capital grant payout
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 Balance Platform dual-control configuration on top.
Intent-based discovery
Agents search by intent (e.g., 'send a transfer to a bank account' or 'list Adyen transfers') and Jentic returns the matching /transfers 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 v4 integration: 3-5 days for Balance Platform onboarding, transfer state machine handling, and reconciliation tooling. 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 v4 use?
The spec declares ApiKeyAuth (X-API-Key header), BasicAuth, and a clientKey scheme. 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 at runtime.
What does v4 add over v3?
v4 adds GET /transfers and GET /transfers/{id} alongside the existing POST /transfers and the approve, cancel, and returns endpoints. This means integrations can list and look up transfers directly without iterating through transactions, which simplifies reconciliation and incident response.
Can I send a transfer to a third-party bank account?
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 via GET /transfers/{id}.
How do I send a transfer with the Adyen Transfers API v4 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 v4?
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, contact Adyen support to review the platform's transfer quota.
How do I return a settled transfer?
POST /transfers/{transferId}/returns creates a return that moves the funds back to the source balance account. Pass the transferId in the path and amount.value with amount.currency in the body. Use GET /transfers/{id} before and after to confirm the original transfer's state has changed.
GET STARTED