OpenPayd API
★ Only Publicly Available OpenAPI DocumentPaymentsPayouts Transfersbearer42 EndpointsREST
For Agents
Spin up multi-currency accounts, manage beneficiaries, send payouts, and run FX through OpenPayd's banking-as-a-service API.
Use for: I need to onboard a new corporate client on OpenPayd, Open a multi-currency account for a verified linked client, Send a SEPA payout to a saved beneficiary, Convert 50,000 EUR to GBP at the current rate
Not supported: Does not handle card acquiring, in-store POS, or merchant chargebacks — use for embedded multi-currency accounts, payouts, and FX only.
Jentic publishes the only available OpenAPI specification for OpenPayd API, keeping it validated and agent-ready. OpenPayd is a banking-as-a-service platform that lets businesses spin up named multi-currency accounts, manage beneficiaries, send international payouts, and run currency conversions through a single API. The 42-endpoint surface covers linked-client onboarding, account creation, beneficiary lifecycle, transactions, and FX, making it suitable for fintechs and marketplaces that need embedded banking infrastructure in Europe and the UK.
Install Jentic One Beta
Connect the OpenPayd API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenPayd 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 OpenPayd API.
Onboard linked clients (individuals or businesses) under the master account
Open multi-currency virtual accounts for each linked client
Create, retrieve, and update beneficiaries before sending funds
Initiate SEPA, SWIFT, and Faster Payments payouts to verified beneficiaries
Run currency conversions between supported currency pairs
List historical transactions on a linked-client account
Authenticate via OAuth bearer JWT obtained from /oauth/token
Use Cases
Patterns agents use OpenPayd API for, with concrete tasks.
★ Embedded multi-currency accounts for marketplace sellers
A marketplace creates a linked client per seller, opens GBP and EUR virtual accounts under each, and lets sellers receive payouts directly into named accounts. OpenPayd handles the underlying banking rails so the marketplace does not need its own e-money licence. Onboarding to live is typically a few weeks, mostly KYB.
POST /create-business-linked-client for the seller, then open EUR and GBP accounts via the linked-client account endpoint and return both IBANs.
Cross-border payouts with SEPA and SWIFT
Treasury teams use OpenPayd to send batched payouts to suppliers across the EU, UK, and major SWIFT corridors. The beneficiary endpoints store verified counterparties and the payout endpoints initiate transfers with the correct rail selected per destination, reducing manual SWIFT MT103 work.
Look up the saved beneficiary by ID, then submit a payout for 25,000 EUR via SEPA and confirm the response status is accepted.
FX conversion before settlement
A platform settling earnings to a seller in a different currency converts funds via OpenPayd's FX endpoints before payout, reducing exposure compared with on-rail FX at the receiving bank. The API exposes quote, execute, and settle steps so the agent can confirm rate and amount before committing.
Request an FX quote for 100,000 EUR to GBP, accept the quote, and confirm the converted amount appears on the destination account.
Agent-driven embedded finance through Jentic
An AI ops agent that runs supplier payouts calls OpenPayd via Jentic to refresh the bearer token, look up beneficiaries, and submit transfers. Jentic isolates the OAuth client credentials and exposes the 42 banking operations as discoverable tools so the agent does not need to track token lifetime manually.
Search Jentic for 'send a SEPA payout', load the matching operation, and execute it for a saved beneficiary with amount 5,000 EUR.
Key Endpoints
42 endpoints — jentic publishes the only available openapi specification for openpayd api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/oauth/token
Obtain a bearer token for subsequent calls
POST
/create-linked-client
Onboard an individual linked client
POST
/create-business-linked-client
Onboard a business linked client
GET
/get-linked-client
Retrieve a linked client record
GET
/list-linked-clients
List linked clients under the master account
GET
/list-accounts-for-linked-clients
List multi-currency accounts for linked clients
POST
/oauth/token
Obtain a bearer token for subsequent calls
POST
/create-linked-client
Onboard an individual linked client
POST
/create-business-linked-client
Onboard a business linked client
GET
/get-linked-client
Retrieve a linked client record
GET
/list-linked-clients
List linked clients under the master account
GET
/list-accounts-for-linked-clients
List multi-currency accounts for linked clients
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
OpenPayd OAuth client credentials are stored encrypted in the Jentic vault. Jentic obtains and refreshes the JWT bearer token automatically, so the agent only ever holds a scoped Jentic execution handle.
Intent-based discovery
Agents search by intent (e.g., 'send a SEPA payout' or 'open a multi-currency account') and Jentic returns the matching operation across the 42-endpoint surface with its input schema, removing the need to navigate OpenPayd's documentation tree.
Time to first call
Direct OpenPayd integration: 1–2 weeks for OAuth handling, sandbox onboarding, and rail-specific request shaping. Through Jentic: a few hours — search, load schema, execute against sandbox.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe API
Card processing and Connect-based payouts to connected accounts
Choose Stripe when the use case is card acquiring rather than bank-rail payouts and FX.
FAQs
Specific to using OpenPayd API through Jentic.
Why is there no official OpenAPI spec for OpenPayd API?
OpenPayd does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call OpenPayd API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the OpenPayd API use?
OpenPayd uses OAuth 2.0 with a JWT bearer token obtained from /oauth/token. Through Jentic, the client credentials live in the encrypted vault and Jentic refreshes and attaches the bearer token automatically, so the agent never handles the raw client secret.
Can I open multi-currency accounts with the OpenPayd API?
Yes. After onboarding a linked client via /create-linked-client or /create-business-linked-client, you open named accounts under that client; the spec exposes endpoints to list accounts per linked client and retrieve their details.
What are the rate limits for the OpenPayd API?
OpenPayd applies platform-level rate limits that are not encoded in the OpenAPI spec. Treat the sandbox as a guide for shape and confirm production limits with OpenPayd before scheduling high-volume payout batches.
How do I send a SEPA payout through Jentic?
Run pip install jentic, search 'send a SEPA payout', load the matching payments operation, and execute it with the beneficiary ID, amount, and currency. Jentic obtains the bearer token from /oauth/token first, then calls the payout endpoint.
Does the spec point at sandbox or production?
The default base URL in the spec is https://sandbox.openpayd.com/api, the OpenPayd Sandbox Environment. For production traffic, switch the server to OpenPayd's live host once your account has been promoted out of sandbox.
GET STARTED