Biometric
eKYC for taxi and ride-hailing

The passenger gets the driver you verified

At registration: a driving licence, liveness and face matching. Before a shift: a short selfie, so another person's account never goes on the road.

500 checks a month free — no card

Verification · shift_checkApproved
97%
Liveness confirmed
Driving licence read
Face matches the reference
Allowed on the road · shift approved
A familiar pain

One account — another person behind the wheel

Drivers are onboarded online. Forged licences, rented profiles and deepfakes come with them. You need control both at registration and at every shift start.

Forged licenceRejected
Rented accountRejected
Deepfake to cameraRejected
Registered driverApproved
Three outcomes

From registration to going on the road

01

Register without an office queue

The driver uses a smartphone: licence → liveness → face match. The flow is configured for your risk profile.

  • Driving licence is the default document
  • Reference saved · ready for shifts
Verification · shift_checkApproved
97%
Liveness confirmed
Driving licence read
Face matches the reference
Allowed on the road · shift approved
02

Forgeries and rentals do not pass

Liveness rejects photos, video, masks and deepfakes. Another person's face will not match the licence or the reference.

  • Liveness against photos, video, masks and deepfakes
  • Face match against the licence and shift reference
Face match · rejectedRejected
41%
Forged licence
Deepfake to camera
Face does not match
Shift start denied
03

A check before every shift

A short comparison with the reference. The verdict is available through the API and dashboard, and every session keeps an event log.

  • One integration for onboarding and shifts
  • Verdict through the API and the Sessions dashboard
Verification · shift_checkApproved
97%
Liveness confirmed
Driving licence read
Face matches the reference
Allowed on the road · shift approved
Liveness check

A live person — at registration and on shift

The system checks that a live person, not a photo, video, mask or deepfake, is in front of the camera. You set the acceptance threshold.

PRO · onboarding
DISTANCE · balance
FAST · shift / weak devices
Confirmation during service

Before a shift — a selfie against the reference

A face reference is saved at registration. Before a shift, the driver completes a short liveness and reference match. No match means no shift.

Verification · shift_checkApproved
97%
Liveness confirmed
Driving licence read
Face matches the reference
Allowed on the road · shift approved
Integration

No-code builder — or API

Build a verification flow in Flow Builder or connect REST API and webhooks to your server.

Flow Builder · no code

Licence → liveness → Face2Face → Shift re-auth

scenario: 'shift_check'
checks: ['liveness', 'document', 'face_match']
status: 'approved'
Trust

Taxi platforms choose Biometric.Vision

ISO/IEC 27001 · No. 760281Algorithms among the world's strongest in NISTMore than 8 years in Kazakhstan and CIS
Questions

Questions and answers

How does registration differ from a before-shift check?

Registration includes a licence, liveness and face match with the document. Before a shift, a short liveness check and match with the saved reference are enough.

How do you stop account rental?

Before going on the road, the system compares a new selfie to the reference and checks liveness. Another person's face or a deepfake will not match.

Which documents does a driver need?

The primary document is a driving licence. A vehicle registration document can be added to your flow if needed.

How quickly can we connect?

Build the scenario in the visual no-code builder. REST API and webhooks are available for a deep integration.

We can review your flow in 20–30 minutes

See how to keep someone else's account off the road

A short demo for your driver flow: the checks you need at registration and before every shift.