Adyen Balance Control API
Browse all Adyen APIs48
AI ReadinessFoundational (D+)48/100
Official vendor OpenAPI document · agent-readyPaymentsPayouts TransfersapiKey, basic1 EndpointsREST
For Agents
Transfer funds between two merchant accounts on the same Adyen legal entity using a single balanceTransfer call.
Use for: Transfer funds between two of my Adyen merchant accounts, Rebalance settlement merchant accounts before a payout run, Move commission from a parent merchant account to a sub-merchant account, Correct a misrouted settlement by transferring funds back to the right merchant account
Not supported: Does not handle card payments, payouts to bank accounts, account holder management, or cross-legal-entity transfers - use for internal merchant-account-to-merchant-account transfers only.
The Adyen Balance Control API moves funds between merchant accounts that belong to the same legal entity inside one Adyen company account. It exposes a single POST /balanceTransfer endpoint that initiates a transfer with a source merchant account, destination merchant account, amount, and idempotency key. The API is designed for treasury operations on Adyen's classic platform - rebalancing settlement merchant accounts before payouts, reallocating commission, or correcting misrouted funds - and is separate from the Balance Platform Configuration API used by Adyen for Platforms customers.
Install Jentic One Beta
Connect the Adyen Balance Control API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adyen Balance Control 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-balance-control" | sh2
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-balance-control" | 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 Balance Control API.
Move funds between merchant accounts under one Adyen company account using POST /balanceTransfer
Specify source and destination merchant account codes plus amount and currency in a single request
Pass an idempotency key (merchantReference) so retries do not create duplicate transfers
Authenticate with an X-API-Key header or basic auth credentials issued in the Customer Area
Use the test endpoint host before switching to the live PAL host for production transfers
Use Cases
Patterns agents use Adyen Balance Control API for, with concrete tasks.
★ Treasury Rebalancing Between Merchant Accounts
Adyen merchants who run multiple merchant accounts under one legal entity need to rebalance funds before payouts, after disputes, or to fund a new account. The Balance Control API's POST /balanceTransfer endpoint moves a specified amount from one merchant account to another in a single call, with an idempotency key to prevent duplicate movements when retries occur.
Call POST /balanceTransfer with sourceMerchantAccount=AcmeRetail, destinationMerchantAccount=AcmeWholesale, amount {value:50000, currency:EUR}, and a unique merchantReference, then return the pspReference
Commission and Revenue-Share Allocation
Marketplaces and platform operators on Adyen's classic platform often collect funds into a single capture merchant account and then split commission across operating accounts. The Balance Control API enables that split with a sequence of /balanceTransfer calls - one per recipient - without involving Adyen for Platforms or external bank rails.
For each commission recipient, call POST /balanceTransfer from the capture merchant account to the recipient merchant account with the calculated share amount and a per-transfer merchantReference
Idempotent Correction of Misrouted Settlements
When a settlement lands on the wrong merchant account, finance teams need a safe way to move funds back without risk of duplicate corrections. The Balance Control API accepts a merchantReference that Adyen treats as an idempotency key - replaying the same call with the same reference returns the original result rather than creating a second transfer.
Replay POST /balanceTransfer with the same merchantReference used in the original failed correction and confirm the response returns the existing pspReference rather than creating a new transfer
Agent-Driven Treasury Operations via Jentic
Finance agents that run scheduled rebalancing or react to alerts can use Jentic to discover and execute Balance Control transfers without hand-rolling Adyen client code. The agent searches Jentic for a transfer intent, loads the operation schema, and executes the call with the X-API-Key managed inside your Jentic One instance - the agent context never holds the raw credential.
Use Jentic to search for 'transfer funds between adyen merchant accounts', load the balanceTransfer operation, and execute it with the source, destination, amount, and merchantReference for the scheduled rebalance
Key Endpoints
1 endpoints — the adyen balance control api moves funds between merchant accounts that belong to the same legal entity inside one adyen company account.
METHOD
PATH
DESCRIPTION
POST
/balanceTransfer
Transfer funds between two merchant accounts under one company account
POST
/balanceTransfer
Transfer funds between two merchant accounts under one company account
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.
A
Adyen Balance Control API
- Foundational (D+)48/100
100
Foundational Compliance58
Developer Experience & Jentic Compatibility26
AI-Readiness & Agent Experience94
Agent Usability30
Security100
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
100
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: A+Signals: 4
99%
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).
100%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
58
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: C+Signals: 4
8%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
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.
26
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
63%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
0%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
43%
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.
30
Security
Trust, risk posture, and security compliance.
Grade: FSignals: 1
30%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
100
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A+Signals: 1
100%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Adyen Balance Control API by hand means handling its X-API-Key or basic auth and targeting the classic PAL host for a call that moves money. Through Jentic you install once, import the Balance Control API from the API Directory, store the key once, and your agent calls it.
Permission scoping
Balance Control takes the source and destination merchant accounts in the request body rather than a resource id in the URL path, so you limit the agent to the single operation it needs, the balance transfer. Because you pick the operations, this surface exposes nothing beyond that transfer.
Credential isolation
Your Adyen X-API-Key and basic auth credentials are stored once, encrypted, 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 'transfer funds between adyen merchant accounts', and Jentic returns the balanceTransfer 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
Stripe
Stripe Treasury and Connect cover comparable internal balance and transfer flows
Choose Stripe when the underlying processor is Stripe rather than Adyen; Balance Control only operates inside the Adyen network
FAQs
Specific to using Adyen Balance Control API through Jentic.
What authentication does the Adyen Balance Control API use?
The API supports two schemes: an apiKey scheme using the X-API-Key header, and HTTP basic auth with a Customer Area username and password. Through Jentic, the X-API-Key is stored in the encrypted vault so agents call balanceTransfer without ever holding the raw credential.
Can I transfer funds across different Adyen company accounts with this API?
No. The Balance Control API only moves funds between merchant accounts that share the same legal entity under one Adyen company account. Cross-company or cross-legal-entity movement requires Adyen for Platforms and the Balance Platform Transfer API.
What are the rate limits for the Adyen Balance Control API?
The OpenAPI spec does not declare programmatic rate limits. Adyen documents per-merchant-account throughput limits in their developer portal - coordinate large rebalancing batches with your Adyen account manager and use idempotent merchantReference values so retries are safe.
How do I trigger a balance transfer through Jentic?
Search Jentic for 'transfer funds between adyen merchant accounts', load the POST /balanceTransfer operation, and execute it with sourceMerchantAccount, destinationMerchantAccount, amount, and a unique merchantReference. Jentic returns the structured response including the pspReference.
Is the merchantReference field used for idempotency?
Yes. Replaying POST /balanceTransfer with the same merchantReference returns the original transfer's pspReference rather than creating a duplicate transfer, which makes it safe to retry on network failures or agent timeouts.
Can I limit what my agent is allowed to do with the Adyen Balance Control API?
Yes. Because Jentic One is self-hosted and you decide which operations your agent may call, you can grant it only the single POST /balanceTransfer operation this API exposes and nothing else. The source and destination merchant accounts travel in the request body rather than a resource path, so scoping the agent to just the balance transfer keeps the surface limited to moving funds between accounts. Your own rules also govern which credentials the agent may use, and the stored X-API-Key or basic auth is injected only at execution time so it never enters the agent's context.
GET STARTED