In production

IntegralDots ConsentHub Open banking platform

The SAMA Open Banking Framework, run as one governed platform.

ConsentHub onboards third-party providers, checks their certificates, runs the consent lifecycle and serves account information and payment initiation APIs to the security profile the framework requires: FAPI 1.0 Advanced today, ready for FAPI 2.0. Operations, security and compliance teams work from one console, and every decision is logged.

  • Aligned withSAMA Open Banking Framework
  • SecurityFAPI 1.0 Advanced, ready for 2.0
  • ServicesAccount information and payment initiation
  • RunsYour data centre or private cloud
ConsentHub open banking programme: 214,380 customers connected through 14 live partners; a gallery of partner cards showing what each fintech offers and how many customers use it; regulatory status for each service and the monthly SAMA report; customer growth over six months against the programme target; and two items waiting for a decision
  1. Partners at a glanceEvery live partner, what it offers your customers and how many use it, with the ones still in testing.
  2. Regulatory statusEach service, the monthly report to SAMA, the security profile and partner certificates, in one column.
  3. Customers connectedSix months of growth against the programme target, with the moment the consent screen reached the app.
  4. Needs a decisionPartners asking to go live and certificates due for renewal, each with a button to act.

Product screens show demo data.

Why it matters

Open banking is a regulatory duty and a live service at the same time.

The SAMA Open Banking Framework sets out how banks share account information with authorised third parties and, in the next stage, let them initiate payments. To meet it, the bank has to know every TPP, check every certificate, hold every consent, and be able to prove all of it later.

  • A stack in piecesGateway, authorisation server, consent store and directory checks are bought separately and wired together by hand, with gaps between them.
  • Security profile driftFAPI rules are strict and detailed. A small configuration change can break conformance, and nobody notices until a TPP's calls start failing.
  • Consent nobody can seeCustomers, TPPs and operations staff each hold a different picture of what was agreed and when it ends.
  • Evidence on requestAudit and reporting questions take days of log searches across systems that were never built to answer them.
How it works

From TPP registration to the last API call.

Each of the five stages hands the next a verified client, a valid consent or a bound token, and logs what it did.

  1. Onboard

    TPPs register through dynamic client registration, using a software statement from the framework's directory. Roles and certificates are checked against the directory.

  2. Consent

    The TPP lodges a consent request. The customer signs in through your identity layer, picks accounts and approves in your app or web banking.

  3. Secure

    Tokens are issued under FAPI 1.0 Advanced: pushed authorisation requests, private_key_jwt client authentication, and access tokens bound to the TPP's certificate over mTLS.

  4. Serve

    Account information and payment initiation APIs reach your core banking and payment hub through your integration layer, within the consent's permissions and expiry.

  5. Govern

    Every call is metered and logged. Operations sees traffic and errors; compliance gets consent, availability and performance evidence.

Capabilities

What a bank needs to run open banking, in one place.

Onboarding

TPP registry and directory sync

Dynamic client registration, software statement validation, and a local registry kept in step with the directory, including suspended and removed participants.

Certificates

Certificate checks on every call

Transport and signing certificates checked for chain, role and revocation status, with expiry warnings sent to your team and to the TPP.

Consent

The full consent lifecycle

Account access and payment consents from request to authorisation, use, expiry and revocation, with a consent dashboard your customers use in your own app.

Security

FAPI 1.0 Advanced, ready for 2.0

mTLS, PAR, signed request objects, PKCE and private_key_jwt today. The FAPI 2.0 Security Profile can be staged and tested alongside before you switch.

APIs

Account information and payment initiation

Accounts, balances, transactions, beneficiaries and standing orders first. Payment consents and payments next, executed through your payment hub.

Insight

Traffic, limits and commercial plans

Usage by TPP and API product, fair-use limits and error analysis, plus plans for any premium APIs you offer beyond the mandated scope.

Inside the product

Built for the teams that run open banking day to day.

ConsentHub service levels: 99.97% availability over 30 days against an agreed 99.5%, with a planned upgrade marked on the daily chart; a typical answer to partners of 0.4 seconds against a 1.5 second limit; and the reports due this month with their status and buttons to open or approve them

Service levels and regulatory reports

Heads of operations and compliance see whether the service met the agreed level, how quickly partners get an answer, and which reports are due this month.

  1. Availability each dayThirty days against the agreed level, with planned work marked so it is not mistaken for an outage.
  2. Response to partnersTypical answer time for each service, compared with last month and the agreed limit.
  3. Reports due this monthWhat has gone to SAMA, what is ready to sign and what is still being prepared.
ConsentHub customer consents: 286,940 active consents held by 214,380 customers; consents by purpose with the change since October; consents ended each month, split into expired and stopped by the customer, with the start of renewal reminders marked; a consent receipt as the customer sees it in the yourbank app, with a Stop sharing button; and four next steps

Customer consents, as the bank and the customer see them

Compliance and product teams see how many customers share data and why, how many consents end each month, and exactly what a customer sees in your app.

  1. Consents by purposeActive consents for each purpose, with the change since last month.
  2. Consents endedExpired and stopped by the customer, month by month, with the effect of renewal reminders.
  3. The customer's viewThe consent receipt in your app: accounts shared, what the partner can see, why, until when, and a button to stop sharing.
  4. Next stepsExpiring consents, new purpose requests, wording changes and complaints, each with a button to act.
Security & deployment

The security the framework expects, and the evidence auditors ask for.

Deployed inside your boundary, connected to your identity layer and your core, and designed around the framework's security profile.

Deployment

  • Your data centre or private cloud in the Kingdom
  • Customer data and consent records stay in your environment
  • High-availability gateway and authorisation server across sites
  • A separate sandbox where TPPs test before going live

Security

  • FAPI 1.0 Advanced: PAR, PKCE, signed request objects and private_key_jwt
  • Access tokens bound to the TPP's certificate over mTLS
  • Directory, certificate and revocation checks on every call
  • Signing keys held in your HSM

Governance

  • Consent records with their full history
  • Maker-checker approval for TPP, product and security changes
  • Availability, performance and usage figures for regulatory reporting
  • Tamper-evident audit log, retained under your records policy

Integration

  • Core banking and payment hub through your integration layer
  • Customer authentication through OneSign or your current identity provider
  • Payment initiation on instant rails through PayConnect
  • Events and logs to your SIEM, monitoring and ticketing tools
Designed around
  • SAMA Open Banking Framework
  • FAPI 1.0 Advanced
  • FAPI 2.0 Security Profile
  • OAuth 2.0 and OpenID Connect
  • mTLS certificate-bound tokens (RFC 8705)
  • Pushed authorisation requests (RFC 9126)
  • OpenAPI 3
  • PDPL data handling
FAQ

Questions banks ask about open banking

Does it cover both account information and payment initiation?

Yes. Account information is the base. Payment initiation reuses the same TPP onboarding, consent and security layers, and payments are executed through your payment hub. The framework introduces these services in stages, and each API product can be switched on when you are ready for it.

Which FAPI profile does it use?

FAPI 1.0 Advanced, which is what open banking in the Kingdom uses today, with pushed authorisation requests, private_key_jwt client authentication and certificate-bound tokens over mTLS. The FAPI 2.0 Security Profile can be configured and tested in parallel, so the move can be planned and tested in advance.

Can we keep our existing API gateway or identity provider?

Often, yes. ConsentHub can sit behind an existing API gateway. Customer authentication can run through OneSign or your current identity provider, provided it can meet the security profile. We check this with your architects at the start.

How do customers see and revoke their consents?

Through a consent dashboard in your own app and web banking, built on the ConsentHub consent APIs. A revocation takes effect on the TPP's tokens straight away and is recorded in the consent history.

How does a rollout usually start?

With account information in the sandbox and a few TPPs, then production, then payment initiation. The pace depends mostly on your core banking and channel landscape, which we review first.

See ConsentHub on your own landscape.

Book a demo, or ask for a review of your current open banking stack against the framework's requirements.