Skip to main content
This guide explains what a typical end-user experiences during an ID Document Check + Liveness Test session, and highlights the UX optimizations that drive high completion rates.

​
Flow Overview

1

Start screen

The user lands on a clean, branded screen that sets expectations (e.g., “You’ll need your ID and your face”). This reduces drop-off by removing uncertainty.
2

Country and document selection

The user selects their country and document type (Passport, ID Card, etc.).
If your workflow is configured for a single document type, this screen is automatically skipped — taking the user straight to capture.
3

ID capture with intelligent retries

The user photographs the front of their document. On-device quality check — Before submitting, the SDK checks for glare, blur, and cutoff edges. If a problem is detected, the user is prompted to retake.Backend validation with guided retry — Once submitted:
  • Pass → proceed to liveness
  • Fail → the user sees specific instructions (e.g., “Document expired”, “MRZ unreadable — retake in stronger light”) rather than a generic error
This self-serve retry loop significantly increases pass-through rates. See the full list of validation outcomes under ID Verification Warnings.
4

Liveness + face match

A selfie liveness check ensures the user is physically present and prevents replay/deepfake attacks. If the user doesn’t respond in time, the process retries once automatically instead of hard-failing.
5

Final outcome

After all checks complete, the user sees one of three results:
ResultDescription
ApprovedAll checks passed. Data is extracted and available via API/webhook.
DeclinedThe system determined the verification cannot be approved.
In ReviewAutomated checks were inconclusive — requires manual review.
By combining smart UX, progressive validation, actionable feedback, and graceful retries, the Didit verification journey keeps good users moving and keeps bad actors out — without manual intervention.