Document Verification
The solution verifies the authenticity and liveness of the document using various checks and extracts data using optical character recognition (OCR). The extracted data contains text strings and a trusted image of the user’s face. This image is used for the Liveness Check by default.
- Document authenticity
- Document liveness
- Data extraction
Document Checks
Below is a list of the possible checks that may be performed during verification.
Data Checks
| Check | Description | Configurable |
|---|---|---|
| MatchCheck | Checks if the fields are in the correct format based on our document knowledge. | Yes |
| LogicCheck | Checks whether the values make sense, for example is the date on the document a possible date. Includes general document logic, like check digits or document field rules. | No |
| FieldFormatCheck | Checks whether each field’s value has the shape its issuer prescribes. | No |
| BarcodeAuthenticity | Checks if the barcode on the document is accurate and authentic. | Yes |
| SuspiciousDataCheck | Checks for sample and specimen text in the data fields and suspicious number of sequences. | No |
| DataIntegrityCheck | Checks if the document has all the data fields that it should contain. | No |
| MRZCheck | Checks the MRZ format and its consistency with the data in the other fields. | No |
Document Liveness Checks
| Check | Description | Configurable |
|---|---|---|
| ScreenCheck | Determines if the document is presented on a screen (phone, tablet, desktop). | Yes |
| PhotocopyCheck | Checks if the image of the ID is a black & white photocopy or a colored print out. | Yes |
Visual/Fraud Checks
| Check | Description | Configurable |
|---|---|---|
| PhotoForgeryCheck | Checks whether the profile photo on the document has been tampered with. | Yes |
| SecurityFeatures | Analyzes security features like holograms to determine whether the document is legitimate. | Yes |
| GenerativeAICheck | It checks whether the document has been generated by AI. | Yes |
Document Validity Checks
| Check | Description | Configurable |
|---|---|---|
| VersionCheck | Checks whether this type of document is acceptable in its jurisdiction today. | No |
| ExpiredCheck | Determines whether this particular document is expired. | No |
Image Quality Checks
Image-related assessment sits outside standard verification checks listed above.
| Check | Description |
|---|---|
| Clarity | The combined output of the heuristics and models that decide whether the captured images are good enough to verify. |
| HandPresence* | Checks whether a hand is holding or occluding the document. |
| Cropped | It’s not possible to perform all of our checks without full context, so it checks whether the document is not too close to the edges. |
*HandPresence doesn’t impact the overall liveness verdict.
Please note that not all checks apply to all document types: for example, barcode checks only apply to documents containing barcodes.
Document Checks Configuration
The sensitivity (or strictness) of the selected checks can be adjusted to suit a specific process. The aim is always to strike a balance between high conversion and fraud detection.
We recommend sticking with the default settings and only adjusting the sensitivity if necessary based on data gathered during the operation.
The following attributes can be either disabled or set the level on 10 point scale:
| Check | Configuration |
|---|---|
| MatchCheck | DataMatchMatchLevel |
| BarcodeAuthenticity | BarcodeAnomalyMatchLevel |
| ScreenCheck | ScreenMatchLevel |
| PhotocopyCheck | PhotocopyMatchLevel |
| PhotoForgeryCheck | PhotoForgeryMatchLevel |
| SecurityFeatures | StaticSecurityFeaturesMatchLevel |
| GenerativeAICheck | GenerativeAiMatchLevel |
A few other parameters related to image quality can be adjusted (blur, glare, lighting, sharpness, DPI and tilt). However, these changes are usually unnecessary.
Document Verification process
Verification process requires two sequential steps.
- Capture document images on the device
- Complete the document verification and get the result
Document Capture
This is a process in which the user scans documents using a mobile application. The number of documents to be scanned depends on the configuration. For some documents, such as passports, only one side needs to be scanned, whereas for others, such as ID cards, both sides need to be scanned.
For document scanning, we recommend using the provided Document Verification SDK, which ensures the best possible capture conditions, offers a great user experience (UX) and provides feedback codes available immediately after the scan, enabling the mobile application to react accordingly and help achieve a higher conversion rate in the event of errors relating to the conditions.
Document image requirements
- Supported media types: PNG, JPEG
- Resolution: FullHD - 4K
The Document Capture SDK provides the required images.
Document Verification Result
The verification status is either ‘SUCCESS’ or ‘FAILURE’.
We also provide a score on a scale from 0 to 10, reflecting the lowest level of certainty among the passing Visual/Fraud checks. However, this is more statistical information because there are multiple fraud checks, and even if one of them has a lower score, the others that pass can cause the whole document to pass.
The evaluation logic is based on different weights, whereby some checks are given greater importance (e.g. photocopy detection), while others are given less importance.
As mentioned in the section ‘Document Checks Configuration’, the sensitivity of the checks can be adjusted.
The verification result also contains the following data:
- information about performed checks
- extracted user and document data in text format
- extracted user’s face that is, by default, used as a trusted image for liveness check
- cropped image showing the front and back of the document