Skip to main content
The Document Authentication module validates the authenticity of a submitted identity document by running a series of forensic checks against the document image. It determines whether the document is genuine or shows signs of forgery, tampering, or reproduction. The module returns results at configurable sensitivity levels, allowing you to balance fraud detection strictness against user friction.

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.
The result codes reflect the risk level after passing, not the sensitivity setting itself. A document that passes at high sensitivity is labelled 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 for a successfully authenticated document.
JSON

Document authentication V1

Capabilities

Number of significant checks failed

A count of the number of significant checks that failed authentication

Number of moderate checks failed

A count of the number of moderate checks that failed authentication.

Number of insignificant checks failed

A count of the number of insignificant checks that failed authentication.

Document authentication result

Returns the overall outcome of the document’s authenticity checks - whether the document matches a known genuine template and whether its structural features (layout, fonts, security elements, data consistency) are consistent with an authentic document of that type.

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 returned by the module.
JSON