WCWealth CRM Direct
Guides › Compliance

Core Banking for a New Digital Bank in Saudi Arabia: SAMA Rules, Costs and Timelines

SAMA approvals, in-kingdom hosting and Sharia requirements shrink the core banking shortlist for a Saudi digital bank to a handful of vendors. Here's what each filter does, what it typically costs, and a realistic 12-to-24-month plan.

Wealth CRM Direct editorial team · November 2026 · 9 min read

Why SAMA's Licensing Stages Shape the Core Banking Decision

If you're building a digital bank in Saudi Arabia, treat the core banking system as part of your license application, not a procurement task for later. The Saudi Central Bank (SAMA) wants to see your target operating model, technology architecture, outsourcing arrangements and cybersecurity posture before it recommends a license. So the core banking software you pick for Saudi Arabia has to look credible on paper early, and it has to be deliverable on a timetable the regulator will hold you to.

SAMA's digital bank licensing guidelines set out a staged process. In outline:

  1. Pre-application engagement with SAMA to discuss the business model, shareholders and capital.
  2. Formal application with a business plan, governance structure, risk framework and technology blueprint.
  3. In-principle approval and government approval, followed by company incorporation.
  4. Establishment and operational readiness: building systems, hiring key people, and passing SAMA's readiness assessments, which typically include testing and independent reviews.
  5. Launch, often with restrictions at first (customer numbers, product range or balances) that are lifted as the bank shows stable operations.

Minimum paid-up capital for a digital bank has been set in the billions of riyals. Confirm the current figure with SAMA and local counsel before you model funding. It matters for technology because it shows what SAMA expects: a full bank with full prudential obligations, not a lighter fintech regime.

Advertisement

That has three consequences for the core decision. You need a vendor that can explain its architecture to SAMA's technology and cyber teams. You need an implementation partner with Saudi delivery experience. And you need a platform that works under launch restrictions, with product limits, customer caps and phased feature releases controlled through configuration rather than code changes.

Outsourcing, Cloud and Data Residency: The Filters That Cut the Long List

Most global core vendors can pass a generic functional RFP. Far fewer can meet Saudi hosting, outsourcing and data-protection expectations together. Apply these three filters before you score any functionality.

SAMA outsourcing and cloud expectations

SAMA's outsourcing rules generally treat a core banking platform as material outsourcing, whether it runs as SaaS or as a vendor-managed service. Expect SAMA review or no-objection before you sign or go live, contractual audit and access rights for both the bank and SAMA, exit and transition plans, and concentration-risk analysis. Moving material functions or data outside the Kingdom faces a much higher bar and needs explicit approval. SAMA's cloud computing framework and the National Cybersecurity Authority's cybersecurity controls for organizations and for cloud add requirements on encryption, key management, logging and provider certifications. SAMA's Cyber Security Framework and business continuity requirements shape your disaster-recovery design.

Data residency under the PDPL

The Personal Data Protection Law (PDPL), enforced by the Saudi Data and AI Authority (SDAIA), regulates personal data processing and allows transfers outside the Kingdom only under defined conditions. Combined with SAMA's sector expectations, the working assumption for a digital bank is simple: production customer data, backups and disaster recovery stay in Saudi Arabia. A vendor whose SaaS runs only from Frankfurt, Dublin or Singapore is effectively out unless it can deploy into an in-kingdom region.

That's why cloud geography matters. Oracle, Google Cloud (with Aramco), Huawei Cloud and local providers such as center3 (part of stc) have offered or announced in-kingdom capacity, and Microsoft and AWS have announced Saudi regions. Availability changes quickly, so confirm which services are actually generally available in-kingdom before you assume a vendor's reference architecture will work.

Questions that expose weak candidates quickly

  • Has the platform run in production in Saudi Arabia, or in another market with strict residency rules such as the UAE, Qatar or Indonesia?
  • Can every component, including analytics, fraud scoring, support tooling and log aggregation, run in-kingdom? Offshore support access often sinks the residency story.
  • Will the vendor accept SAMA audit rights and step-in clauses without heavy redlines?
  • Who holds the encryption keys, and can the bank use its own HSMs or a key service located in Saudi Arabia?

Red flag: a vendor that says residency "can be handled later." It can't. SAMA will ask about it during the application, and re-platforming hosting after approval resets your timeline.

Islamic Core Banking: What Sharia Compliance Requires of the Platform

Most Saudi retail customers expect Sharia-compliant products, and SAMA expects banks to maintain Sharia governance: a Sharia board, a compliance function and Sharia audit. Your core has to support that governance model, not just the product names. A conventional ledger with renamed fields won't survive a serious Sharia review.

Islamic core banking capability should cover these areas natively:

  • Financing contracts: murabaha and commodity murabaha, tawarruq (widely used in Saudi personal finance), ijara and ijara muntahia bittamleek, with correct sequencing of asset purchase, ownership and sale.
  • Profit-based deposits: mudaraba and wakala investment accounts with profit-sharing ratios, pool management and profit distribution, plus qard-based current accounts.
  • Commodity trade integration for tawarruq and murabaha, with audit trails showing ownership transfer before sale.
  • Late-payment handling that sends charity amounts to a separate account instead of booking them as income.
  • AAOIFI-aligned accounting and reporting your Sharia board and auditors can test.
  • Product governance workflow, so Sharia board approval is recorded before a product setting goes live.

The vendor field splits in two. Established platforms with dedicated Islamic modules, including Temenos, Oracle FLEXCUBE, Infosys Finacle, Finastra and specialists such as Path Solutions (iMAL) and ICS Financial Systems, have long Gulf track records but differ widely in how cloud-native their current versions are. Newer cloud-native cores such as Thought Machine, Mambu and 10x are highly configurable, but Islamic products are usually built as configured product logic, sometimes by the integrator. That can work well. The question is who owns and maintains the Sharia logic after go-live.

Our position: for a first-time Saudi digital bank with a mainly Islamic retail book, favor a vendor with proven, packaged Islamic contract support over one that offers maximum configurability, unless the cloud-native vendor can show a live Islamic product set that a Sharia board has already reviewed. Configurability doesn't replace product logic that has been vetted.

Also check integration with local rails and utilities: SARIE and instant payments, mada, SADAD, Nafath for digital identity, SIMAH for credit data, and SAMA's open banking framework. Pre-built connectors can save months.

Indicative Platform Costs for a Saudi Digital Bank

Costs depend on customer volume forecasts, product scope, hosting model and how much of the surrounding stack the core vendor supplies. The figures below are typical 2026 market ranges in USD for a greenfield digital bank targeting several hundred thousand to a few million retail customers. Contracts vary widely, and local pricing and currency terms differ, so confirm every figure with vendors.

Cost itemTypical 2026 range (USD)Main cost drivers
Core banking subscription or license (annual)$1M–$4M in years 1–2, rising with accountsPer-account or per-customer pricing, modules (Islamic, lending, cards), minimum commitments
Core implementation services$5M–$20MProduct count, Islamic product build, integrator rates
In-kingdom cloud hosting (annual)$0.8M–$3MProduction plus DR in-kingdom, non-production environments, managed services
Surrounding stack (digital channels, onboarding, AML, fraud, cards, payments hub)$6M–$20M over first 2 yearsBuild vs. buy, number of vendors, local rail connectors
Security, testing and independent assurance$1M–$4MPenetration testing, NCA/SAMA control assessments, readiness audits
Indicative total technology spend to launch$20M–$60MScope at launch, vendor mix, timeline slippage

Hypothetical worked example: say a digital bank plans 500,000 customers in year two, with current accounts, mudaraba savings, tawarruq personal finance and a debit card. Core subscription might run $1.5M–$3M a year, depending on per-customer pricing and minimum commitments. Add roughly $9M for implementation, $1.5M a year for in-kingdom hosting and about $12M for channels and surround systems, and technology spend to launch lands around $25M–$30M before staffing.

The biggest cost risk isn't the license. It's delay. Every extra month before launch burns salaries, vendor fees and hosting with no revenue coming in, and for a funded digital bank that can easily run to seven figures a month. A vendor that's cheaper on paper but adds four months of Islamic product build usually costs more overall.

A Realistic 12-to-24-Month Path From Application to Launch

Twelve months from formal application to launch is possible only if technology selection is mostly done before you file and the core vendor has delivered in Saudi Arabia before. Eighteen to 24 months is more typical. Phases overlap, and regulatory reviews often set the pace more than build work does.

PhaseTypical durationCore banking workstream
Pre-application and vendor shortlisting2–4 months (before filing)Residency and Islamic filters, RFP, architecture for the application
Application review and approvals4–9 monthsVendor selection, contract negotiation, outsourcing documents for SAMA
Incorporation and build6–12 monthsIn-kingdom environments, product configuration, Sharia board product approvals, integrations
Testing and readiness assessment2–4 monthsSIT, UAT, performance and DR tests, penetration testing, independent reviews
Restricted launch and scale-up3–6 months after launchEmployee pilot, customer caps, phased product release

Red flags that usually predict slippage:

  • Contracts signed before SAMA has reviewed the outsourcing arrangement.
  • Islamic products scheduled for "phase two" when the business plan relies on financing revenue from launch.
  • An integrator with no Arabic-language delivery team or no history of SAMA readiness reviews.
  • Disaster recovery designed late, or placed outside the Kingdom.
  • No named owner for Sharia logic maintenance after go-live.

Rules, capital thresholds and cloud approvals change, and how they apply depends on your shareholders and structure. Work with Saudi regulatory counsel and a licensed Sharia advisory firm before you finalize contracts or the application.

Next step: before discussing features with any vendor, send your long list three pass/fail questions. Can it run fully in-kingdom today? Does it have a live Islamic product set reviewed by a Sharia board? Has it been through a SAMA or comparable Gulf regulator review? Shortlist only the vendors that pass all three.

Common questions

Can a Saudi digital bank run its core banking system on a cloud outside the Kingdom?

In practice, rarely. SAMA's outsourcing rules require explicit approval for material outsourcing outside the Kingdom, and the PDPL restricts cross-border transfers of personal data. Most digital banks plan for production, backup and disaster recovery to sit in-kingdom, and should confirm any exception with SAMA and local counsel early.

How long does it take to go from a SAMA digital bank license application to launch?

Plan for 12 to 24 months. The shorter end assumes technology selection is mostly done before filing and a vendor with Saudi delivery experience. Many banks also launch with restrictions that take another three to six months to lift.

Do we need a specialist Islamic core banking vendor?

Not necessarily, but you need packaged or already-reviewed support for tawarruq, murabaha, ijara and mudaraba deposits, plus AAOIFI-aligned accounting. Cloud-native cores can be configured for Islamic products, but check that a live product set exists and that someone clearly owns the Sharia logic after go-live.

What does core banking software for a Saudi digital bank typically cost?

Typical 2026 market ranges are $1M to $4M a year for the core subscription in early years and $5M to $20M for implementation. Total technology spend to launch is often $20M to $60M including channels and surround systems. Figures vary by contract and scope, so confirm them with vendors.

Written by the Wealth CRM Direct editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.