Document Capture and Verification

TrustX provides a number of document verification services that enables users to check the validity of an uploaded document image. Depending on the results, a decision can be made whether the identity verification flow is a success or fails due to one or many checks failing.

This document will describe how to prompt the end-user to capture a document image and perform a variety of verification checks as part of the Process Definition. After all checks are completed, a decision can be made using the 'Simple Decider' activity and results can be viewed from the Backoffice application or TrustX API.

Capture a Document

Document capture can be performed during a Process Instance by including a 'Capture Document Image' activity within a Process Definition.

Document Type

Before a document can be captured, the type of document must be determined. TrustX provides multiple solutions for determining the document type that will be captured.

• Define Document Type - Enables users to directly define the document type to be captured. This will not request input from the end-user.
• Select Document Type - Requests the end-user to choose which document type will be captured from a list of acceptable document types.

The 'Acceptable Document Type' activity can determine that the captured document image matches the required document type.

To implement a document capture, follow the steps below:

1. Add a 'Define Document Type' or 'Select Document Type' activity to the Process Definition. In this example, a 'Define Document Type' activity will be used.
2. Click the activity to open the right-side contextual menu and set the applicable document type within the input parameters. This activity supports the following:

3. The resulting Process Definition should appear as follows:

Capture a Document

The next step involves integrating the 'Capture Document Image' activity to prompt the end-user to capture an image of their document.

1. Create a new gateway that can be used to mark the start of the document capture flow.
2. Add a 'Capture Document Image - Front' activity to the Process Definition. This activity will request the end-user to take a photo of the front-side of their ID document. Connect this activity to the entry gateway using the global connect tool.
3. The Process Definition can be designed to handle a scenario where the captured document is not of the correct document type. Create a new gateway after the 'Capture Document Image' activity and connect them using a sequence flow arrow.
4. Create a new sequence flow arrow using the global connect tool and connect the 'change document type' gateway to the 'document capture entry' gateway.
5. Click the sequence flow arrow to open the context menu. Expand the 'Condition' configuration and create a new Expression: ${changeDocument==true}

When the end-user reaches this step within the TrustWeb app, they will be prompted to take a photo using their camera. An instruction screen will appear detailing how to proceed.

(Optional) Capture a Document Video

Beta

TrustX document capture and verification provides an optional video capture step that prompts the end-user to record a video of their document during the identity verification process that can be used in addition with verification methods to ensure the authenticity of a document.

This can be achieved using the 'Capture Document Image & Video - Front v4' and 'Capture Document Image & Video - Back v4' activities. The steps below will demonstrate a standard implementation.

1. After the Front side Document Capture Entry Gateway defined in the Capture a Document step above, add a 'Capture Document Image & Video - Front v4' activity, replacing the 'Capture Document Image - Front v4' activity.
2. Connect the activity to the entry gateways created in the Capture a Document section.

3. This activity supports the following input parameters:

When the end-user reaches the video capture step during the Process Instance, they will be prompted to record a video of their document.

For more information on this activity, see the Document Activity Parameters page.

Quality Assessment

The 'Document Quality Assessment' activity is used to determine the quality of the captured document image.

1. After the document type gateway created in the step above, add a 'Document Quality Assessment' activity to the Process Definition and use the global connect tool to connect it to the gateway.
2. The activity has a 'Failed document quality' boundary event that is triggered when the document failed to pass the quality threshold. In this example, the boundary event is connected to the start of the document capture gateway using a sequence flow arrow.
3. This activity supports the following input parameters:

Screen Replay Detection

Screen Replay Detection determines whether a document image is a genuine capture or a copy being displayed from a computer monitor or mobile device.

To configure Screen Replay Detection, follow the steps outlined below:

1. Add a 'Screen Replay Detection' activity to the Process Definition and connect the activity to the 'Document Quality Assessment' activity created in the step above.

2. This activity has two boundary events:

   1. Screen replay detected - triggered when an image is detected as a screen replay.
   2. Exceed screen replay detection count - triggered when the end-user has exceeded the set amount of retries.

3. In this example, the 'Screen replay detected' event will be connected to the start of the capture process. The 'Exceed screen replay detection count' will be configured later when the 'Simple Decider' activity is implemented.

4. 'Screen Replay Detection' contains the following configurable input parameters:

Black and White Copy Detection

The Black and White Copy Detection service checks whether the captured document image is genuine or a black and white copy of the original document.

To configure Black and White Copy Detection, follow the steps outlined below:

1. Add a 'Black and White Copy Detection' activity to the Process Definition and connect the activity to the Screen Replay Detection' activity created in the step above.

2. This activity has two boundary events:

   1. Black and white printout detected - triggered when an image is detected as a black and white copy of the original document
   2. Exceed black and white detection count - triggered when the end-user has exceeded the set amount of retries.

3. In this example, the 'Screen replay detected' event will be connected to the start of the capture process. The 'Exceed screen replay detection count' will be configured later when the 'Simple Decider' activity is implemented.

4. 'Black and White Copy Detection' contains the following configurable input parameters:

Color Copy Detection

Color Copy Detection checks whether the captured document image is genuine or a color copy of the original document.

To configure Color Copy Detection, follow the steps outlined below:

1. Add a 'Color Copy Detection' activity to the Process Definition and connect the activity to the 'Black and White Copy Detection' activity created in the step above.

2. This activity has two boundary events:

   1. Color copy detected - triggered when an image is detected as a color copy of the original document
   2. Exceed color copy detection count - triggered when the end-user has exceeded the set amount of retries.

3. In this example, the 'Screen replay detected' event will be connected to the start of the capture process. The 'Exceed screen replay detection count' will be configured later when the 'Simple Decider' activity is implemented.

4. 'Color Copy Detection' contains the following configurable input parameters:

Photo Substitution Detection

Photo Substitution Detection determines whether the face image associated with the captured document image belongs to the original document or whether it has been replaced or altered.

To configure Photo Substitution Detection, follow the steps outlined below:

1. Add a 'Photo Substitution Detection' activity to the Process Definition and connect the activity to the 'Black and White Copy Detection' activity created in the step above.

2. This activity has two boundary events:

   1. Photo substitution detected - triggered when if the face photo associated with the document has been altered.
   2. Exceed photo substitution count - triggered when the end-user has exceeded the set amount of retries.

3. In this example, the 'Screen replay detected' event will be connected to the start of the capture process. The 'Exceed screen replay detection count' will be configured later when the 'Simple Decider' activity is implemented.

4. 'Photo Substitution Detection' contains the following configurable input parameters:

Text Substitution Detection

Beta

TrustX Text Substitution Detection performs a check against a captured document image to determine whether any text on the document has been altered, substituted or obscured from the original document.

To configure Text Substitution Detection, follow the steps outlined below:

1. Add a 'Text Substitution Detection ' activity to the Process Definition and connect the activity to the 'Black and White Copy Detection' activity created in the step above.

2. This activity has two boundary events:

   1. Text substitution detected - triggered when if the face photo associated with the document has been altered.
   2. Exceed text substitution detection count - triggered when the end-user has exceeded the set amount of retries.

3. In this example, the 'text substitution detected' event will be connected to the start of the capture process. The 'Exceed screen replay detection count' will be configured later when the 'Simple Decider' activity is implemented.

4. 'Photo Substitution Detection' contains the following configurable input parameters:

Confirm Document Image

After document verification checks have been performed, a prompt can be sent to the end-user to confirm that they're satisfied with the document capture. To do this, the 'Confirm Document Image - Front' can be used. This activity will display a confirmation screen to the end-user in TrustWeb.

1. Add the 'Confirm Document Image' activity to the Process Designer and connect it to the 'Text Substitution Detection' activity using the global connect tool.
2. The activity supports the following input parameters:

4. After the 'Confirm Document Image' activity, add a new gateway that will be used to capture the confirmation of the document image.
5. If the end-user is not satisfied with the document image, they can request to retake the photo. To handle this flow, connect a sequence flow arrow from the gateway to the beginning of the document capture flow.
6. Click the sequence flow arrow and create an expression under the Condition column: ${_documentConfirmed!=true} .

Document Processing

The next step requires processing the captured document. To accomplish this, the 'Regula Document Processor' activity will be used.

1. After document confirmation, add a 'Regula Document Processor' activity and connect it to the 'Document confirmed' gateway created in the step above by using the global connect tool. The activity consists of the following input parameters.

Making a Decision

The 'Simple Decider' activity can be used to set a final outcome of a Process Instance. This activity is typically found at the end of a Process Definition and after all checks have been performed.

1. Add a 'Simple Decider' activity to the Process Designer and connect the activity to the 'Regula Document Processor'. In this example, an additional gateway is created for switching back to the desktop.
2. The 'Simple Decider' activity is connected to an 'End' gateway to conclude the Process Definition.

3. The activity has the following input parameters:
   1. Decision on Any Failure - Defines the overall outcome should a check failure occur. Possible values are FAIL and PASS. The default value is FAIL.
   2. Derive Decision From - This parameter will set the decision of the overall outcome to the value provided as input. No iterative check will be performed. Accepted values are PASS, FAIL, or REVIEW. The result will be provided as the _decision output parameter. This parameter is empty by default.

Viewing Results

Results of a document capture and verification can be viewed from the Backoffice or the TrustX API.

Viewing Results in the Backoffice

The results of a Process Instance can be viewed from the Backoffice application. From the Backoffice application, follow the steps outlined below.

1. Select Process Instances from the left vertical navigation bar.
2. The Process Instances page provides various search options to find the Process Instance of choice.

3. From the list of search results, select the magnifying glass to view the Process Instance page.

4. Results can be found under the 'Documents' section. A further breakdown of results can be found under the 'Checks' section.

Viewing Results Using TrustX API

Document Check results can be retrieved from the TrustX API. The tenant will require additional permissions to retrieve this data. This section highlights some of the queries and privileges needed to retrieve this information.

The example below returns check information by providing the Process Definition and Process Instance ID.

Permissions: TNT#{tenantid}#UserDataServer:getChecksByKey

Example Request:

GET https://{{tenant}}.{{region}}.trustx.com/api/userdata-server/processDefinitions/{processDefnId}/processInstances/{processInstanceId}/userdata/checks

Content-Type: application/json

X-API-Key: {{apiKey}}

​

{}

Example Response:

{

    "visualIntegrity": {...},

    "documentProcessing": {...},

    "video": {...},

    "docInjectionDetectionFront": {...}

}

Further Reading

• Document Activity Parameters - A collection of all document related activities and their input parameters.
• Document Processor Activity Parameters - A collection of document processing related activities and their input parameters.