Your channels. Powered by OREBAN.
Build mobile banking, internet banking and other financial experiences on top of OREBAN’s APIs. Your team owns the experience; the core owns the accounting.
curl -X POST https://api.oreban.com/v1/auth/token \
-H "Content-Type: application/json" \
-d '{
"client_id": "cli_7F3PQD",
"client_secret": "<secret>"
}'
{
"access_token": "<token>",
"token_type": "Bearer",
"expires_in": 3600
}Everything your channels need to talk to the core.
Nine areas make up the developer surface. Each one is documented with the request and response shapes your team will build against.
API Documentation
Endpoint reference, request and response shapes, error codes and pagination behaviour for every resource exposed by the core.
Authentication
Credential-based token issuance with scoped access, so each channel and internal tool holds only the permissions it needs.
Customers API
Create and update customers, manage customer types and KYC tiers, and retrieve the customer record behind an account.
Accounts API
Open accounts against configured products, read balances and statements, and apply restrictions, holds and liens.
Transactions API
Post and query transactions, with the double-entry ledger behaviour handled inside the core rather than in your channel.
Loans API
Originate loans, read repayment schedules, record repayments and follow the state of a loan through its lifecycle.
Webhooks
Subscribe to core events so your channels react to postings, status changes and loan activity without polling.
Sandbox
A non-production environment for building and rehearsing against, with the same contract as production.
API Status
Operational status for the API surface, so your engineering team can see what is happening before your customers ask.
React to what the core does, as it happens.
Subscribe your services to core events instead of polling for changes. Each delivery carries the resource that changed and the reference you can reconcile against.
customer.createdA customer record has been opened.account.openedAn account has been opened against a product.transaction.postedA transaction has posted to the ledger.account.status.changedA restriction, hold or closure was applied.loan.disbursedLoan funds have been released to the customer.loan.repayment.receivedA repayment has been recorded against a schedule.{
"id": "evt_9WQ41H",
"event": "loan.repayment.received",
"created_at": "2026-03-05T11:02:18Z",
"data": {
"loan_id": "lon_5KD82C",
"account_id": "acc_4TZ91B",
"amount": 91000,
"installment": 1,
"outstanding_principal": 328500
}
}From credentials to production in three steps.
Get sandbox credentials
We issue client credentials for the sandbox environment and walk your engineers through the authentication flow.
Build against the sandbox
Develop your channels against the same contract you will run in production, with test customers, accounts and products in place.
Move to production
Production credentials are issued once your institution is configured, and the integration you already built points at the live core.
Point your engineers at the core.
We will set your team up with sandbox credentials and walk through the endpoints your channels depend on.