This is an introductory guide and overview for the Document report.
If you're looking for API documentation:
The Document report is composed of data integrity, visual authenticity and police record checks. It checks the internal and external consistency of the identity document provided by the applicant to identify potential discrepancies.
In addition, any data extracted from the document through OCR is returned in the properties attribute.
The Document report combines software and an expert team to maximise fraud detection. The majority of documents will be processed instantly. However, when document analysis falls back to expert review, the report status will be delivered asynchronously via webhook notifications. (Read about webhooks in our API documentation).
Expert review is required when we encounter images that use sophisticated counterfeiting techniques, or the image is of poor quality (blurred, low resolution, obscured, cropped, or held at an unreadable angle).
The Document report uniquely uses the
sub_result field in the API response
to give a more detailed description than the
|Clear||If all underlying verifications pass.|
|Rejected||If the report has returned information where the check cannot be processed further (for example, poor image quality or unsupported document).|
|Suspected||The analysed document is suspected to be fraudulent.|
|Caution||If any other underlying verifications fail, but they don't necessarily point to a fraudulent document (for example, the name provided by the applicant doesn't match the one on the document).|
Breakdowns are made up of sub-breakdowns. A breakdown will have a consider
result when at least one of its sub-breakdowns contains a
You can read how individual breakdowns contribute to the overall
value in the Document report in our API
The following diagram shows how breakdowns and sub-breakdowns are mapped to particular sub-results. It also shows how the mappings can be changed, where possible, depending on your configuration:
The following diagram shows the reasons which can lead to specific sub-breakdowns and therefore sub-results other than 'Clear':
You may find our guide on "suggested client actions" for the Document report useful.
Almost all use cases will require the 'primary' Document report, but yours may require one of the following BETA Document reports:
- Document with Address Information
- Document with Driving Licence Information
Contact your account manager for more information about the features in these BETA reports.