Open banking in Saudi Arabia: what it asks of your integration layer

Saudi Arabia's open banking program has moved from policy to a licensed market. For banks, the API that third parties call is the part everyone sees. The real work sits behind it: identity, consent, security, integration and operations.

Where the framework stands

The Saudi Central Bank (SAMA) has built the program in clear steps:

  • January 2021: SAMA issued its Open Banking Policy.
  • November 2022: the Open Banking Framework was issued, covering account information services (AIS).
  • September 2024: a second release followed, focused on payment initiation services (PIS).
  • March 2026: SAMA began licensing fintech companies to provide open banking services, after a regulatory sandbox phase.

The framework combines business rules with technical standards, which SAMA describes as Customer Experience Guidelines, API Specifications, Implementation Requirements and Operational Guidelines. SAMA also runs an Open Banking Lab where banks and fintechs can test their implementations against the framework.

With licensed third parties entering the market, a bank's open banking capability stops being a compliance project with a deadline. It becomes a production service that other companies build their products on. That is a different standard to meet.

Open banking is an integration problem first

Behind a single "list accounts" or "get transactions" call there may be a core banking system, a cards platform, a separate financing system and a customer master. Behind a payment initiation call sit your payment processing, your limits and fraud controls, and the domestic payment rails you depend on.

Third-party traffic also behaves differently from your own channels. Aggregators poll, batch and retry in patterns you do not control, and they will find every slow back-end query. If your open banking APIs call core systems directly, your own mobile banking customers will feel it.

The integration layer has to absorb that load: read models and caching where the data-freshness rules allow, back-end protection through rate limits and circuit breakers, and consistent data mapping, so the same account looks the same through every API and every channel. If that layer is still a web of point-to-point links, retiring them in sequenced waves is usually the first step.

Identity and consent decide every call

Every open banking call depends on one check: that this customer has authorized this third party to perform this action on this account at this moment. Making that check reliable is an identity and consent problem.

On security, the KSA open banking profile builds on the OpenID Foundation's Financial-grade API (FAPI) standards. The OpenID Foundation's conformance tests for the KSA profile are based on FAPI 1.0 Advanced, with Pushed Authorization Requests (PAR) and client authentication by mutual TLS or private key JWT. The FAPI 2.0 Security Profile was published as final in February 2025, and the OpenID Foundation has reported that SAMA has committed to migrating from FAPI 1 to FAPI 2.

In practice, choose an authorization server that passes the KSA profile conformance tests on FAPI 1.0 Advanced today and is ready for FAPI 2.0, so the move becomes a configuration change rather than a rebuild.

Consent deserves the same care. Treat it as a first-class record with a full lifecycle:

  • requested by the third party, then authorized by the customer through strong authentication you already trust;
  • scoped to specific accounts, permissions and an expiry;
  • checked on every resource call, not only when the token is issued;
  • visible to the customer, who can review and revoke it in your channels;
  • retained with its full history for disputes, audit and data-protection obligations.

Customer authentication should reuse the identity platform behind your digital channels, so customers meet the same experience and the same risk controls. A separate login built only for open banking creates a second attack surface and a weaker customer experience. And data shared through open banking is still personal data under the Personal Data Protection Law (PDPL), so consent records and access logs need the same protection as the data itself.

API security lives at the gateway

The API gateway is where most security requirements become enforceable. At a minimum it should:

  • terminate mutual TLS and validate third-party certificates;
  • validate access tokens, including their binding to the client certificate, on every call;
  • apply quotas and rate limits per third party, and shield back ends from bursts;
  • validate requests against the published API schemas;
  • handle message signing and replay protection wherever the specifications require them;
  • log every call with the third-party, consent and customer context an investigation will need.

Keep the open banking exposure zone separate from your internal APIs. The same back-end service may serve both, but the external path needs its own gateway policies, its own monitoring and its own kill switch.

Payment initiation raises the stakes

Account information is read-only. Payment initiation moves money on instruction from a third party, which raises the engineering bar:

  • idempotency on every payment request, so a retried call never becomes a duplicate payment;
  • clear, timely payment status that the third party can query and the customer can trust;
  • the same limits, fraud screening and sanctions controls you apply in your own channels;
  • end-to-end traceability from the third-party request to the settlement record, with reconciliation.

Payments initiated by third parties also inherit the operating demands of instant payments: they arrive at any hour, including during your core's end-of-day run. Our note on what IPS changes for bank operations covers that side.

Onboarding is part of the product

Third parties judge a bank by how quickly they can get from first contact to a working integration. Accurate documentation, a realistic sandbox, clear certificate and client onboarding steps, and a named support channel matter as much as the APIs themselves. Go through the onboarding steps yourself, and test against the Open Banking Lab, before the first licensed third party does.

Monitoring, SLAs and reporting

Once third parties build on your APIs, an outage is no longer an internal incident. It breaks someone else's service, in front of their customers. The framework includes Operational Guidelines alongside the API specifications; treat them as the floor. Measure what third parties actually experience, per endpoint: availability, latency, error rates and consent completion rates. Build dashboards and incident communications for that external audience, plan capacity for the third-party volumes you expect rather than today's, and give the numbers a named owner.

Beyond compliance

Banks that treat open banking purely as a mandate tend to build the minimum and carry it as a cost. The same platform, run as a product, can also support partner propositions and commercial APIs beyond the regulated scope. At a leading Saudi bank, an API ecosystem built on the existing integration estate now generates 8% of the bank's annual profit. Open banking is a good reason to build that foundation properly.

Readiness checklist

  • Current framework releases (AIS and PIS) mapped to your products, systems and accountable owners
  • Authorization server conformance-tested against the KSA profile: FAPI 1.0 Advanced today, ready for FAPI 2.0
  • Strong customer authentication that reuses your digital identity platform
  • Consent store run as a system of record, with customer-facing review and revocation
  • Gateway enforcing mutual TLS, certificate-bound tokens, quotas, schema validation and full logging
  • Back ends protected from third-party load with read models, rate limits and circuit breakers
  • Payment initiation with idempotency, status reporting, fraud controls and reconciliation
  • Developer onboarding, sandbox and support tested end to end, including in the Open Banking Lab
  • Monitoring and SLA reporting from the third party's point of view, with named owners
  • Data-protection review covering consent records, logs and shared data under the PDPL

Our ConsentHub platform covers third-party onboarding, the consent lifecycle and the account and payment APIs, and DevGate, our developer portal, is in early access.

If you want an outside view of how ready your integration layer is for licensed third-party traffic, book an executive briefing. We will look at where you stand against the framework and give you a written view of the gaps that matter most.