Face Match 1:1

Powered by cutting-edge AI, computer vision, and biometric technology, our solution ensures fast, accurate, and secure identity verification at scale. Designed to combat fraud, simplify compliance, and enhance user experience, Didit provides a robust and trustworthy platform that meets the highest industry standards.

​

Retries & actionable feedback

In a Didit session, a face match that fails for a fixable capture reason (the selfie is too dark, blurry, off-center, or the similarity is borderline) does not immediately decline. The user is asked to retry with guidance, up to a configurable number of attempts — the same model used for Liveness.

• Attempt budget — face_match_max_attempts controls the total number of face-match submissions per session. Default 3 (one initial attempt plus two retries), configurable per workflow node (range 1–3).
• Retry feedback — while attempts remain, a retryable failure keeps the user on the step and returns feedback_codes (the Web and Mobile SDKs surface these as coaching messages automatically):
  {
    "detail": "Make sure your face matches your document photo, improve lighting and try again.",
    "error": "LOW_FACE_MATCH_SIMILARITY",
    "feedback_codes": ["LOW_FACE_MATCH_SIMILARITY"],
    "attempts_used": 1,
    "max_attempts": 3
  }
  
• Exhaustion — once the budget is exhausted the computed status is applied (Declined or In Review).

​

How It Works

---

​

Document Requirements

For optimal verification success, documents must meet these standards:

​

General Requirements

• Government-issued and valid within its configured validity period
• Physically intact (no damage, scratches, or stains obscuring details)
• All critical information (full name, date of birth, MRZ, etc.) clearly legible
• Consistent data across all submitted documents

​

Image Requirements

• Original, real-time photo (no screenshots, scans, or digital copies)
• Supported formats: JPG, JPEG, PNG, PDF
• Maximum file size: 5MB
• Full-color image with all document corners visible
• Free from glare, shadows, digital editing, or manipulation
• Physical documents required (digital IDs supported only in select regions where officially recognized)

​

Additional Settings by Country & Document Type

Configure fine-grained rules per country and document type directly from the console. These controls let you tailor acceptance criteria and transcription preferences to your compliance needs.

• Expiration mode: Choose how to handle documents with past expiration dates.
  • Reject expired: If the document’s expiration date is earlier than today, mark it as expired and reject.
  • Allow expired: Do not flag or block documents with a past expiration date.
• Preferred character format: Select how extracted names and fields should be normalized.
  • Prefer Latin characters (A–Z): Example: “Mohammed”
  • Prefer original script (non‑Latin): Example: “محمد”
• Regional support & subtypes: Enable documents by region and specify acceptable subtypes when a document type contains many variations.
  • Example: For United States driver’s licenses, select the exact subtypes you accept (e.g., Arizona Commercial Driver License, Indiana Operator License (REAL ID), New York Enhanced Driver License, etc.).
  • Use the “Accepted subtypes” control to quickly include/exclude many variants (e.g., “128 selected”).

Tip: These settings apply per country and document type, so you can be strict in some markets while more permissive in others.