Does the scenario fit different SIM registration rules?

Biometric.Vision returns document data, liveness status and the face match result. The operator plugs them into their own scenario and, following the requirements of each market, decides which data is mandatory and how the decision is made.

Does Face Captcha fully prevent SIM swap fraud?

No. Biometrics adds an owner check at the risk point and makes it harder to take over a number with an intercepted code or social engineering. The final decision stays with the operator’s risk rules and processes.

Is a full eKYC needed again for eSIM issuance or port-out?

If identity is already confirmed, a full eKYC does not have to be repeated. The operator can request only Face Captcha and compare the face with the original profile. A full check is needed when the owner changes or operator rules require the document to be verified again.

Does the solution replace device intelligence, AML or transaction monitoring?

No. Biometric.Vision is responsible for biometric identity confirmation. Device signals, transaction monitoring and other checks keep running inside the operator’s existing stack.

Where does the check plug in?

Into an app, a web scenario, a dealer flow or a CRM — via Web SDK, Mobile SDK, REST API or MCP. The operator defines the call points at activation and on risky actions.

Biometrics for telecom

Tie the number to a real person — from SIM activation onwards

The subscriber confirms their identity at connection. Before a SIM swap, port-out, eSIM issuance or self-care login, the operator asks for the owner’s face again. Biometric.Vision is a biometric layer inside your existing subscriber journey: a short eKYC for the honest subscriber, while someone else’s document, photo or intercepted code is not enough to control the number.

Start free Request a demo

Session · sim_activationSuccess

matchedface ↔ document

Document captureddata extracted

Liveness checkpassed

Face match with documentmatched

Liveness confirmedpassive

SIM activation · number linked to the document holder

Number can be activatedVerdict returns to your subscriber flow

Sound familiar?

An extra step slows activation down. A weak check hands the number to the wrong person.

A new subscriber does not want to fill in a long form and wait for a document to be reviewed by hand. And after connection the number stays a risk point: it gets reissued through support, ported to another operator, used to sign in to self-care.

If identity was verified only at registration, everything after that usually comes down to a one-time code or knowledge questions. After someone else’s SIM swap the operator has to work the incident, the contact centre takes the calls, and the subscriber may simply leave.

Activation streamlive

Activation 4831Deepfake on a prepaid activationrisk

Activation 4832Someone else’s document · someone else’s numberrisk

Activation 4833SIM swap requested without the ownerreview

Activation 4834Document · liveness · face matchedapprove

Honest subscribers and fraud share one stream — split them before the number is issued.

Document recognition

The document is captured at activation — with no manual data entry

The subscriber shows a passport or ID to the phone camera. The platform extracts the fields and checks document integrity: anomalies such as a swapped photo, edited fields or a shot taken from a screen are visible before the next step. The data returns into the operator’s registration scenario — no scans by email, no retyping, no manual review queue.

Support for 433+ document types from 180+ countries lets you build a single connection scenario across different markets.

Session · subscriber documentCaptured

Document typerecognized

Holder dataextracted

Portrait from documentready for match

Document types433+

Countries180+

Manual entrynot needed

Responseto your subscriber flow

Document in sessionData available to the next verification step

Liveness check

The number goes to a live applicant, not to their photo or a deepfake

Passive liveness does not ask anyone to turn their head or follow commands in front of the camera. For a real subscriber it is a short activation step. A photo, a video, a mask or a deepfake cannot replace a present human being.

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

Session · passive livenessLive person

Photo instead of facenot found

Video from a screennot found

Masknot found

Deepfake signsnot found

Liveness confirmed without commandsTested to ISO 30107-3 Level 2

Face match

A genuine document only confirms the person it belongs to

The system compares the applicant’s face with the photo in the document. If a different person is in front of the camera, a genuine passport or ID is not enough. That way the number is tied to the document holder at the very first activation.

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

Session · face matchMatched

Subscriber

Document

Face in frame and portrait from documentone person

Operator similarity thresholdpassed

Document holder confirmedThe comparison threshold is configurable to operator rules

Step-up verification

A risky action is confirmed by the owner’s face — without a new full eKYC

Before a SIM swap, port-out, eSIM issuance or self-care login, the operator’s risk rule triggers Face Captcha. The subscriber shows their face, the system compares it with the identity confirmed at activation and returns the result into the existing flow.

When a step-up is needed, and what to do with the result, stays the operator’s call. An honest subscriber never has to upload a document again. The verdict is produced in 1.4 seconds.

Session · SIM swap / eSIMAllowed

Now

Activation

18:40SIM swap requestcreated

18:40Face Captchamatched

18:40Full KYC againnot needed

18:40Result to risk rules1.4 sec

The action goes to the number’s ownerThe decision on the risky action stays with the operator

For developers

Classic integration

If your team prefers to assemble architecture manually, connect ready SDKs and API.

JS · Webview

Web SDK / Flow Widget

Ready JS camera component for web registration or in-app Webview. Verification runs inside your onboarding; design adapts to your brand.

JavaScriptCustom designWebview

iOS · Android

Mobile SDK

Native verification flow in mobile apps: camera access and biometric micro-packets even on weak connections.

SwiftKotlinOffline-ready

Backend

REST API

Layer results and final verdict arrive in your backend logic: risk rules and decisions stay on your side. X-API-KEY auth.

RESTX-API-KEYServer-side

AI · AGENTS

MCP server for AI agents

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

MCPClaudeAI-agents

sim_activation — REST API

# SIM activation / sim_activation

POST /v1/verification/check/

Host: api.biometric.vision

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

Content-Type: application/json

{ "scenario": "sim_activation", "checks": ["document", "liveness", "face_match", "device"] }

# → 200 OK

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

37 / 570+NIST FRVT

99.9997%match accuracy

ISO 30107-3 L2passive liveness

1.4 secstep-up verdict

Questions and answers

The scenario stays short: data is read from the document automatically and passive liveness needs no commands in front of the camera. The subscriber confirms identity in one flow and the operator receives the data in their system without manual transfer.

500 checks a month — free

Build one path from SIM activation to risky actions

Link document, liveness and face at connection. Add step-up verification wherever the number can be reissued, ported or used without the owner knowing. Start with a test scenario or walk the subscriber journey on a demo.