CAIRLDocs
Guides

Identity Verification

Understand the supported evidence flow, result states, and disclosure boundary.

Identity Verification

CAIRL Identity Verification evaluates supported evidence and returns a server-authored result. This guide explains the current public flow and its boundaries. It does not establish production availability, provider qualification, or GA readiness.

Before you begin

Have the following ready:

  • A supported US-issued driver’s license, state ID, passport, or passport card
  • A device with camera access
  • Stable lighting and neutral background

The flow records consent before collecting verification evidence.

Capture the document

Capture the required side or sides when prompted. Keep the text legible and the document edges visible. Passports use the photo-page capture path. Passport cards require front and back captures.

Complete selfie and liveness checks

Follow the on-screen camera instructions. The selfie, liveness result, and face comparison contribute evidence to the server-authored decision; no single captured image establishes a successful result by itself.

Review the extracted details

Review the extracted details before submission. The fields are read-only. If extraction is wrong, recapture the document instead of editing the values.

Understand the result

The durable, point-in-time result is one of:

  • approved — the required gates completed successfully
  • review_pending — the session needs authorized review before a final result
  • rejected — the session did not meet the required gates
  • incomplete — the flow ended without a terminal approval or rejection

Only approved can produce a successful hosted result. The result does not remain current indefinitely: method, document, environment, exposure, freshness, and review conditions affect what it can support. When the app offers another attempt or a recovery path, follow that instruction rather than treating a capture or upload as approval.

What an approved result can support

A compatible integration can receive only the consented, scope-authorized claims allowed for that interaction. Public claim responses do not include raw document images or biometric material. Identity Verification does not by itself establish compliance, universal document coverage, uniqueness assurance, production availability, or GA status.

On this page