The overall result indicator on the Document Reader SDK might display red if the document does not pass security checks. Below are the most common reasons for such occurrences:
Primary Causes
- Document Movement: During scanning, the document must remain stationary. Even minor shifts can cause errors during MRZ reading, document type detection, visual zone recognition, and authenticity checks. Disabling the Glare Compensation option may partially mitigate movement effects, but this can degrade image quality and analysis results.
- External Light Sources: Scanning with the reader lid open or without a lid allows external light to distort images, especially in UV mode. This causes overexposure on critical document areas. Enabling the Smart UV option (default: off) reduces light interference but increases processing time and may cause issues when scanning copies.
- Holograms and Glossy Lamination: Shiny document elements disrupt visual zone recognition and document type detection. The default Glare Compensation option partially mitigates this effect.
- Invalid Document: The document may be:
- Not yet valid (e.g., a visa with a future start date).
- Expired (the end date has passed).
- Document Sample: The document is flagged as a sample if:
- The document number contains only zeros.
- The country code is invalid (e.g., "UTO").
- The owner’s name is on a stop-list (e.g., "Test", "Specimen", "Sample").
- Unknown or New Document Type: The document is unrecognized because:
- Its design is not in the SDK’s template database.
- It is a counterfeit with unexpected features.
- Series Changes in Documents: New document series may reuse older templates with minor changes (e.g., altered visual zone placement, lamination type). This leads to misidentification, as the system classifies it as part of the previous series.
- Failed Passive Authentication (PA) of the RFID Chip: Occurs when scanning samples where the certificate chain does not link to a trusted root. This is often intentional to block test documents.
Important
Some causes (e.g., new document series) require updating the SDK’s template database. Users are advised to monitor new SDK releases and install updates for improved recognition compatibility.
Comments
Article is closed for comments.