Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Payments / Adyen / Adyen Transfers API
Adyen Transfers API logo

Adyen Transfers API

Browse all Adyen APIs
61
AI ReadinessAI-Aware (B-)61/100
See full scorecard
Official vendor OpenAPI document · agent-readyPaymentsPayouts 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.

Jentic One on GithubView OpenAPI Document

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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com%2Fadyen-transfers-v4" | sh
2

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fadyen.com%2Fadyen-transfers-v4" | 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 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

Jentic AI Readiness Score

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

T

Transfers API

- AI-Aware (B-)
61/100
76
Foundational Compliance
69
Developer Experience & Jentic Compatibility
69
AI-Readiness & Agent Experience
94
Agent Usability
25
Security
80
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
76

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
98%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

7%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

69

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4
2%

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

69

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: B+Signals: 4
63%

Description Coverage

Coverage of descriptions across API elements.

82%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

91%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

41%

Summary Coverage

Coverage of summaries across operations/tags/info.

94

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1
94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

25

Security

Trust, risk posture, and security compliance.

Grade: FSignals: 1
25%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

80

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1
80%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Adyen Transfers API by hand means handling its X-API-Key, basic, and clientKey auth, targeting the balance platform test host, and preserving any dual-control on money movement. Through Jentic you install once, import the Transfers API from the API Directory, store each credential once, and your agent calls it.

Permission scoping

Transfers puts the transfer id in the URL path for reads and returns (/transfers/{id}, /transfers/{transferId}/returns), so a rule can pin your agent to one transfer: it can read that transfer and request its return and nothing else. You choose the operations it may call, so creating transfers, approving, or requesting grants stays out unless you add them.

Credential isolation

Your Adyen X-API-Key, basic auth, and clientKey credentials are stored once, encrypted, as separate entries by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'send a transfer to a bank account' or 'list adyen transfers', and Jentic returns the matching Transfers operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Adyen Transfers API v3

→

Earlier major version of the Transfers API

Use v3 only when an existing integration is on it; choose v4 for any new integration

Alternative

Adyen Payout API (deprecated)

→

Classic-platform payout surface superseded by Transfers API

Choose Transfers API v4 for any new payout integration; Payout API is deprecated

Complementary

Adyen Balance Platform Configuration API

→

Configures balance accounts referenced by Transfers API

Use Balance Platform Configuration to create the balance accounts; use Transfers v4 to move money between them

Complementary

Adyen Legal Entity API

→

Onboards the legal entities that own the balance accounts

Use Legal Entity API to KYC the entity, then Transfers v4 to move funds for that entity

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 through Jentic One, the self-hosted execution layer.

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.

Can I limit what my agent is allowed to do with the Adyen Transfers API?

Yes. Because you run Jentic One yourself, your own rules decide which of the eleven operations the agent may call, so you can allow it to look up transfers via GET /transfers/{id} while keeping POST /transfers, POST /transfers/approve, and POST /grants off limits unless you add them. Since the transfer id sits in the URL path for reads and returns (/transfers/{id} and /transfers/{transferId}/returns), a rule can pin the agent to a single transfer, letting it read that transfer and request its return and nothing else. The credentials the agent is permitted to use are equally under your control, so it can only act within the scope you set.

GET STARTED

Start building with Adyen Transfers API

Explore with Jentic One
View OpenAPI Document