Biometric
Banking · eKYC and AML

eKYC for banks and secure remote customer onboarding

Open accounts remotely with one configurable workflow for document verification, liveness, face matching and AML screening. Deploy in the cloud or inside the bank perimeter.

The main risk of digital onboarding

Banks shouldn't have to choose between security, compliance and conversion

Remote account opening has to work for genuine customers — and shut the door on those arriving with forged or leaked passports, front people (money mules) and synthetic identities. Otherwise fraud losses, staff workload and regulatory risk all grow.

A check that's too strict sends customers back to branches. One that's too weak invites fraud and regulator questions. The bank's task is to make the check invisible to a genuine customer and impossible for an attacker.

Onboarding flow

From the customer’s consent to a decision the bank can explain

One session, seven steps. Every step returns a result that stays with the session, so a decision can be reconstructed months later.

  1. 01Consent to data processing
  2. 02Document capture
  3. 03Liveness check
  4. 04Face match with the document
  5. 05AML screening
  6. 06Decision by your rules
  7. 07Audit trail

The order and the set of checks are assembled per scenario in the Flow builder: the bank sets the thresholds and decides what happens on a borderline result — a retry, a manual review or a rejection.

How a bank gets controlled online onboarding

Fraud protection, compliance and a smooth customer journey — in one scenario

Instead of a patchwork of separate services, the bank gets a single verification scenario. It protects against fraud, supports KYC/AML requirements and doesn't force customers through extra steps.

01

Don't lose the customer at the very first step

The customer gives consent, follows a short guide, completes a liveness check and scans their document. No branch visit is needed: the journey stays clear and takes minutes. The bank applies the same rules across the app, branches and kiosks — tuned to its own risk profile.

A clear journey with no branch visit
The same rules across every channel
A scenario tuned to your risk profile
02

Stop fraud before an account is opened

The system confirms a live person is in front of the camera — not a photo, video, mask or deepfake. For account opening the bank can choose DISTANCE or PRO; for repeat sign-in and lower-risk operations, the faster FAST mode fits better. You set the threshold and the rules yourself: when to route an application to compliance and when to auto-reject.

PRO (3D) — for high risk
DISTANCE — a balance of security and convenience
FAST — for sign-in and low risk
03

Run KYC and AML without a stack of separate services

The system reads a passport or ID, matches the face against the document photo and simultaneously screens the data against sanctions and other lists: OFAC, EU, UK, Dow Jones, plus national registries. This lets you run KYC/AML checks in a single process and act on a match immediately.

We confirm identity against the document
AML screening doesn't add friction for the customer
Someone else's document can't open an account
04

Get a decision you can verify and explain

The bank receives a single result: whether identity was confirmed, liveness passed, the document was read, the face matched and whether there are AML risks. The session stores photos, the liveness check video, document fields, an event log and webhooks. That gives staff a transparent decision history and lets them reject suspicious applications without a manual branch review.

One integration instead of several systems
A full decision history in the dashboard
Where it applies

Which modules each banking scenario needs

ScenarioModules in the flowWhat the bank gets
Account openingDocument verification · liveness · face match · AML screeningA verified customer and a decision record for the file
Loan applicationDocument verification · liveness · face match · AML screeningIdentity confirmed before the credit decision, not after it
Card issuance for an existing customerLiveness · face match against the saved templateNo repeat document scan for a customer already verified
Account recoveryLiveness · face match against the saved templateA recovery path that a stolen phone alone does not open
Periodic re-verificationLiveness · face match · repeat AML screeningRefreshed customer data without a branch visit
Reusable KYC

One KYC — less friction across the bank's whole ecosystem

After a successful identification, a customer doesn't need to scan documents again when applying for a card, a loan or an investment product — confirming identity by face is enough. That shortens the path to the next product and helps keep the customer inside the bank's ecosystem. With an On-Premise deployment, biometric data stays inside your perimeter.

One KYC for accounts, cards, loans and investmentsOn-Premise
minutesonline account opening
<1 secfast liveness check
37 / 570+NIST FRVT rank
ISO 27001information-security certification
Deployment and data

Where the data is processed and what the bank can show later

Deployment
Cloud, or On-Premise inside the bank perimeter.
Where processing happens
With On-Premise the core runs on the bank’s servers and biometric data does not leave the perimeter.
What a session holds
Photos, the liveness result, document data and the module verdicts, tied to one session id.
Audit trail
Session events — created, liveness, face match, AML, closed — are readable in the dashboard and can be delivered to your systems through webhooks.

These are controls, not a compliance guarantee: which of them satisfy a given requirement depends on the jurisdiction and on the bank’s own procedures. Retention periods and deletion rules are set for each deployment — agree them before launch.

For developers

Classic integration for developers

If your team prefers assembling the architecture by hand, use our ready-made SDKs and APIs.

JS · Webview

Web SDK / Flow Widget

A ready-made JS camera widget for your website or embedded mobile webview. Fully customizable design to match your brand.

JavaScriptCustom designWebview
iOS · Android

Mobile SDK

Native libraries for mobile apps. Deep access to the smartphone camera and biometric micro-packet transfer even on weak 3G connections.

SwiftKotlinOffline-ready
Backend

REST API

Direct access to secure liveness-check endpoints for building your own server-side logic. Authorization via a private X-API-KEY.

RESTX-API-KEYServer-side
AI · AGENTS

MCP server for AI agents

AI agents connect to verification directly — with no code. Compatible with Claude, GPT and any MCP client.

MCPClaudeAI agents

Documentation: assembling a flow · webhooks and events · REST API reference

liveness — REST API
# Check liveness by session_id
POST /v1/liveness/check/
Host: api.biometric.vision
X-API-KEY: sk_live_••••••••••••••
Content-Type: application/json
{ "session_id": "sess_9f2a…", "mode": "active" }
# → 200 OK
{ "live": true, "score": 0.999, "checks": { "deepfake": "pass", "mask": "pass" } }

Questions and answers

For account opening, banks typically choose DISTANCE or PRO — including with active actions (3D). FAST mode is convenient for repeat sign-in and low-risk operations and shouldn't be the only onboarding method. The passing threshold and decision zones — route to compliance or auto-reject — are configured by the bank.

Liveness rejects photos, video, masks and AI-generated faces. Document matching confirms that the person in front of the camera is the same one on the passport or ID. Device analysis helps spot proxies, VPNs, emulators and other suspicious signals. A front person or someone else's passport won't pass this check.

Customer data is automatically screened against international sanctions lists (OFAC, Consolidated EU, Consolidated UK, Canada, Dow Jones), wanted-persons lists and national registries — including terrorism/WMD financing lists and bank blacklists. The check is invisible to the customer; results are available in the dashboard.

It gives you controls, not an automatic yes. The platform holds an ISO/IEC 27001 certificate and its face-recognition algorithms are ranked in the NIST FRVT evaluation; On-Premise deployment keeps biometric data inside the bank perimeter, and every session leaves an audit trail. Whether that satisfies a specific requirement depends on the jurisdiction and on the bank’s own procedures, so plan a local legal review before launch.

With On-Premise, the platform is deployed on the bank's own servers: biometrics and check results never leave your perimeter. Sessions — photos, the liveness-check video, document data and logs — are stored in the dashboard; data is encrypted both in transit and at rest.
500 checks a month free

Protect the bank's digital growth — with no extra friction for customers

Create a developer account and build an account-opening verification scenario. See how a single platform helps protect onboarding, run KYC/AML and keep the customer journey smooth. The first 500 checks a month are free, no bank card required.

Numbers and facts

433+
Document types —Support for passports and hundreds of other document types worldwide
180+
Countries supported —Global coverage for verification across different jurisdictions
40 sec
Onboarding time —Registration and verification in under a minute
99%
Technology accuracy —High-precision AI-based recognition and document verification