Identity verification · Built to your process
eKYC built around your onboarding, not a generic widget.
We build eKYC flows for your app, website or branch: ID reading, face matching, liveness checks and hand-off to your systems. You decide where the data is stored and who can see it.
A typical eKYC flow
- Capture the IDID card or passport photographed in the app or browser
- Read and checkText read from the document, format and expiry checked
- Selfie and livenessA live person, compared with the ID photo
- DecisionApproved automatically, or sent to your staff to review
- Your systemsResult and evidence passed to CRM, core system or contract signing
Live demo
Try face liveness yourself
This is the liveness step from our eKYC engine: look at the camera for a few seconds and it tells a real person from a photo or screen. No ID document is needed.
Your browser will ask for camera access. Images are not stored; the demo returns only pass or fail with a score.
What we build
The parts of an eKYC flow
- Document capture and reading: guided photo capture, text extraction from ID cards and passports, including the machine-readable zone
- Face match: comparing the selfie with the photo on the document, with a score your rules act on
- Liveness check: confirming that a real person is in front of the camera, not a photo or a screen
- Review console: a queue where your staff see the images, extracted data and scores, and approve or reject
- Audit trail: who was verified, when, with which evidence and which decision
- Integration: APIs and webhooks into your CRM, core system, or a digital signing step with a certificate
Why custom
Fitted to your rules and your data location
Off-the-shelf eKYC services decide your flow and where ID images are stored. A custom build lets you set thresholds, wording, languages and hosting region, and link verification to the next step.
- Web, Android and iOS, in English, Vietnamese and other languages
- Hosted in your environment or ours, in a region agreed with you
- Rules for automatic approval, manual review and retries set by you
- Can use recognised third-party verification engines where you prefer them
Required checks depend on your industry and country. We build to the requirements you and your advisers set; we do not give regulatory advice.
Engagement
How a project runs
- Scoping call: who is verified, which documents, which countries, what happens after.
- Proposal: the flow, the screens, where data lives, how it is tested, and the price.
- Pilot with a small group of real users, then tuning of thresholds and wording.
- Launch and support, with the same team maintaining it afterwards.
Questions
Frequently asked
Is this an off-the-shelf eKYC product?
No. We build the eKYC flow to your process, screens, languages and data location, and can use recognised third-party verification engines where you prefer them.
Does One Sign advise on KYC regulations?
No. We build to the requirements set by you and your compliance or legal advisers; we do not give regulatory advice.
Planning online onboarding?
Tell us who you need to verify and where, and we will propose a flow.