The Orenda API lets you build banking into your product: onboard and verify customers, open accounts, issue cards, and move money. It’s one REST API, used the same way for every program and region.

​
One API for every banking need

Authentication

Sign users in with passkeys, MFA, or your own SSO.

Onboarding & verification

Applications, KYC and KYB, document checks, and built-in AML and transaction monitoring.

Accounts

Open multi-currency accounts with local and IBAN details, limits, and statements.

Cards

Issue and manage cards: freeze, PIN, 3DS, secure details, and cardholders.

Beneficiaries

Save payees and check their name before paying (Verification of Payee).

Payments

Send money: domestic, international (FX), scheduled, and batch.

Transactions

Transaction history, filtering, and PDF/CSV statements.

Fees & limits

The fee schedule and published limits, ready to render in-app.
Real-time updates are covered in WebSockets. Crypto (quotes, send, receive, swaps) and open banking consent exist on the platform but aren’t covered in these docs yet — contact the team if you need them. Need multi-user or organisation access? Contact the team.
The same contract works for every program. Some features and limits vary by program; those are noted on the endpoint and listed on the Program capabilities page.

​
Conventions

  • Base URL: https://api.next.orenda.finance
  • Every endpoint is under /v1/.
  • Send your token as Authorization: Bearer <id_token> — the ID token from sign-in, not the access_token. See Authentication.
  • Send an Idempotency-Key on anything that creates a payment, payee, or card, so a retry can’t duplicate it. Optional today, required in a future release — see Idempotency.
Start with Authentication, or browse the API Reference.