Skip to main content

Document verification

Document verification confirms that a government-issued identity document is authentic, readable, and acceptable for your flow, and extracts the fields you need for onboarding and compliance.

What it does​

  1. Guides the user to capture or upload the document
  2. Runs authenticity and quality checks (security features, tampering, copy / screen attacks, score thresholds)
  3. Applies your country and document-type filters
  4. Enforces minimum age when configured
  5. Produces a step result (PASSED, FAILED, or review statuses) with optional structured reasons

Where it sits in a flow​

Document verification is usually the first identity step. Pair it with liveness so you know a live person matches the document portrait. Other steps (PoA, phone, forms) can follow depending on risk appetite.

Document verification → Liveness → (optional PoA / form / phone) → Result + webhook

Outcomes you should handle​

OutcomeWhat to do
PASSEDContinue the flow or accept the identity evidence
FAILED + reasons[]Map codes to UX (retry, different document, support), statuses and codes
Manual reviewKeep the user pending until review completes, manual review

Configure it​

Operational settings (thresholds, filters, labels) live in the flow builder:

→ Document verification guide · Create a flow