Does Biometric.Vision replace the AML and antifraud platform?

No. Biometric.Vision is a biometric layer inside the existing antifraud stack: document, liveness and face checks, repeat-face search and step-up. Transaction monitoring, investigations and the final risk verdict stay in the operator’s stack.

How does biometrics stop bonus abuse and multi-accounts?

Face match ties the account to the document holder, and Face Search finds repeat registrations in the operator’s own player database. What to do with a match is decided by the operator’s risk rules.

How is the player’s age checked?

The system extracts the date of birth from the document during eKYC. The operator applies its age and jurisdiction rules to that data; a separate selfie-based age estimate is not the basis of this scenario.

What happens before a payout?

The operator’s risk rule calls Face Captcha: the player re-confirms the face already linked to the account at registration. The result returns to the risk engine and feeds the operator’s payout decision. A full document check does not have to be repeated.

Does the solution protect against deepfakes?

Passive liveness checks whether a live person is in front of the camera and blocks photos, videos, masks and deepfakes. Attack resistance is confirmed to ISO 30107-3 Level 2.

Biometrics for iGaming

One real player — one account

At registration Biometric.Vision ties the account to a live document holder and detects repeat faces. Before payout the system re-confirms the player. It is a biometric layer for the operator’s existing antifraud stack — no need to replace the AML or compliance platform.

An honest user gets a short eKYC. Someone else’s document, a deepfake or a brand-new account is not an easy way to collect a bonus or a payout.

Start free Request a demo

Session · player_onboardingSuccess

matchedface ↔ document

Player document captureddata extracted

Passive liveness checkpassed

Face match with documentmatched

Step-up before payoutavailable

Bonus hunting and multi-accounts · controlled by the player’s face

Player admitted to the accountVerdict returns to your player journey

Sound familiar?

Bonuses go to people the promo was never meant for

A heavy check stops real players before the first bet. A weak one lets bonus hunters, someone else’s documents and account farms through — and the marketing budget leaves with them.

Biometrics keeps a short path for the honest player and blocks fraud from registration to payout.

Player streamlive

Registration 4831Deepfake on camera · bonus accountrisk

Registration 4832Someone else’s document · bonus hunterrisk

Registration 4833Repeat face in the operator databasereview

Registration 4834Document · liveness · face matchedapprove

Real players and bonus hunters share one stream — split them before the first payout.

Document recognition

eKYC and age control start from one document

The player uploads a document — the system extracts the data and checks integrity. No manual field entry and no long form. Document anomalies show up before the next step, and the date of birth enters the operator’s rules with the rest of the data. So age does not need a separate scenario.

Support for 433+ document types from 180+ countries lets you onboard players across markets with one scenario.

Session · player documentCaptured

Document typerecognized

Holder dataextracted

Date of birthin age rules

Portrait from documentready for match

Document types433+

Countries180+

Manual entrynot needed

Responseto your onboarding

Document in sessionData available to the next verification step

Liveness check

In front of the camera — a live player, not their photo or a deepfake

Passive liveness does not ask anyone to turn their head or repeat commands. For a real player it is a short registration step. A photo, a screen recording, a mask or a deepfake will not pass.

Attack resistance is confirmed to ISO 30107-3 Level 2.

Session · passive livenessLive person

Photo instead of a facenot found

Video from a screennot found

Masknot found

Deepfake signsnot found

Liveness confirmed without commandsTested to ISO 30107-3 Level 2

Face match

Someone else’s document will not build a believable account

The system matches the player’s face to the photo in the document. Even a genuine document does not prove identity if another person is in front of the camera.

The algorithm is independently tested in NIST FRVT and ranked 37th among 570+ solutions. Match accuracy is 99.9997%.

Session · face matchMatched

Player

Document

Face in frame and portrait from documentsame person

Operator similarity thresholdpassed

Document holder confirmedMatch threshold is tuned to the operator’s rules

Re-confirmation

Before payout the owner’s face appears — not a new full KYC

On payout, a large stake or signs of account sharing the operator’s risk rule calls Face Captcha with one request from the existing flow. The service re-matches the player to the identity confirmed at registration and returns the result to the risk engine. The final payout verdict stays with the operator, and an honest user does not redo the full onboarding.

The verdict is formed in 1.4 seconds.

Session · payoutAllowed

Now

Registration

18:40Payout requestcreated

18:40Face Captchamatched

18:40Full KYC againnot needed

18:40Result to risk engine1.4 sec

Payout — to the account ownerThe payout decision stays with the operator

Promo protection

A new account does not make the player a new person

Face Search compares the face to the operator’s own player database — with no cross-operator pool — and returns matches found. The risk team joins them with device signals to catch multi-accounts, bonus hunting and re-registrations of blocked players. What happens next is decided by the operator’s risk rules.

Average search speed across the operator’s face database is ~1.5 sec.

Face Search · operator databaseSearch complete

New registrationFace compared to the operator’s player database1:N

match

Average face-database search speed~1.5 sec

Repeat face in your databaseNext — the operator’s risk rules

For developers

Classic integration

If your team prefers to assemble the architecture itself, connect ready SDKs and APIs.

JS · Webview

Web SDK / Flow Widget

A ready JS camera component for web registration or an in-app Webview. The check runs inside your onboarding; the design follows your brand book.

JavaScriptCustom designWebview

iOS · Android

Mobile SDK

A native verification flow in the mobile app: camera access and biometric micropacket transfer even on a weak connection.

SwiftKotlinOffline-ready

Backend

REST API

Layer results and the final verdict arrive in your backend logic: risk rules and the decision stay on your side. Auth via X-API-KEY.

RESTX-API-KEYServer-side

AI · AGENTS

MCP server for AI agents

Connect checks to agent scenarios without writing glue code. Works with Claude, GPT and any MCP client.

MCPClaudeAI-agents

player_onboarding — REST API

# Player onboarding / player_onboarding

POST /v1/verification/check/

Host: api.biometric.vision

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

Content-Type: application/json

{ "scenario": "player_onboarding", "checks": ["document", "liveness", "face_match", "face_search"] }

# → 200 OK

{ "status": "completed", "live": true, "face_match": "match" }

37 / 570+NIST FRVT rank

99.9997%match accuracy

ISO 30107-3Level 2 — liveness

ISO 27001No. 760281

Questions and answers

The scenario stays short: data is read from the document automatically, and passive liveness does not ask for camera commands. Extra checks can stay on risk actions instead of running on every login.

500 checks a month free

Protect the path from registration to payout

Combine eKYC, repeat-registration control and step-up in one player journey. Start with a test scenario or walk through the points where you lose money on a demo.