Open Bank Project API
OBP-API gives banks, fintechs and regulators one modern API across every core banking system: accounts, payments, customers and consents, with the open banking standards built in and access decided on every call.
$ GET /obp/v7.0.0/assets/OMR { "asset_code": "OMR", "asset_type": "FIAT", "name": "Rial Omani", "decimal_places": 3, "status": "ACTIVE" }
Read from the public sandbox at apisandbox.openbankproject.com on a recent day.
OBP-API covers the whole of a bank's API: what customers and partners use, and what the bank runs it with.
Accounts and payments
Accounts, balances, transactions, counterparties, standing orders, direct debits and payment requests with strong customer authentication.
Customers
Customer records, KYC checks, documents and photographs stored safely and attached to the records they belong to.
Extend
Define new data and endpoints at run time, and publish them as an API of their own with its own OpenAPI document.
Control
Views decide which fields each party sees. Roles decide which endpoints they may call. Consents let customers decide who sees what.
Standards
The Open Bank Project API, Berlin Group NextGenPSD2 and UK Open Banking, served by the same platform from the same data.
Connect
Connectors reach your systems over REST, RabbitMQ, gRPC, Akka or stored procedures, and Bank Nodes connect banks from inside their own networks.
Every endpoint is documented in the API itself, with examples, the Roles it needs and the errors it can return.
Applications call OBP-API. OBP-API applies the standards and the access rules, then reaches each bank's own systems through connectors.
Planning an open banking platform, a banking-as-a-service offer or a regulatory sandbox? Tell us what you want to build, and we will show you OBP-API working with your own banks, products and standards.