How to Choose a Digital Banking Platform in Saudi Arabia: An Evaluation Framework

By Eurisko Team · Last reviewed November 2026

Comparing digital banking platforms against evaluation criteria

A bank in Saudi Arabia chooses a digital banking platform inside rules set by the Saudi Central Bank: the SAMA Cyber Security Framework governs how electronic banking is secured and how suppliers and cloud services are approved, and the Open Banking Framework adds account information and payment initiation to the channel roadmap. Start the selection from those rules, then score a short list of vendors against weighted criteria agreed before the first demo, and make each vendor prove its score with evidence.

This guide opens with what SAMA requires of digital channels and technology suppliers and how the neighbouring markets differ, then gives a selection committee the framework: eight criteria with rule-of-thumb weights, the evidence to request, a five-step evaluation process and the red flags that should lower a score. It is written to be vendor-neutral; our own position is confined to the last section.

What SAMA requires of digital channels and technology suppliers

The SAMA Cyber Security Framework (Circular 381000091275 of 24 May 2017, in force) is the document a platform will be measured against. Its section on electronic banking services says multi-factor authentication should be used when a customer registers and for all electronic banking services, and names the moments that need it: sign-on, adding or modifying beneficiaries, adding utility and government payment services, high-risk transactions above predefined limits, and password reset. Requesting and activating multi-factor authentication should use different delivery channels, high availability should be ensured, scheduled downtime should be communicated to SAMA and customers, and SAMA’s approval should be obtained before a new electronic banking service is launched.

The framework’s third-party domain is where the supplier appears. The outsourcing process should include SAMA’s approval before material outsourcing and the involvement of the bank’s cyber security function. For cloud, the bank should obtain SAMA approval before using cloud services or signing with the cloud provider, and in principle only cloud services located in Saudi Arabia should be used; anything outside the Kingdom needs explicit SAMA approval.

SAMA’s Open Banking Framework, announced in November 2022 as a set of legislation, regulatory guidelines and technical standards, started with account information services and designated payment initiation for its second release, so consent management and partner APIs belong in the platform scope.

For the selection, that means three tests. Can step-up authentication be set by policy for each of the moments SAMA lists, without custom code? Can the platform run in your own data centre or in-Kingdom, so the cloud question does not decide the vendor for you? And can the vendor show national rails such as Nafath sign-in and sarie transfers working in the demo, not on a slide?

How the neighbouring markets differ

If your group operates across borders, or a vendor’s references come from another market, the rules that platform was built to are not yours. In brief:

United Arab Emirates: under the Central Bank of the UAE’s Outsourcing Regulation for Banks (Circular 14/2021), a bank needs a notice of non-objection before outsourcing any material activity and must keep its master system of record, including all confidential customer data, in the UAE. The Open Finance Regulation (Circular 03/2025) makes participation in the Open Finance Framework mandatory for licensees, with banks in the first onboarding phase.

Kuwait: the Central Bank of Kuwait’s Cyber and Operational Resilience Framework (CORF), issued in December 2025 as the successor to its 2020 Cybersecurity Framework, applies to every entity the CBK regulates and includes dedicated third-party risk baselines covering contracts, sub-contracting, exit strategy, data storage and the use of cloud services.

Oman: the Central Bank of Oman’s Open Banking Regulatory Framework deems licensed banks authorised to provide open banking services but requires a no objection letter first, and holds banks to its API standards and its data and information security specification. It also lists the CBO’s rules for availing cloud services (BM 1185) among the rules participants must follow.

Lebanon: Banque du Liban’s Basic Decision 7548 on electronic banking and financial operations (Basic Circular 69), as replaced in January 2026, requires a bank to notify BDL in writing ninety days before starting or changing an electronic operation, to obtain prior approval for e-KYC, and to store customer and transaction data in Lebanon.

First, what exactly are you choosing?

A digital banking platform is the layer that delivers mobile and online banking to customers: onboarding, accounts, payments, cards, lending journeys and engagement, connected to the core banking system underneath. It is not the ledger, and it is not a generic content or experience tool. Committees that skip this definition end up comparing a core vendor’s channel module, a standalone platform and a custom build as if they were the same purchase.

Write down three things before the longlist: the segments in scope (retail, SME, corporate, a new digital brand), the journeys that must be live on day one, and what stays where it is (the core, the card system, the payment hub). Those three lists become the script for every demo and the scope of every price.

Which evaluation criteria should carry the most weight?

Eight criteria cover almost every selection. The weights below are a rule of thumb, not data: a bank launching a new digital brand may move weight to delivery, and a bank answering a supervisory finding may move it to security. What matters is that the weights are agreed and written down before vendors present, so the scoring cannot be bent around a favourite.

Score each criterion from one to five on evidence, multiply by the weight, and file the evidence with the score. A score with no document, demo or reference behind it is an opinion.

Digital banking platform scoring grid (weights are a rule of thumb)
CriterionWhat to look forSuggested weightEvidence to request
Fit to journeys and segmentsYour day-one journeys for retail, SME and corporate, in Arabic and English20%Scripted demo of your journeys; live apps in the stores
Architecture and core independenceRuns above your middleware; no hard tie to one core; scales by module15%Architecture documents; a reference on a different core
Integration and APIsDocumented APIs; national identity and payment rails; open banking consent15%API specifications; sandbox access; proof of concept
Security and regulatory complianceControls mapped to your regulator’s rules; data residency options15%Control mapping; penetration test summary; certificates
Configurability and ownershipBusiness teams change journeys without code; clear rights to what you build10%Live change in the demo; ownership clauses in the contract
Delivery model and time to launchNamed team, staged go-lives, skills transfer10%Team CVs; milestone plan; reference timelines
Commercial model and total costLicence, implementation, run and change costs over five years10%Priced five-year scenario; rate card for changes
Vendor viability and exitFinancial health, release history, escrow, exit assistance5%Audited accounts; release notes; exit plan

How do you test architecture and integration claims?

Most platforms look alike in a demo and differ underneath. Core independence is the first thing to test: ask whether the platform talks to your core directly or through your middleware, what happens to the channels if you upgrade or replace the core, and for a reference bank running the same platform on a different core from yours.

Then test integration where projects actually slip. Ask for the API specifications before the demo, not after. Ask which integrations exist as product (national digital identity, instant payment rails, card systems, sanctions screening) and which would be built for you. Ask how an open banking consent is granted, viewed and revoked, and how a failed payment is retried without posting twice. For mobile security, ask for test results against the OWASP Mobile Application Security Verification Standard, not a general assurance.

Who owns the roadmap, the configuration and the code?

Every platform is configurable in the brochure. In the demo, have the vendor change a real journey in front of you: add a step to onboarding, change a fee, switch a feature on for one segment. Note who made the change (a business user or a developer), whether it needed an app release, and what approval trail it left.

Then settle ownership in writing. Who owns the journeys, rules and designs your teams build on the platform, and can they be exported? Who decides the product roadmap, and what happens to your customisations at each upgrade? If source code access matters to you, ask for the escrow terms and the release conditions, and read them. A platform you cannot change without the vendor, on a roadmap you do not influence, is a dependency your risk committee should see priced.

How to run the evaluation in five steps

A disciplined process keeps the decision defensible to the board, the auditors and the regulator. As a rule of thumb, allow three to six months from longlist to contract; a rushed proof of concept is the usual false economy.

  • Longlist: six to eight vendors from market research and peer banks, cut to three or four on must-have criteria (segments, deployment model, Arabic, references in comparable markets).
  • RFP: send the same scope, the same journeys and the same pricing template to every vendor, with the weights disclosed at criterion level.
  • Scripted demos: every vendor walks through your scripts, in your order, with your evaluators scoring live. No free-form presentations.
  • Proof of concept: the top two connect to a test instance of your core or middleware and deliver one real journey end to end, in a fixed period.
  • References and due diligence: speak to banks in production without the vendor on the call, and complete the financial, security and legal checks before the final score.

What should the cost comparison include?

Licence price is the least comparable number in a proposal. Ask every vendor to price the same scenario over five years: licence or subscription and what drives it (customers, users, modules), implementation, integrations, hosting or infrastructure, support, upgrades, and the cost of a typical change request. Add your own costs: the internal team, testing, security assessments and regulatory approvals.

Then stress the model. What happens to the price if customer numbers double, if you add a segment, or if you leave? Exit costs (data extraction, transition support, parallel running) belong in the comparison from the start, because they are hardest to negotiate after signature.

Red flags that should lower a score

None of these disqualifies a vendor alone. Each should cost points and prompt a harder question.

  • The demo runs on the vendor’s scripts, not yours, or on slides where the product should be.
  • No reference bank in production on a core, a segment or a regulatory regime comparable to yours.
  • Integration with your core is described as standard, but no specification or proof of concept is offered.
  • Compliance answers name frameworks but come with no control mapping, test report or certificate.
  • Every change, including wording and fees, needs the vendor’s developers and an app release.
  • Pricing cannot be modelled over five years, or exit terms are left for later.
  • The team in the proposal is not the team named in the contract.

How Eurisko fits

Eurisko has delivered banking software since 2009 and has more than 200 engineers. Our platform, Eurisko DXP, is a licensed digital banking platform for retail, SME and corporate channels that sits above the bank’s middleware and runs in front of any core, deployed inside the bank’s own data centre or private cloud. Business teams change journeys, products and rules in its Journey Builder, and what they build belongs to the bank. Our ISO/IEC 27001 certification is in progress, not yet complete.

We are not the right choice if you want a core banking system, or a channel module supplied by your core vendor under a single contract: DXP is the channel and experience layer, and it is built to run in your estate. If the framework above puts us on your longlist, we are glad to be scored against it.

FAQ

Frequently asked questions.

What is the most important criterion when choosing a digital banking platform?

Fit to your own journeys and segments usually carries the most weight, because a platform that cannot deliver your day-one journeys in Arabic and English fails whatever its architecture. Architecture, integration and regulatory compliance follow closely. Agree the weights before the first demo and score on evidence.

How long does a digital banking platform selection take?

As a rule of thumb, allow three to six months from longlist to signed contract: a few weeks for the longlist and RFP, a few for scripted demos, and the rest for a proof of concept, references and negotiation. Regulatory approvals or notifications for outsourcing run alongside and should be planned from the start.

Do we need a proof of concept, or are demos enough?

Demos show what a platform can do in the vendor’s environment. A proof of concept shows what it does against your core or middleware, with your data model and your security controls. For a system that will carry every customer interaction, run one with the top two vendors before the final score.

Should the digital banking platform come from our core banking vendor?

It can, and a single supplier simplifies integration and accountability. The trade-off is that your channels then follow the core vendor’s roadmap and are harder to keep if you change the core. Score the core vendor’s channel module on the same criteria and evidence as independent platforms.

Does SAMA need to approve our digital banking platform?

The approvals sit with the bank, not the vendor. The SAMA Cyber Security Framework expects a bank to obtain SAMA approval before material outsourcing, before using cloud services or signing with a cloud provider, and before launching a new electronic banking service. Plan those approvals into the selection timeline and prefer a platform whose hosting model fits them.

Let’s build

Have something ambitious in mind?

Start a project →

Popular searches

Jump to