What if a legitimate customer's face does not match?

The API returns manual review status with a reason. You can hold the withdrawal, give the customer another attempt, or pass the result to an operator — permanently blocking the account is not required.

Does your AML check the wallet and transaction?

No. The biometric.vision AML module screens the person's identity against sanctions, watchlists, and PEP lists at registration and re-KYC. Wallet and on-chain movement checks are handled by separate specialized systems.

How do you find multi-accounts?

1:N search compares a face against the platform database in about 1.5 seconds. If a possible match is found, the system surfaces it to an operator for review.

Where is data stored / is on-premise possible?

By default data is stored in the biometric.vision cloud. If regulation requires a separate perimeter, on-premise or private deployment is available. We align configuration with your security team.

Biometrics for crypto platforms

Verify the owner at login and before withdrawal

A crypto transaction cannot be reversed. That is why biometric.vision matches the customer's face at registration, before withdrawals, during account recovery, and at periodic re-KYC. Checks take seconds, and the platform gets a verdict before funds leave.

500 checks a month — free

No card. No commitment. Integration in 30 minutes

Start free Request a demo

Verification · withdrawal_verificationPASS

Face matchedselfie and account owner photo

Document readtype identified

Liveness confirmedlive person

Face matchedconfirmed

AML screeningclear

Approve withdrawalVerdict with reason · before funds are sent

Wrong face and deepfakes are rejected automatically

Sound familiar?

A night withdrawal went through. In the morning the owner says it wasn't them

The password worked, 2FA passed — and the transaction went to an external address. It can no longer be cancelled.

The document showed who opened the account. But before a withdrawal you need to confirm the same person is in front of the screen now.

What changes: the platform asks for a live selfie and matches it to the owner's face. Stolen credentials alone are no longer enough to withdraw.

Wallet

03:00

Withdrawal confirmed− 4.20 BTCTo external address bc1q••••7ha9 · irreversible

New device · password login

Transaction is on-chain — cannot be reversed.

From registration to withdrawal

Confirm the owner across the full risk path

At registration the account is linked to a person. The same check then runs before withdrawal, when security settings change, and during account recovery. The API returns a verdict — approve, reject, or send to manual review — with the reason for the decision.

At the moment of risk

Large withdrawal

The customer takes a new live selfie and the system matches it to the person who opened the account.

Match against the account owner's faceVerdict before the transaction is sent

Matched

Settings change

The owner confirms a new login method or security reset.

Liveness and face match before the changeEvent is recorded in your system

Liveness confirmed

Face matched to owner

New login method confirmed

Apply changes

Account recovery

Liveness and face match help return the account to the person who opened it.

Search across the platform face databaseEdge cases go to an operator

Recovery requestmatch against account owner database

Database · 1,240,508

Account owner confirmed

Primary scenario — CEX

Built for your model

The main scenario on this page is a centralized exchange. On/off-ramp and custody use the same check at their own points of access to funds.

Centralized exchange (CEX)

Confirm the owner before withdrawal and during account recovery.

On/off-ramp

Get a clear status after document and selfie checks.

Wallets and custody

Make sure recovery or critical settings are changed by the owner.

Live person check

Liveness alone is not enough — you need a separate layer against spoofing

That is why at registration and before withdrawal deepfake protection

Checks are complemented by device and network signals: virtual camera, VPN, suspicious device

The system detects

Photos and recorded videoblocked

Silicone and 3D masksblocked

AI-generated facesblocked

Camera stream substitutionblocked

For developers

Classic integration for developers

Embed checks into your architecture with ready-made SDKs and API.

JS · Webview

Web SDK / Flow Widget

Ready web flow for document, selfie, and re-check. Design adapts to your interface.

JavaScriptCustom designWebview

iOS · Android

Mobile SDK

Native capture and in-app guidance, resilient on weak networks.

SwiftKotlinOffline-ready

Backend

REST API

Trigger checks from your risk system and get a structured verdict. Authorized via X-API-KEY.

RESTX-API-KEYServer-side

AI · AGENTS

MCP server for AI agents

Connect biometric checks to agent workflows and control the outcome.

MCPClaudeAI-agents

withdrawal_verification — REST API

# Re-check before withdrawal

POST /verifications

Host: api.biometric.vision

X-API-KEY: sk_live_••••••••••••••

Content-Type: application/json

{

"scenario": "withdrawal_verification",

"customer_id": "customer_reference",

"checks": ["liveness", "face_match"]

}

# → 200 OK

{ "status": "review", "scenario": "withdrawal_verification", "next_action": "hold_withdrawal" }

Trust

Crypto platforms choose Biometric.Vision

ISO/IEC 27001:2022Certificate No. 760281

ISO/IEC 30107-3:2023 Presentation Attack Detection certificate

ISO/IEC 30107-3:2023Presentation Attack Detection · No. RSBV-2504-8642

GDPRCertificate of compliance · No. RSBV-2504-8643

Questions and answers

What exchanges and compliance teams usually ask

That is up to your platform. Triggers can include amount thresholds, a new address or device, recent settings changes, or time since the last check. biometric.vision receives a request only for the events you choose.

500 checks a month — free

Test biometrics where a mistake is already irreversible

Run checks on your own registration and withdrawal flow. See which statuses and reasons the system returns for normal and suspicious sessions.

Start free Request a demo

Numbers and facts

433+

Document types

Support for passports and hundreds of other document types worldwide

180+

Supported countries

Global coverage for verification across jurisdictions

40 sec

Onboarding time

Registration and user verification in under a minute

99%

Technology accuracy

High-precision AI-based document recognition and verification