Government ID + liveness + face match

Capture the ID.
Prove the person.

Make it easy to capture a government ID, prove the person is live, and match that person to the portrait on the document.

Capture the IDProve livenessMatch face to ID
A person completing a mobile liveness check matched to a government identity document
LIVE SIGNAL99.2%confidence
Face matchedID portrait · live frame

One verification request can orchestrate

Government IDLivenessFace matchSSNOFACPhoneEmailAddressAdverse mediaGovernment IDLivenessFace matchSSNOFAC

01 / Orchestrate

Ask for the proof you need.
Nothing you don’t.

Configure each verification request around the risk of the moment. Mojo Verify guides the person, runs the required checks, and returns one coherent result.

Verification request · vrf-A91K

New customer onboarding

DeliveryEmail + SMSExpires7 daysModeIdentity first
92confidence

Verification completed

Low risk. KYC level 2.

  • Government ID verified
  • Live face matched
  • Sanctions screen cleared
  • Phone ownership confirmed
01

Configurable by risk

Turn SSN, government ID, liveness, phone, email, address, OFAC, adverse media, signature, and custom data on per request or by group default.

02

One decision surface

See completed checks, confidence, risk level, trust level, and KYC level without stitching together a stack of unrelated results.

03

Events, not polling

Signed, PII-free completion and failure webhooks tell your system when to move. Fetch details server-to-server only when needed.

A mobile phone automatically capturing an aligned identity document

02 / Identity Capture

Make a better capture before you make a decision.

Real-time guidance checks document position, fill, brightness, sharpness, and stability before auto-capture. Desktop users move to mobile with a QR handoff instead of fighting a laptop camera.

  • Extract OCR, PDF417 barcode, and passport MRZ data
  • Cross-check front and back names, dates, and document numbers
  • Score authenticity, security features, completeness, and image quality
  • Decide pass, manual review, or fail with explicit reasons
Explore Identity Capture

03 / Liveness

The face in front of the camera. The person on the ID.

A guided check establishes that a real person is present, measures liveness confidence, and can compare the live face against a reference document or known identity.

≈5 secguided check2 modesKYC or standalone1 resultlive + matched
Explore Liveness
Presence detectedLive
ID portraitLive frameMatch

04 / Verified Signing

DocuSign,
done right.

A signature says someone agreed. Mojo Verify establishes who that someone is first. Capture the signer’s government ID, prove they are live, match them to the ID, then allow the document to be signed.

  • Before verified identity and liveness can gate access to signing
  • During viewed, liveness, signing, and signature events are recorded
  • After encrypted signed PDF, integrity hash, and controlled sharing
Explore Verified Signing
IDENTITY-BOUND AGREEMENTAlex MorganSigned
IDENTITY VERIFIEDLive face matched
  1. Government ID verified
  2. Liveness passed
  3. Face matched to ID
  4. Signature captured
  5. Signed PDF sealed

05 / Experience

One link. A complete path to verified.

People know what to do next. Your system always knows what happened.

01

Invite

Email, SMS, both, or your own delivery.

02

Capture

Identity document and optional liveness.

03

Check

Run the required identity and risk signals.

04

Decide

Confidence, risk, KYC level, and receipt.

05

Notify

Signed webhook with no PII in transit.

06 / Portable KYC

Verify once.
Bring trust forward.

Individuals can carry their verification level to participating partners. Businesses receive the KYC tier and completed-check status—not raw ID images, SSNs, or biometric media.

07 / Developer experience

From request to webhook with a small, explicit contract.

Create the checks you need, send the person the returned link, and let signed terminal events drive the next action.

Read the developer docs
create-verification.http
POST /api/verify/requests/create
Authorization: apikey mvs-••••••••

{
  "first_name": "Alex",
  "last_name": "Morgan",
  "require_gov_id": true,
  "require_liveness": true,
  "require_ofac": true,
  "notification_method": "both"
}
verification.completedsigned · no PII

Trust starts with knowing who is there

Make identity
part of the product.

Tell us where trust breaks in your flow. We’ll help you configure the right proof, user experience, and integration path.