A tier-1 commercial bank · Addis Ababa
Onboarding across the branch network
Verification moved into the branch conversation instead of after it. Every decision carries a reconstructable evidence trail.
eKYCBanking
Flagship capability
Onboarding in minutes.
Onboarding in minutes.
Evidence built for regulatory review.
Document OCR, liveness detection, face matching and verification against Ethiopia’s national digital ID — performed in one journey and logged end to end. Branch officer, mobile agent or online applicant: the same controls apply.
Verification result
Approved
Face match
0.98score
Document OCR
99.2% confidence
Authoritative checks
National digital IDMatched
AML / PEP / sanctionsClear
LivenessConfirmed
The problem
Where manual onboarding actually costs you.
It is rarely the headcount. It is the customer who walks out, the file that cannot be reconstructed six months later, and the audit finding nobody can explain.
Today, without eKYC
- Applicants wait days for a decision, and a share of them never come back.
- Document checks depend on how careful the officer was that morning.
- Screening runs in a separate system, and the results live in someone’s inbox.
- When the regulator asks how a decision was made, the trail is incomplete.
With eLON eKYC
- The applicant is verified in a single sitting, in front of the officer or on their own phone.
- Document, face and liveness checks return a score and a threshold decision, not a judgement call.
- AML, PEP and sanctions screening run in the same flow, and the outcome is stored with the case.
- Every case exports a complete evidence trail — consent, operator, timestamps, results.
How it works
Five steps, one case record.
STEP 01
Capture
Identity document photographed or scanned. OCR extracts the fields; MRZ and checksums are validated.
STEP 02
Liveness
Active liveness challenge is designed to detect printed photos, screen replays and masks before any comparison runs.
STEP 03
Face match
The live capture is compared against the document portrait and returns a match score against your threshold.
STEP 04
Authoritative check
Details are verified against Ethiopia’s national digital ID and the registries you are entitled to query.
STEP 05
Screen & decide
AML, PEP and sanctions screening run; the case is auto-decided or routed for review, with the reason recorded.
Architecture
It plugs into what you already run.
We do not ask you to migrate your onboarding onto a platform you cannot control. The verification layer sits between your channels and the sources of truth, and you keep your own system of record.
Your channels
Branch desk, mobile agent app, call centre, web or app onboarding. Multi-language UI.
eLON verification layer
Orchestration, score thresholds, review queue, consent capture, retention policy and audit export.
Authoritative sources
National digital ID and the registries you are entitled to query, plus AML / PEP / sanctions lists.
Your systems
Core banking, CRM or onboarding platform, through documented APIs. Your system stays the record.
Deployment location is a configuration choice, not a fixed constraint. Identity and biometric data are treated as the most sensitive category and are governed by the Data Protection Statement agreed with you.
Commercial model
Two ways to buy it.
Which one fits depends on your volume profile and how much of the cost you want fixed. We recommend only after seeing the numbers — and there is no obligation to pick either at this stage.
Per verification
For variable or seasonal volume, pilots, and institutions that prefer to pay as they grow.
- Unit price per completed verification, tiered by volume
- No minimum commitment to discuss
- Cost tracks actual onboarding activity
Usually preferred at scale
Subscription with committed volume
For established onboarding volume where a predictable monthly line item matters more than flexibility.
- Lower unit rate against a committed monthly volume
- Predictable cost for budgeting and regulatory reporting
- Includes support and service levels agreed per tier
In production
What it looks like once it is live.
A microfinance institution
Field agents working offline
Enrolment captured outside network coverage and synchronised on return, so remote applicants are not excluded by connectivity.
Offline modeMicrofinance
A telecom operator
SIM registration at retail scale
Liveness and face matching applied at the point of sale, with an audit export the regulator can be handed directly.
LivenessTelecom
* Client identities are withheld. Written references are available under NDA during a procurement.
Technical FAQ
What the technical evaluation asks.
How long does an eKYC integration take?
It depends mainly on which source systems need to be connected and how much of your workflow changes. A pilot scoped to one channel and one registry is materially faster than a full rollout across branches with core-banking integration. We give you a realistic sequence after a scoping session rather than a headline number.
What accuracy and throughput can you support?
Match scores and decision thresholds are configurable, so you set the balance between false accepts and manual review for your risk appetite. Throughput is sized against your peak — the design question is what happens at month-end or during a registration drive, not the daily average. Both are validated against your own sample during the pilot.
Where is customer identity data stored?
Storage location, encryption, retention period, access control and any cross-border transfer are defined in our Data Protection Statement and agreed with you contractually. Deployment location is a configuration choice. Identity and biometric data are treated as our most sensitive category, and access is tightly role-scoped.
Does it work when connectivity or power is unreliable?
Yes — this is treated as a design input rather than an exception. Capture can continue offline and synchronise later, and the interface is built for low-bandwidth conditions. The trade-off is that authoritative checks requiring a live registry query cannot be completed while offline; those are queued and resolved on reconnection, and the case state reflects that honestly.
Do you support Amharic and Afaan Oromo in the interface?
Yes. Operator and applicant interfaces are available in Amharic, Afaan Oromo and English, with a dedicated Ethiopic typeface so Amharic renders correctly rather than falling back to a substitute. Language coverage is agreed per deployment.
Resources
Take something to your committee.
Procurement usually starts with a document, not a call. These are the ones most often asked for — no form-filling beyond a name and a work email.
eKYC Capability Statement
One page per capability: what we deliver, what we integrate with, and the credentials behind it.
Integration Datasheet
API surface, deployment options, data-handling notes and the questions your CISO will ask.
Data Protection Statement
Storage location, encryption, retention, access control and cross-border transfer — in writing.
Next step
Show us one onboarding journey.
Bring a single real (desensitised) case — an account opening, a SIM registration, a loan application — and we will walk through where the current process loses time and where identity risk is currently uncontrolled. That conversation is free of charge and needs no commitment.
Request a Demo
A qualified engineer reviews your requirement before anyone calls you. No obligation, no sales sequence.