Biometric
Biometrics for insurance

Payout — to the same person accepted at the policy

Document, liveness and face match accept the real policyholder at onboarding. Before payout — re-verification against the same reference. A fake face or deepfake never reaches the money. An honest customer issues a policy from a smartphone — without head turns or blinking prompts.

Session · insurance_onboardingPassed
Customer in widgetDocument → selfie → verdict in Session
User step · document
Document typeIdentityCard / ID
OCRextracted
In Sessiondocument data
Liveness check
Check list(No risks found)
StatusPassed
Face match
Resultmatched
Check list(No risks found)
Overview · decision
No risk flag foundSession passed automatic fraud checks
Device & browserChrome @ Windows
StatusPassed
Issue policyOperator sees verdict in Session
Sound familiar?

Policies and payouts are online — and so are the schemes

You launched remote issuance and online payouts. Into the same stream come not just honest customers: stolen documents, stand-ins, deepfakes on camera, claims filed for someone else.

Strict manual review kills conversion and buries the team in disputes. Weak control at entry and payout — you pay out on someone else’s identity. Digital growth and identity-fraud protection pull in opposite directions — both affecting loss ratios.

Sessions · policies & payoutsRisk / reject
Attempt · deepfake
Claim · deepfakeSynthetic face on camera
TabLiveness check
StatusFailed
Attempt · drop
Claim · stand-inSomeone else’s document · payout for another
Risk in SessionOperator sees rejection before payout
Genuine customer
PolicyholderDocument + liveness + policy reference
No risk flag foundAutomatic fraud checks passed
Decision in Session
Reject the schemeDo not pay out
Approve the customerPolicy / payout · Passed
How verification works

One pipeline: from policy to payout verdict

A short flow for issuance and for re-verification before payout. No promises of 'whole policy in N seconds'.

01

Document

The customer photographs a passport or ID — data is extracted automatically.

Session · documentExtracted
Document typepassport / ID
OCRextracted
In Sessiondocument fields
02

Liveness & face

Selfie: a live person and a match with the document photo. A fake face or deepfake does not pass.

Session · liveness + facePassed
Check list(No risks found)
StatusPassed
Resultmatched
03

Device

An extra risk layer — session and device: emulators, root, VPN, proxy, TOR, model and OS. Not instead of the face — alongside it.

Session · deviceChecked
Device & browserin Overview
VPN / emulator / rootchecked
Before payoutsignal in Session
04

Verdict

Approve, reject or send to manual review — into your flow via API. At payout the same pipeline matches the claimant to the policy reference.

Session · verdictapprove
DecisionApproved
Policy / payoutallowed
ApprovedCan issue policy / process payout
Before payout

Before payout — the same person as on the policy

When a claim is filed, the system re-checks liveness and matches the face against the reference collected at issuance. A stand-in, someone else’s document or a deepfake does not reach the money silently.

An honest customer is confirmed quickly. Identity substitution is cut off before payout — no field visits, no manual check of every claim.

Session · payoutPassed
Claimant
Selfie at payoutMatch against policy reference
Reference match
Resultmatched
Livenessconfirmed
Substitution
Wrong faceDoes not match the policy
RejectedDo not pay out
Decision before payout
Same personPolicy reference · payout allowed
After first verification

Verified once — then payout, portal and renewal by face

The customer already passed verification at policy issuance. For next steps — a short face confirmation, not a full document form again: claim filing, portal sign-in, renewal.

Less friction for your own customers. Rejection for an impostor under someone else’s account. One reference works across the policyholder’s lifecycle.

Session · repeat sign-inPassed
User
Selfie at payoutWithout full KYC again
Reference match
Resultmatched
Checks(No risks found)
Decision
Payoutsign-in by face
Portalsign-in by face
Renewalsign-in by face
ConfirmedPolicy reference · without full KYC
For developers

Classic integration for developers

If your team prefers to build the architecture manually — use our ready-made SDKs and API.

JS · Webview

Web SDK / Flow Widget

A ready-made JS camera component (widget) for a website or Webview inside an app / portal. Design is customizable to your brand.

JavaScriptCustom designWebview
iOS · Android

Mobile SDK

Native libraries for a mobile app: camera access and biometric micro-packet transfer even on weak 3G.

SwiftKotlinOffline-ready
Backend

REST API

Direct access to policy issuance and pre-payout match endpoints. Authorization via X-API-KEY.

RESTX-API-KEYServer-side
AI · Agents

MCP server for AI agents

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

MCPClaudeAI-agents
insurance_onboarding — REST API
# Policy issuance / insurance_onboarding
POST /v1/verification/check/
Host: api.biometric.vision
X-API-KEY: sk_live_••••••••••••••
Content-Type: application/json
{ "scenario": "insurance_onboarding", "checks": ["document", "liveness", "face_match"] }
# → 200 OK
{ "decision": "approve", "live": true, "face_match": true }
Trust

One pipeline at policy and payout — no empty promises

Face match and passive liveness are linked to the policyholder’s reference: accepted at issuance — matched before payout. No regional titles, no numbers that cannot be honestly defended.

Need details on accuracy, certifications and document coverage — we’ll break them down on a demo for your flow. Below on the page — the platform facts block.

Questions & answers

Because policy issuance and payout are different moments. Between them the claimant can be substituted. Re-matching against the policy reference closes that gap.

Emulators, root, VPN, proxy, TOR, device model and OS. It is a support layer alongside the face, not a biometrics replacement.

Not necessarily. Sanctions/PEP screening can be added to the same flow if your product requires it (life, investment, international). It is not the focus of this page.

Channel partner onboarding can also be covered by identity/KYB verification. This page focuses on the policyholder at issuance and payout; channel — briefly, on request at a demo.

Storage architecture depends on the project and contract. At the demo we’ll show options and boundaries — without blanket promises of 'always this way'.

Dashboard: 500 checks a month free, no card. Or request a demo on your policy and payout flow.
500 checks a month free

Test it on your own policy and payout flow

Connect the API, run policy issuance and a payout claim on your scenarios. No card — 500 checks a month free.

Numbers and facts

433+
Document typesSupport for passports and hundreds of other document types worldwide
180+
Supported countriesGlobal coverage for verification across jurisdictions
40 sec
Onboarding timeUser registration and verification in under a minute
99%
Technology accuracyHigh-precision AI-based recognition and document verification