How it works?
Verify the authenticity of end user’s ID documents to prevent fraud. Shufti Pro offers a robust and secure solution for ID-based end user verification, designed to establish a strong defense against potential fraudulent activities. Protect clients against fraud, forgery, data tampering, and unauthorized photo replacements while also maintaining high end user conversion rates.
The document verification process includes the following steps:
- Document Upload: End user captures/uploads an image of their ID document.
- Authenticity Check: Shufti Pro verifies the document’s images for authenticity, image integrity, and data validity.
- Verification Results: The outcomes of the verification process are recorded and stored securely in the Shufti Pro’s back office.
ID Document Checks
Shufti Pro's ID document verification includes but is not limited to the following checks:
- The document must be valid and not expired.
- All details on the document must be clear and legible.
- Essential information such as Name, Date of Birth, and ID Number must be present.
- The end user's photograph must be visible on the document.
- The document must be original and unaltered in any form.
Document Verification Settings
Types of proof
Clients can choose what type of verification proofs they want to collect from the end user for verification:
There are two types of proof to select from
- Image only: This option permits the collection of only image-based proof, focusing solely on photographic evidence.
- Video only: Selecting this enables the collection of video evidence, which is essential for verifying live presence or real-time actions.
- Both: By choosing this option, users can provide a comprehensive set of proofs, encompassing both image and video evidence, for a more robust verification process.
Document Types
The client has the flexibility to tailor the range of document types permitted for the verification process, enabling a customised approach to suit specific verification needs. By default, only the ID card is allowed for verification. Checkout supported documents for verification here.
Data Extraction & Verification
Enabling this feature utilizes advanced OCR (Optical Character Recognition) technology, which enables the system to automatically extract and verify all the required data points from the proofs submitted by end users.
The following data points/parameters are verified in Document service:
Parameters | Description |
---|---|
name | This key object contains name information extracted from the document. |
name.first_name | This key contains the first name of the end-user extracted from the document proof. |
name.middle_name | This key contains the end user’s middle name written on the document. |
name.last_name | This key contains the end user’s last name written on the document. |
dob | This key contains the end user’s date of birth written on the document. |
age | This key contains the age of the end user for age verification. |
issue_date | This key contains the issue date of the document proof. |
expiry_date | This key contains the expiry date of the document proof. |
document_number | Contains the document number extracted from the document proof provided by the end-user. |
selected_type | This key contains the type of document proof selected by the end-user. |
supported_types | This key contains all types of supported document proofs. |
gender | This key contains the gender of the end-user listed on the document proof. |
face_match_confidence | This key contains a confidence score based on how accurately the end user’s face matches with their photo on the document proof. The value of this key will be between 0 to 100. Examples: 30, 40, 50, 60, 70 |
full_address | This key contains the end-user's full address as listed on the document. |
Document Authenticity Checks
Upgrade your document authenticity checks to meet your unique business needs by enabling the acceptance of a wider variety of document types that are typically not allowed in standard procedures. By default, none of the documents mentioned in the following image are allowed.
Verification Instructions
{
"document":{
"proof":"",
"supported_types":["id_card","driving_license","passport"],
"verification_instructions" : {
"allow_paper_based" : "1",
"allow_photocopy" : "1",
"allow_colorcopy" : "1",
"allow_black_and_white": "1",
"allow_laminated" : "1",
"allow_screenshot" : "1",
"allow_cropped" : "1",
"allow_scanned" : "1",
"allow_e_document" : "1",
"allow_handwritten_document" : "1"
}
}
}
{
"document_two": {
"proof":"",
"supported_types":["id_card","driving_license","passport"],
"verification_instructions" : {
"allow_paper_based" : "1",
"allow_photocopy" : "1",
"allow_colorcopy" : "1",
"allow_black_and_white": "1",
"allow_laminated" : "1",
"allow_screenshot" : "1",
"allow_cropped" : "1",
"allow_scanned" : "1",
"allow_e_document" : "1",
"allow_handwritten_document" : "1"
}
}
}
These parameters can be used with Document, Document Two.
Parameters | Description |
---|---|
allow_paper_based | Required: No Type: string Value Accepted: 0, 1 Default Value: 1 If this string is assigned value “1” then Shufti Pro will accept paper-backed documents for verification. |
allow_photocopy | Required: No Type: string Value Accepted: 0, 1 Default Value: 0 If this string is assigned value “1” then Shufti Pro will accept photocopied documents for verification. |
allow_colorcopy | Required: No Type: string Value Accepted: 0, 1 Default Value: 1 If this string is assigned value “1” then Shufti Pro will accept color copied documents for verification. Note: If allow_photocopy = "1" then this instruction will be ignored. |
allow_black_and_white | Required: No Type: string Value Accepted: 0, 1 Default Value: 0 If this string is assigned value “1” then Shufti Pro will accept black and white documents for verification. Note: If allow_photocopy = "1" then this instruction will be ignored. |
allow_laminated | Required: No Type: string Value Accepted: 0, 1 Default Value: 1 If this string is assigned value “1” then Shufti Pro will accept laminated documents for verification. |
allow_screenshot | Required: No Type: string Value Accepted: 0, 1 Default Value: 0 If this string is assigned value “1” then Shufti Pro will accept screenshot documents for verification. |
allow_cropped | Required: No Type: string Value Accepted: 0, 1 Default Value: 1 If this string is assigned value “1” then Shufti Pro will accept cropped documents for verification. |
allow_scanned | Required: No Type: string Value Accepted: 0, 1 Default Value: 1 If this string is assigned value “1” then Shufti Pro will accept scanned documents for verification. |
allow_e_document | Required: No Type: string Value Accepted: 0, 1 Default Value: 1 If this string is assigned value “1” then Shufti Pro will accept E-Documents for verification. |
allow_handwritten_document | Required: No Type: string Value Accepted: 0, 1 Default Value: 0 If this string is assigned value “1” then Shufti Pro will accept handwritten documents for verification. |
Shufti Pro has enabled the following parameters [Paper-based, Laminated, Scanned, Color copy, Cropped, and E-document] by default for all clients on boarded from September 11, 2023 onwards.
{
"verification_mode": "video_only",
"allow_online": "1",
"allow_offline": "0"
}
To make the originality checks more strict, the recommended practice would be to enable a live capture option with video mode enabled which would allow you to take a live video in real time. This configuration will help to detect fraudulent documents in real-time.
Document Two Service
Document Two Service offers a seamless way to authenticate end users' personal details using multiple documents. For example, when compliance procedures require collecting two documents for verification, this service enables the collection of an ID document along with a passport to facilitate verification.
For instance, if you have already verified the date of birth (DOB) and name of the end user from their ID card, you can utilize the Document Two Service to cross-verify these same details on their credit card or passport. This ensures thorough and rigorous checks for added security and confidence in the verification process.
The supported documents, onsite and offsite parameters, requests, responses, and decline reasons remain consistent for both the Document and Document Two services.