Architecture
Applications call OBP-API. OBP-API applies the standards, authentication, Roles and views, then reaches each bank's systems through the connector that suits them.
Each call is authenticated, checked against the caller's Roles and views, and passed to the connector configured for that bank and method.
A connector translates OBP's calls for your systems. Choose one per bank, or one per method.
Try every endpoint, read its documentation and see the Roles it needs.
Manage banks, users, Roles, consumers, rate limits and caches.
Where developers sign up, register their apps and get started.
AI agents that find and call endpoints with the user's own permissions.
Identity providers for development and production.
Watches running instances and suggests the improvements that matter most.
Runs inside a bank's network and connects it to a platform operator, with outbound connections only.
SEPA, RabbitMQ and gRPC adapters that sit beside your core banking system.
Routes requests between instances, for example by region.
Runs startup programmes, from the call for applications to graduation.
Tests open banking APIs against the agreed standard, and issues signed conformance reports.
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.