I want to catch cases where the MRZ is missing or unreadable before the verification workflow continues.

This feature helps detect when a document’s MRZ (Machine Readable Zone) is missing or cannot be read before moving forward in the verification workflow. By stopping or rerouting these cases early, it reduces failed verifications and prevents wasted user effort.

This feature is designed to identify documents where the MRZ is not present or is unreadable before the verification workflow proceeds. Its purpose is to prevent downstream verification steps from running when the core MRZ data cannot be reliably extracted. In practice, the workflow evaluates MRZ readability at an early stage and flags cases that do not meet the minimum quality needed to continue. When a case is flagged, the workflow can be interrupted so the user can correct the issue rather than encountering a failure later. This improves completion rates by reducing avoidable rejections and repeated attempts. It also improves operational efficiency by reducing the number of cases that enter manual review or fail after additional processing. Common causes include partial captures, blur, glare, low resolution, occlusion, or documents that do not contain an MRZ in the expected location. The feature is especially useful in mobile capture scenarios, where image quality can vary significantly. Overall, it ensures that verification continues only when the MRZ can be confidently read, improving both user experience and verification reliability.