Biometric
Biometrics for logistics

Behind the wheel is the driver you trusted with the cargo

Verification starts when you onboard a contractor: documents, liveness and face match. Before departure — and when receiving or handing over cargo — the driver confirms identity again. If someone else is behind the wheel or at the ramp, the system won't let them through.

Start freeRequest a demo
Sound familiar?

You verified one person — a different one went on the trip

At onboarding you checked the driver's documents, confirmed the licence was valid and everything looked fine. On trip day someone else got behind the wheel — they were simply given the account. That person never went through your check. They may not hold a valid licence or shouldn't be carrying your load at all.

Usually you find out too late — after an accident, missing cargo or a client claim. Liability lands on your company. A one-off check at registration isn't enough. You need to know the person carrying the cargo is the one you cleared to work.

What you get

From contractor onboarding to cargo release

01

Onboard contractors without offices or in-person meetings

The driver verifies from their smartphone: photograph the document and take a selfie. It doesn't matter which city they're in — no physical presence required.

Licence or passport + liveness + face match with the document
02

Catch substitution before every trip

The check doesn't stop after onboarding. Before departure the driver confirms identity again and the system compares their face to the reference. If someone else is behind the wheel, the check won't pass.

Before departure · on pickup · on handoff
03

Only an authorised person receives the cargo

At release the recipient confirms identity on the spot. That way you know the cargo goes to the person it was intended for. Identity verification complements — not replaces — checks on the legal carrier.

Identity confirmation at release
Contractor network

One verification standard for every city

When contractors work across regions, keeping a consistent manual verification process is practically impossible.

Biometric.Vision runs remote biometric checks on a single scenario: every new driver follows the same procedure from their smartphone, wherever they are.

For developers

Classic integration for developers

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

JS · Webview

Web SDK / Flow Widget

Ready-made JS camera widget for your site or Webview in the driver app. Design adapts to your brand book.

JavaScriptCustom designWebview
iOS · Android

Mobile SDK

Native libraries for the driver app: camera access and biometric micro-packets even on weak 3G.

SwiftKotlinOffline-ready
Backend

REST API

Direct access to onboarding and re-check endpoints to embed verdicts in your TMS and dispatch stack. Authorisation via X-API-KEY.

RESTX-API-KEYServer-side
AI · AGENTS

MCP server for AI agents

AI agents connect to verification directly — no code required. Works with Claude, GPT and any MCP client.

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

Questions & answers

From a smartphone: document and selfie. No office or paperwork required.

500 checks a month free

Always know who's driving

Create an account, get API access and test on your own drivers. 500 checks a month free, no card.

Start freeRequest a demo

Numbers and facts

433+
Document types —Passports and hundreds of other document types worldwide
180+
Countries supported —Global coverage for verification across jurisdictions
40 sec
Onboarding time —Registration and verification in under a minute
99%
Technology accuracy —High-precision AI document recognition and verification