Biometric
KYC · Uzbekistan

KYC in Uzbekistanon Uzbek IDs

We read the Uzbek ID card and biometric passport, check liveness and match the selfie against the document photo. Fields come back in Uzbek and Russian.

One API covers onboarding for a bank, a microfinance or a payment organization — no paper forms, no branch visit.

Uzbek documents

We read Uzbek documents in the original

OCR extracts the visual zone and cross-checks it against the MRZ. The models are trained on both Latin and Cyrillic, so Uzbek and Russian fields come through without transliteration.

ID card

The newer domestic document with a chip. We read the visual zone and MRZ, PINFL included.

Biometric passport

The citizen's passport and earlier series: MRZ, validity, holder photo for face match.

Driving licence

For flows where a passport is optional: rentals, sharing, delivery, driver checks.

Foreign documents

433+ document types from 180+ countries. Non-residents, visitors and labour migrants go through the same check as Uzbek citizens.

A residence permit or a neighbouring country's passport in the frame changes nothing. The document is detected automatically; its type and country come back in the API response.

Regulation

Built around Uzbek regulators' requirements

You answer to the Central Bank and to the financial intelligence unit. We supply the tools that meet the requirement — and the log that proves it was met.

CBU

Remote identification

A bank or payment organization has to be sure the document is presented by its holder, not by whoever sent the photograph. Liveness and face match produce that evidence; our liveness is tested to ISO/IEC 30107-3 against presentation attacks.

AML/CFT

Identification and screening

Identifying the customer and screening them against lists are baseline duties of a financial monitoring entity. AML screening — sanctions, PEPs, wanted lists — runs in the same request as the document check.

Personal data

Data localisation

Uzbekistan requires personal data of its citizens to be processed inside the country. Storage location and retention are configured to your policy, and we collect only what the check itself needs.

Localisation rules and identification procedures change more often than a landing page is rewritten. The final compliance call belongs to your compliance officer; we provide the tooling and the evidence for it.

Integration

Connect the way you prefer — AI agents included

Widget, mobile SDKs, REST API and an MCP server. Uzbek documents verify the same in all four; only the way you call it differs.

JS · Webview

Web SDK / Flow Widget

A ready camera widget for your site or an in-app browser. Prompts switch to Russian, and the design follows your brand book.

JavaScriptCustom designWebview
iOS · Android

Mobile SDK

Native libraries with direct camera access. Biometrics go out in small packets, so a check still completes on weak mobile data in the regions.

SwiftKotlinWeak network
Backend

REST API

Direct access to the verification endpoints for your own server logic. Auth by a private X-API-KEY; the result arrives on a webhook.

RESTX-API-KEYWebhooks
AI · Agents

MCP server for AI agents

An AI agent starts a check and reads the result itself, with no glue code in between. Works with Claude, GPT and any MCP client.

MCPClaudeAI agents
uz_onboarding — REST API
# Create a verification session: country UZ selects the Uzbek document set
POST /v1/sessions
Host: api.biometric.vision
X-API-KEY: sk_live_••••••••••••••
{ "scenario": "uz_onboarding", "country": "UZ", "checks": ["document", "liveness", "face_match", "aml"] }
# → 200 OK
{ "session_id": "sess_4c81…", "status": "created", "url": "https://flow.biometric.vision/s/sess_4c81…" }
Why us

A platform already working in the region

Central Asia is home turf

We are a vendor of the Centralized Identification System of the National Bank of Kazakhstan; Otbasy Bank, Nurbank and Binance run on the platform. Uzbekistan is a neighbouring market with the same onboarding flows and the same demands on documents.

Accuracy measured by NIST

Our face comparison algorithm ranks 37th out of 570+ in the independent NIST FRVT benchmark. Liveness is tested to ISO/IEC 30107-3 against presentation attacks.

Support in English and Russian

Integration is guided by a team that works in English and Russian — the languages your developers actually use. The docs come in both too.

Pricing you can see upfront

Plans and the calculator are public. Start with 500 free checks a month and price your volume before signing anything.

433+
document types recognized
180+
countries covered by OCR
37 / 570+
rank in NIST FRVT
500
free checks every month
FAQ

Questions about KYC in Uzbekistan

Yes. The ID card is read in full: visual zone, MRZ, fields in Uzbek and Russian, PINFL included. Biometric passports and earlier series are supported too.

The storage location is configured to your policy, including keeping data inside the country. We collect only what the check itself needs, and you set the retention period.

Yes, with the same API: 433+ document types from 180+ countries. A visitor or a labour migrant needs no separate flow — the document type is detected automatically.

Screening against sanctions, PEP and wanted lists runs in the same request as document verification and lands in the same session log.

Registration gives you 500 free checks a month, no card required. Beyond that, use the calculator: the price depends on the modules and volume.

REST API and a web widget; a typical integration takes about 30 minutes. The sandbox opens right after registration and issues the keys.
KYC for Uzbekistan

Test us on Uzbek documents

Registration takes a minute and the sandbox issues keys right away. Run your first check today — 500 a month are free.