signzy

API Marketplace

downArrow
Logo
Responsive
Decorative line

Quality Thresholds (Document Image)

Overview

Quality thresholds define the minimum capture standards an ID or PoA image must meet before automated verification proceeds. Typical criteria include sharpness (no motion blur), brightness/contrast, glare limits, edge completeness, resolution (e.g., ≥300–400 DPI equivalent), and unobstructed security features/MRZ. Enforcing thresholds reduces false negatives/positives in OCR/ICR, face match, and document forensics, lowering manual review and fraud risk.
Modern SDKs perform on-device quality checks with real-time prompts (reposition, remove glare, increase light) before upload. Compliance teams document these thresholds to meet auditability, ensure consistent onboarding outcomes, and protect against acceptance of tampered or unreadable IDs. Thresholds should vary by document type and channel (mobile vs. web) and be tuned using empirical error rates and reviewer feedback.

FAQ

Why do quality thresholds matter?
Poor images degrade OCR, chip/MRZ reads, and face match, spiking errors and manual reviews. Strong thresholds stabilize performance.
What should we check?
Focus, exposure, glare, framing, resolution, and artifact detection. Validate MRZ edges and security features are visible.
How are thresholds chosen?
Start from vendor baselines and tune using FAR/FRR, OCR accuracy, and case outcomes. Revisit as cameras and models improve.
What if users can’t meet them?
Provide guidance (live prompts), fallback capture modes, or route to assisted/video KYC under a controlled exception policy.