Security and control
Two layers of permission work together. Roles decide which endpoints may be called. Views decide which accounts and fields may be used. Customers add a third with their consents.
A view decides which fields of an account each party sees, and what they may do with it. Owner, accountant, auditor and public views come built in, and banks add their own.
Hundreds of Roles each open a small set of endpoints. People hold them as Entitlements, applications as Scopes, at one bank or for the whole system.
Give the same Roles to many people at once, and keep them in step when the Group changes.
ABAC rules decide access from the attributes of the user, the account and the request.
The person who creates a payment request cannot be the one who approves it.
Corporate accounts with signatory panels and multi-signature approval.
v7.0.0
Mark the applications your installation runs itself. Only they may act as themselves, they declare the Scopes they need, and administrators see what is missing.
v7.0.0
Grant an application a view of an account, so a service can act on it with its own token, without a stand-in user.
Customers decide which applications may see their data or make payments, for how long, with SCA. Unused consents expire by themselves.
Keycloak, OBP-OIDC and public providers such as Google and Microsoft, each limited to your own client ids.
Client certificates checked at your proxy and passed on as PSD2-CERT, with the proxy itself named and trusted.
Username and password for trusted apps, and Sign-In With Ethereum for wallet holders.
Services sign in as themselves, with no User behind them. Each application's grant types say whether people log in through it, it gets its own token, or both.
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.