A bank in the UAE chooses a digital banking platform inside rules set by the Central Bank of the UAE: the Outsourcing Regulation for Banks decides what approval the contract needs and where customer data may sit, and the Open Finance Regulation makes API-based data sharing and service initiation mandatory for banks. 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 the CBUAE 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 the CBUAE requires of digital channels and technology suppliers
The Outsourcing Regulation for Banks (Circular 14/2021, effective 15 July 2021) applies to all banks operating in the UAE and shapes a platform contract more than any other rule. A bank must obtain a notice of non-objection from the Central Bank before outsourcing any material activity, and must keep a register of all outsourcing arrangements, material or not, recording whether each involves confidential data.
Data location is explicit. The master system of record, which includes all confidential data, must be continuously maintained and stored within the UAE, and customers’ confidential data must not be shared outside the UAE without Central Bank approval and the customer’s prior written consent. The outsourcing agreement itself must keep ownership of data with the bank and its customers, give the bank unfettered access to its data including on termination, state how far subcontracting is allowed, and give the Central Bank access to the service provider, including on-site visits.
The Open Finance Regulation (Circular 03/2025, issued 10 July 2025) makes participation in the Open Finance Framework mandatory for licensees, built around an API Hub that includes a Trust Framework. Banks, including branches of foreign banks, are in the first onboarding phase, and data sharing and service initiation always depend on the user’s express consent.
Guidance on the technology itself comes from the Guidelines for Financial Institutions Adopting Enabling Technologies, issued in November 2021 jointly by the CBUAE, the Securities and Commodities Authority, the DFSA of the Dubai International Financial Centre and the FSRA of Abu Dhabi Global Market, covering APIs, cloud computing, biometrics, big data analytics and AI, and distributed ledgers. A firm licensed in the DIFC or ADGM should confirm which authority’s rules bind its outsourcing. For the selection: ask where every environment and backup will sit, ask for the contract clauses above in the vendor’s standard terms, and ask to see UAE Pass sign-in and Aani payments in the demo.
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:
Saudi Arabia: the Saudi Central Bank’s Cyber Security Framework, in force since 2017, expects a bank to obtain SAMA approval before material outsourcing and before using cloud services, states that in principle only cloud services located in Saudi Arabia should be used, and sets out where multi-factor authentication applies in electronic banking.
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.
| Criterion | What to look for | Suggested weight | Evidence to request |
|---|---|---|---|
| Fit to journeys and segments | Your day-one journeys for retail, SME and corporate, in Arabic and English | 20% | Scripted demo of your journeys; live apps in the stores |
| Architecture and core independence | Runs above your middleware; no hard tie to one core; scales by module | 15% | Architecture documents; a reference on a different core |
| Integration and APIs | Documented APIs; national identity and payment rails; open banking consent | 15% | API specifications; sandbox access; proof of concept |
| Security and regulatory compliance | Controls mapped to your regulator’s rules; data residency options | 15% | Control mapping; penetration test summary; certificates |
| Configurability and ownership | Business teams change journeys without code; clear rights to what you build | 10% | Live change in the demo; ownership clauses in the contract |
| Delivery model and time to launch | Named team, staged go-lives, skills transfer | 10% | Team CVs; milestone plan; reference timelines |
| Commercial model and total cost | Licence, implementation, run and change costs over five years | 10% | Priced five-year scenario; rate card for changes |
| Vendor viability and exit | Financial health, release history, escrow, exit assistance | 5% | 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.