Biometric
Biometric Auth · Re-verification

Verify once — then confirm with your face.

A customer verifies once. From then on, the system recognizes them by face — when withdrawing funds, resetting a password, or signing in on a new device. One selfie instead of passwords and SMS codes.

<1 secauthentication time
99%+recognition accuracy
1 selfieinstead of login + password + SMS

Clients who trust us

NurbankOtbasy BankBinancenaimi.kzBank RBKTennisi.kzSun FinanceShinhan FinanceKcellNPCK — National Payment Corporation of Kazakhstan
A FAMILIAR PAIN

Password stolen. SMS intercepted. Is this really the owner?

A critical operation — a withdrawal, a password reset, a new device — cannot rely on something that can be handed to someone else.

A face cannot be forwarded in a chat and cannot be stolen from a database. One selfie in the moment, and the system knows who is in front of the camera.

USE CASES

One selfie, where a password and SMS used to be.

01 · WITHDRAWALS

Withdrawals and transfers

Before a large transfer, the system asks for one selfie and confirms that the account owner — not a fraudster with a stolen password — is moving the funds.

02 · PASSWORD RESET

Password reset and account recovery

Forgot a password? One selfie replaces the email → SMS → security-question chain. Faster for the customer and safer for the business.

03 · NEW DEVICE

Signing in on a new device

A new phone or browser triggers a face confirmation. If it is the same person who registered, access is granted immediately.

04 · SIGNING

Signing documents and agreements

Before signing an important document, biometric confirmation proves that the account owner — and no one else — is the signer. Legally binding.

How it works

Recognize once — then confirm with a face every time.

01

You verify the customer once

During onboarding, the customer shows their face: liveness plus a match against a document or selfie. That creates the reference — the "who is this" for every sign-in that follows.

02

The system remembers — without the raw photo

An encrypted biometric template (a hash) is stored, not a picture from the camera. A database leak never hands a fraudster "your face".

03

Every critical action is re-checked

Withdrawals, password resets, new devices: one selfie is compared with the template. A 99.9%+ match lets the operation through. A stranger with the password does not get through.

For developers

A familiar integration path for developers

Use ready-made SDKs and APIs when your team wants to assemble the architecture itself.

JS · Webview

Web SDK / Flow Widget

A ready JavaScript camera widget for your website or an embedded mobile browser (webview). Its appearance is fully customizable to your brand.

JavaScriptCustom designWebview
iOS · Android

Mobile SDK

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

SwiftKotlinOffline-ready
Backend

REST API

Direct access to protected liveness endpoints for your own server-side logic. Authorized with a private X-API-KEY.

RESTX-API-KEYServer-side
AI · AGENTS

MCP server for AI agents

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

MCPClaudeAI agents
liveness — REST API
# Check liveness for a 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" } }

Numbers and facts

<1 sec
re-verification timeThe check runs inline and never interrupts the customer's flow.
99.9%
match accuracy vs. the referenceFAR/FRR levels validated by the independent NIST FRVT benchmark.
4 scenarios
critical operations coveredWithdrawals, password resets, new devices, document signing.
0 passwords stored
only a template hash is keptA database leak never hands a fraudster a customer's face.