Choose a digital onboarding and eKYC solution on three tests: whether it proves identity to an assurance level your regulator will accept, whether it connects to the national identity service of each market you operate in, and whether it leaves a case file an examiner can follow without help. Speed matters, but only after those three are met. Ask for evidence on each (test reports, a working connection, an exported case file), not screenshots.
This guide is vendor-neutral. It sets out what the solution has to do from first screen to funded account, the criteria to score and the evidence to request, how business onboarding differs, the red flags, and how to run a pilot. It starts with the international baseline and with what the central banks of Saudi Arabia, the UAE, Kuwait, Oman and Lebanon publish on remote onboarding.
What do international standards expect of remote onboarding?
The Financial Action Task Force (FATF) published its Guidance on Digital ID in March 2020. It keeps the FATF Standards technology-neutral and asks regulated firms to do two things: understand the assurance levels of a digital identity system (its technology, architecture and governance), then decide whether those levels suit the money laundering and terrorist financing risk of the customer and the product. It also says that non-face-to-face onboarding which relies on a reliable, independent digital identity system with proper safeguards may be standard risk, and can even be lower risk.
Two technical references make “assurance” testable. NIST SP 800-63A, the identity proofing volume of the US Digital Identity Guidelines, defines three identity assurance levels and, where biometrics are collected remotely, requires presentation attack detection whose tests conform to ISO/IEC 30107-3:2023. That ISO standard sets out the principles and methods for assessing presentation attack detection and for reporting the results. Neither document binds a bank in the Gulf or the Levant, but both give you a precise question to put to a vendor.
What do regulators in Saudi Arabia, the UAE, Kuwait, Oman and Lebanon require?
Every central bank in the region applies the same risk-based logic and then differs on the identity service it expects you to use. The table summarises what each one publishes; the instruments are linked under Standards and sources. Rules change, so confirm the current text with your compliance team before you finalise requirements.
| Market | What the central bank publishes | National identity rail | Check with the vendor |
|---|---|---|---|
| Saudi Arabia | SAMA Account Opening Rules: remote opening for individuals, sole proprietorships and companies | Nafath, the unified national access system | Live Nafath connection; who may be onboarded remotely |
| UAE | CBUAE guidance on digital identification for customer due diligence | UAE Pass and Emirates ID validation | Verification record kept; data stored in the UAE |
| Kuwait | CBK instructions to banks on AML/CFT | Kuwait Mobile ID from PACI | Verification level used; enhanced checks for remote customers |
| Oman | CBO instructions on digital onboarding and e-KYC (June 2023) | National Digital Onboarding Registry with Mala’a | Registry connection; data fields returned |
| Lebanon | BDL Basic Circulars 69 and 83 | None named in the texts reviewed | BDL prior approval file; data stored in Lebanon |
What must a digital onboarding and eKYC solution do end to end?
Treat onboarding as one orchestrated process, not a set of checks. A solution that covers only identity verification leaves the bank to build the rest, and the rest is where delays and audit findings come from. A complete solution covers nine things.
- Identity capture and document verification: guided capture, data extraction in Arabic and Latin scripts, and checks on the document’s security features.
- Biometric match and liveness: a face match against the document or the national record, with presentation attack detection.
- National digital identity integration: the identity service of each market, used where the regulator expects it.
- Sanctions and PEP screening: at onboarding, and again when lists or customer data change.
- Risk-based due diligence: a risk rating that decides between standard and enhanced due diligence.
- A manual review queue: maker-checker handling of exceptions, with the evidence attached.
- Core and CRM integration: the customer and the account created automatically, with no re-keying.
- Audit evidence and record keeping: every capture, score, decision and timestamp in one case file, retained for the period your regulator sets.
- Ongoing due diligence and re-KYC: periodic refresh, expiry tracking and event-driven review.
Which evaluation criteria matter, and what evidence should you request?
Start with identity assurance, because everything else depends on it. Ask which assurance level the vendor’s proofing process is designed to meet and how that was assessed. For liveness, ask for a presentation attack detection test report from an independent laboratory, carried out in line with ISO/IEC 30107-3, and read which attack types were tested and on which devices. “We use AI liveness” is not evidence. Ask too how the solution deals with injected or synthetic images that never pass through the camera, because that ISO standard covers only attacks presented at the capture device.
Next, coverage and screening. For each market, ask for a production reference that uses the national identity rail, not a roadmap slide. On sanctions and PEP screening, ask which list sources are supported, how Arabic names and their transliterations are matched, how thresholds are tuned, and how a false positive is cleared and remembered so the same person is not flagged again. Request the false positive rate from a test on your own sample data.
Then the bank’s ability to run it. Compliance and product teams should be able to change journey steps, document types, risk rules and thresholds without vendor code, with each change versioned and approved. The solution should report drop-off by step and let an applicant resume on another device without starting again. It should work fully in Arabic, right to left, and be tested with assistive technologies.
Finally, data and evidence. Establish where identity documents and biometric templates are stored, for how long, who can access them, and whether any of it leaves the country. Ask for an exported case file and judge it as an examiner would. Ask what integration with your core, CRM and screening provider has required at comparable clients, in effort from your team as well as the vendor’s. The weights in the table are a starting point: adjust them to your risk appetite, and score on evidence seen, not on answers given.
| Criterion | Ask the vendor | Evidence to request | Weight |
|---|---|---|---|
| Identity assurance and liveness | Which standard was liveness tested against, and by whom? | Independent ISO/IEC 30107-3 test report | High |
| National identity rail | Is the connection live in this market? | Production reference and demonstration | High |
| Screening quality | How are Arabic names matched and false positives cleared? | Test results on your sample data | High |
| Configurability | Can we change steps and risk rules without your code? | A change made live in a workshop | Medium |
| Drop-off analytics and resume | Can we see abandonment by step and resume across devices? | Funnel report from a live deployment | Medium |
| Arabic and accessibility | Is the whole journey right to left and usable with assistive technology? | Arabic walkthrough; accessibility test results | Medium |
| Data residency and biometrics | Where are documents and templates stored, and for how long? | Data flow diagram and retention policy | High |
| Audit trail | Can an examiner follow one case without help? | Exported case file | High |
| Integration effort | What did core and CRM integration take elsewhere? | Interface specifications and effort breakdown | Medium |
How is business onboarding (KYB) different from individual onboarding?
Verifying a company is a different problem from verifying a person, and many solutions that handle individuals well treat business onboarding as a document upload form. A business case has several parties: the legal entity, its beneficial owners, its directors and its authorised signatories, each of whom must be identified as an individual and screened. The entity itself has to be verified against registry or licence data, its ownership structure understood, and its activity risk-rated.
Ask how the solution models ownership chains, whether it connects to the commercial registries of your markets or relies on uploaded documents, how it collects signatory mandates, and how one case with several people at different stages is presented to a reviewer. Expect a higher share of manual review than in retail, and judge the review console accordingly.
What are the red flags when comparing eKYC vendors?
Most weak proposals show the same signs.
- Liveness claims with no independent test report, or a report for a different product version.
- National identity integration described as planned, or delivered through a third party the vendor will not name.
- Journey or rule changes that need a change request to the vendor.
- Biometric data processed or stored in a location the vendor cannot state precisely.
- A screening demonstration that uses only Latin-script names.
- An audit trail that records automated steps but not reviewers’ decisions and comments.
- Approval rates or completion times quoted from other clients, with no offer to measure them on your traffic.
- No answer on re-KYC: what happens when an ID expires or a customer’s risk rating changes.
How should you pilot an eKYC solution, and what should you measure?
Run a pilot with real applicants in one market and one product before you commit, and agree the measures and their definitions with the vendor in writing first. A common target is under five minutes to a funded account for applicants who pass cleanly, but treat that as an aim to test, not a figure to accept from a brochure.
Add two tests of your own. Have your fraud or security team attempt presentation attacks (printed photos, screen replays, masks) under controlled conditions, and have compliance pull case files at random and try to reconstruct each decision from the file alone. Then measure the following on your own traffic.
- Completion rate: applications finished as a share of applications started, with drop-off shown per step.
- Time to funded account: from the first screen to an account that holds money, reported as a median and for the slowest applicants.
- Straight-through rate: the share of applications approved with no manual touch.
- False rejection and retry rate: genuine applicants failed by document, face match or liveness checks, and the attempts they needed.
- Screening false positive rate: alerts cleared as not a match, as a share of all alerts.
- Manual review time: from a case entering the queue to a decision.
- Fraud caught and fraud missed: impersonation attempts stopped at onboarding, and those discovered later.
How Eurisko fits
Eurisko has delivered banking software since 2009. Our Digital Onboarding System covers the pipeline described in this guide: guided document capture with OCR tuned for Arabic and Latin scripts, active and passive liveness with face match, sanctions and PEP screening through the screening providers you choose, risk scoring configurable per market, a maker-checker review console with four-eyes approval, automatic customer creation in your core and CRM, and a case file for every applicant. It connects to national ID verification services where available, supports business onboarding with document workflows and authorised-signatory checks, and deploys on-premise or in your private cloud so that identity data can stay inside your perimeter. It runs standalone, embedded in your existing app, or as the opening journey of Eurisko DXP. Ask us for the same evidence this guide tells you to ask of anyone.
We are not the right choice if you need only a single component, such as a liveness check or a screening feed to plug into an onboarding flow you already run: a specialist component supplier is the simpler route.