Document authentication V1
Validates the authenticity of the fields extracted from an identity document and returns a low, medium, or high risk level.Capabilities
The module returns four capabilities: three integer-based check failure counts and one overall authentication result. The module categorises the individual forensic checks it runs into three severity tiers. For each tier, it counts how many checks failed. These counts explain the severity distribution of failures behind the overall authentication result, which helps you decide whether to reject, escalate to manual review, or accept with conditions.Number of significant checks failed
The number of high-severity authentication checks that failed. Significant checks test the most critical security features of a document, such as template structure, key security elements, and data consistency between the visual zone and machine-readable zone (MRZ). A failure in a significant check is a strong indicator of a forged, counterfeit, or fundamentally altered document.
A value greater than
0 indicates serious authenticity concerns. Even a single significant failure typically warrants rejection or manual forensic review.
Number of moderate checks failed
The number of medium-severity authentication checks that failed. Moderate checks test secondary security features and data consistency elements that contribute to overall document confidence but are less definitive than significant checks. Failures may indicate lower-quality forgeries, minor inconsistencies, or legitimate but unusual document variations.
A small number of moderate failures may occur on legitimate documents, particularly older documents, documents from countries with fewer security features, or documents captured under poor imaging conditions. The count should be interpreted alongside the overall authentication result.
Number of insignificant checks failed
The number of low-severity authentication checks that failed. Insignificant checks test minor features that have limited impact on the overall authenticity determination. Failures in these checks are common on legitimate documents and are unlikely to indicate fraud on their own.
These failures are typically informational. They may be useful for audit purposes or for organisations with very strict acceptance criteria, but they rarely warrant rejection on their own.
Document authentication result
This capability returns the overall outcome of the document’s authenticity checks. It uses the same risk-level model as V2, where the result code reflects the residual risk level after the document has been evaluated. The key concept: a document that passes under strict (high-sensitivity) checks carries low residual risk, while a document that passes under relaxed (low-sensitivity) checks carries higher residual risk. The result code names reflect this residual risk, not the sensitivity setting.Default outcomes
The outcome logic maps directly from the authentication result. Each result code produces a corresponding outcome. Unlike V2, which combines authentication and tamper detection results to determine the outcome, V1 uses only the single authentication result capability.This module does not require its own input payload. It runs off of the document images already captured by the Document Classification module earlier in the journey.
Input payload
The following is a sample payload used to submit data to the Document authentication V1 module for processing.JSON
Sample response
The following is a sample response for a successfully authenticated document.JSON
Document Authentication V2
Validates the authenticity of a submitted identity document by running a series of forensic checks against the document image, determining whether the document is genuine or shows signs of forgery, tampering, or reproduction. Results are returned at configurable sensitivity levels.Capabilities
The module returns two capability categories, both of which use the same set of sensitivity-based result values. Each capability can return one or more result codes.Understanding sensitivity levels
The module uses a sensitivity model that controls how strictly it evaluates documents. This is an important concept for interpreting results correctly, because the code names and their meanings are related:- High sensitivity: This applies the strictest checks. Fewer documents pass, but those that do carry the lowest risk. A document that passes at high sensitivity has cleared the most demanding forensic criteria.
- Medium sensitivity This applies a moderate level of checks. It balances fraud detection coverage with acceptance rates.
- Low sensitivity This applies the most relaxed checks. More documents pass, but those that do carry higher residual risk because fewer forensic criteria were evaluated.
LOW_RISK_PASS because passing strict checks means low residual risk. Also, a document that passes at low sensitivity is labelled HIGH_RISK_PASS because passing relaxed checks leaves higher residual risk.
Document authentication result
Returns the overall outcome of the document’s authenticity checks. It evaluates whether the document matches a known genuine template and whether its structural features, such as layout, fonts, security elements, and data consistency, are consistent with an authentic document of that type.Document tampering result
This capability specifically evaluates whether the document has been altered after issuance. Tampering checks look for signs of post-production modification, such as digitally edited text or photographs, spliced images, pixel-level inconsistencies around data fields, or evidence of photo manipulation software. Tampering detection is different from the authentication check. A document can authenticate as a genuine type (matching a known template) but still fail the tamper check if its content has been modified, for example, a real passport with an altered name or swapped photograph.Default outcomes
The module combines the authentication result and the tampering result to produce an overall outcome. These default outcomes can be used directly in evaluation and routing logic within the journey designer.This module does not require its own input payload. It runs off of the document images already captured by the Document Classification module earlier in the journey.
Input payload
The following is a sample payload used to submit data to the Document Authentication V2 module for processing.JSON
Sample response
The following is a sample response returned by the module.JSON
Related guides and tutorials
The following guides and tutorials use this module or explain how to configure it.How to group document modules
Best practice for grouping documents.