How to Choose a Digital Onboarding and eKYC Solution in Lebanon

By Eurisko Team · Last reviewed November 2026

Digital identity card surrounded by verification services

To choose a digital onboarding and eKYC solution in Lebanon, start from Banque du Liban’s Basic Circular 69, rewritten in January 2026, which makes e-KYC a service that needs BDL’s prior approval, and from Basic Circular 83 on anti-money laundering controls. The texts name no national digital identity service to lean on, so the solution must prove identity through document checks, biometric matching and liveness, keep that evidence in a file a reviewer can defend, and store it in Lebanon. Score vendors on the strength of that evidence, and on the documentation they can give you for the approval request, before you compare speed.

This guide opens with what BDL publishes, summarises how the Gulf markets differ, and then sets out the vendor-neutral core: what the solution must do end to end, the criteria and evidence to request, business onboarding, red flags and how to pilot.

Lebanon: what do BDL’s circulars mean for remote onboarding?

Two BDL texts frame the decision. Basic Circular 83 (Basic Decision 7818 of 18 May 2001) carries the regulations on the control of financial and banking operations for fighting money laundering and terrorist financing. It requires banks to check a natural person’s identity from a passport, an identity card, an individual civil registration or a residence permit, and to classify customers as low, medium or high risk, and it lists the bank’s non-face-to-face customers among the risks to take into account. For customers classified as high risk it calls for more detailed information, administrative approvals according to the risk level and periodic review of the relationship.

Basic Circular 69 (Basic Decision 7548) governs electronic banking and financial operations, and its articles were replaced in full by Intermediate Decision 13791 of 9 January 2026. The current text has a dedicated article on the e-KYC service. A bank may onboard new customers who are natural persons through an E-KYC Form to open payment accounts up to a ceiling of USD 10,000 (BDL may approve a higher ceiling on a justified request), provided it first obtains BDL’s prior approval and submits the documents on the techniques, mechanisms and software it will use. The approval request must show enhanced due diligence, a Digital ID system that covers identity proofing and enrolment, authentication and lifecycle management as per the FATF Guidance on Digital ID, ongoing monitoring of electronic transactions under Circular 83, and customer classification by risk and by operation ceilings.

The same decision sets the conditions for an electronic signature, including the customer’s consent to the likely risks and a signature uniquely linked to the signatory, and states that the one-time password serves as the customer’s e-signature. It requires the bank to notify the customer of each operation as it is executed, and to store in Lebanon all data on customers and executed operations. Circular 83 also requires customer information and copies of the identification documents to be retained for at least five years after the account is closed, and it holds the bank responsible for accuracy when it relies on a third party for identification.

Three consequences follow for the selection. The vendor’s technical documentation is part of your approval file, so ask for it as a ready pack before you shortlist. The decision points to the FATF guidance and names no national digital identity service, so document authenticity checks, biometric matching and liveness carry the full weight of identity assurance, and the quality of that evidence matters more here than in the Gulf. And a solution that can only store identity data outside Lebanon does not fit the data hosting article. The English consolidation of Circular 83 on BDL’s website stops at amendments from the mid-2010s, so confirm its current Arabic text before you commit to a design.

How do the neighbouring markets differ?

If the same solution has to serve more than one country, the core pipeline stays the same and the identity rail, the evidence and the data rules change. The table summarises what the other central banks in the region publish; confirm the current text before you finalise requirements for any of them.

Remote onboarding by market: published rules and national identity rail
MarketWhat the central bank publishesNational identity railCheck with the vendor
Saudi ArabiaSAMA Account Opening Rules: remote opening for individuals, sole proprietorships and companiesNafath, the unified national access systemLive Nafath connection; who may be onboarded remotely
UAECBUAE guidance on digital identification for customer due diligenceUAE Pass and Emirates ID validationVerification record kept; data stored in the UAE
KuwaitCBK instructions to banks on AML/CFTKuwait Mobile ID from PACIVerification level used; enhanced checks for remote customers
OmanCBO instructions on digital onboarding and e-KYC (June 2023)National Digital Onboarding Registry with Mala’aRegistry connection; data fields returned

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 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.

Digital onboarding and eKYC scorecard: what to ask and what evidence to request
CriterionAsk the vendorEvidence to requestWeight
Identity assurance and livenessWhich standard was liveness tested against, and by whom?Independent ISO/IEC 30107-3 test reportHigh
National identity railIs the connection live in this market?Production reference and demonstrationHigh
Screening qualityHow are Arabic names matched and false positives cleared?Test results on your sample dataHigh
ConfigurabilityCan we change steps and risk rules without your code?A change made live in a workshopMedium
Drop-off analytics and resumeCan we see abandonment by step and resume across devices?Funnel report from a live deploymentMedium
Arabic and accessibilityIs the whole journey right to left and usable with assistive technology?Arabic walkthrough; accessibility test resultsMedium
Data residency and biometricsWhere are documents and templates stored, and for how long?Data flow diagram and retention policyHigh
Audit trailCan an examiner follow one case without help?Exported case fileHigh
Integration effortWhat did core and CRM integration take elsewhere?Interface specifications and effort breakdownMedium

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.

FAQ

Frequently asked questions.

What is the difference between digital onboarding and eKYC?

eKYC is the electronic identification and verification of a customer: capturing identity evidence, matching the person to it and screening them. Digital onboarding is the whole journey around it, from the first screen through risk rating, manual review of exceptions and account creation in the core, to the audit record. A solution that does only eKYC leaves the bank to build the rest.

Which standard should liveness detection be tested against?

ISO/IEC 30107-3 is the international standard for testing and reporting presentation attack detection, and NIST SP 800-63A requires such tests to conform to its 2023 edition when biometrics are collected remotely. Ask the vendor for the test report from an independent laboratory, and check the product version, the attack types and the devices it covers.

Is remote account opening treated as higher risk than opening in a branch?

It depends on the market and on the identity evidence. The FATF Guidance on Digital ID says non-face-to-face onboarding that relies on a reliable, independent digital identity system may be standard or even lower risk. Local rules still vary: the Central Bank of Kuwait requires enhanced due diligence for customers not dealt with face-to-face, and Banque du Liban lists non-face-to-face customers among its risk indicators.

Can one eKYC solution cover several Gulf markets?

Yes for the core pipeline of capture, biometrics, screening, risk rating, review and case file, provided it is configurable per market. What changes is the national identity rail (Nafath, UAE Pass and Emirates ID validation, Kuwait Mobile ID, Oman’s registry), the documents accepted, the retention rules and where data may be stored. Ask for a production reference in each market you need.

Is there a national digital identity for bank onboarding in Lebanon?

The BDL circulars reviewed for this guide do not name one. Basic Circular 69 as replaced in January 2026 asks for a Digital ID system in line with the FATF Guidance on Digital ID, and Basic Circular 83 lists the documents used to check a natural person’s identity (a passport, an identity card, an individual civil registration or a residence permit). A remote journey in Lebanon therefore relies on document verification, biometric matching and liveness, and needs BDL’s prior approval.

Let’s build

Have something ambitious in mind?

Start a project →

Popular searches

Jump to