Meet your open banking obligations. Without building the plumbing.
Comply with open banking standards with the world’s leading compliance solution, ahead of the market, without the hassle and delays.
Requested by
Demo TPP
Registered AISP · account information
Access requested
- Account details and holder name
- Balances
- Transactions, last 12 months
Confirmed with SCA in your bank app
Trusted by
Consent governed end to end
Every consent is captured, scoped, time-bound and revocable, with its full lifecycle on record from first authorisation to withdrawal.
Secure APIs by default
Account information and payment initiation calls run over mutual TLS with signed requests, so the transport security is settled before you start.
Evidence, not a reporting scramble
Events land in an append-only audit trail as they happen, so regulatory returns are assembled from the record rather than reconstructed at the deadline.
From authorisation to audit entry, in one pass
- 1The customer authorises a third party in your channel and confirms with strong customer authentication.
- 2The third party calls the account or payment APIs under mutual TLS, scoped to exactly what the consent allows.
- 3Every call and consent change is written to an append-only trail that feeds your regulatory returns.
- 09:14:02consent.createdDemo TPP
- 09:14:31consent.authorisedPSU · SCA
- 09:14:33accounts.readDemo TPP
- 09:14:33balances.readDemo TPP
- 11:02:10consent.revokedPSU
Every event is retained in sequence, so a consent’s full history can be reconstructed for a regulatory return or an investigation.
One platform for the customer, the third party and your own operators
Consent authorisation
The account holder sees who is asking, what is being requested and for how long, then approves with strong customer authentication.
Onboarding and APIs
Providers register, present certificates and call the account information and payment initiation APIs under mutual TLS.
Operator console
Consents, registered providers, API traffic, audit evidence and regulatory reporting in one control surface.
And the surfaces your integrators need
Third-party developers get somewhere to read, somewhere to test and somewhere to prove conformance before any production traffic is switched on.
Your questions, answered
Reach out if we missed yours.
Open banking, compliant from day one
Talk to our team about enablement in your market, or start in the sandbox today.
Tarabut is licensed for open banking in Saudi Arabia. Regulatory requirements, available APIs and reporting obligations differ by market and are subject to the applicable regulator’s framework.