Title
Page icon
Create new category
Edit page index title
Edit category
Edit link
Checks and reports
Session retrieval requires a session ID, this is generated from the create a session endpoint. Below is a basic example of what retrieving a session looks like:
The following are present in every session result:
Parameter | Value | Description |
|---|---|---|
Session ID | uuid | Unique identifier for a identity verification session. |
Client session token | uuid | Unique identifier, Used to authenticate the session. |
Client session token ttl | integer | Returns the time left in seconds until the the session expires. |
User tracking ID | uuid | The user ID you set in your backend. |
State | ONGOING COMPLETED EXPIRED | The current state of the session. It provides the overall state of the session. You can search through session results prior to the session being completed, but some checks may not have been processed yet. |
Resources | Object | A container of all ID documents and liveness captures for this session. A new resource is created on each attempt at a document or liveness submission. |
Checks | Object | A container of all checks performed for this session. |
Results of checks
Basic examples of how to get the results of each check can be found below.
A recommendation reason will only be provided if the value isn't 'APPROVE'. The recommended approach for processing a session is to ensure that each check value is APPROVE.
We will use the check container to iterate through all of the checks that have been completed as part of the session. The checks object will only contain information once the user has completed all events in the session.
Document Authenticity
The document authenticity check can be fully automated or have a manual check. This can alter the sub checks that have been performed.
Liveness
The liveness response is available immediately. The user may have multiple attempts of liveness and It's possible for some of these attempts to be rejected.
Face Match
The face match check can be fully automated or have a manual check. This can alter the sub checks that have been performed.
AML
There are two different types of AML checks that can be configured, In addition to the normal check report, AML watchlist checks will also return a WatchlistSummary object.
Watchlist Check:
Advanced Watchlist Check:
AML raw
You have the ability to extract the raw results from the comply advantage API, as well as a link to a comply advantage page displaying the hits (if any) by using the raw_results media ID.
Field | Description |
|---|---|
provider | The third party provider used for our AML check. |
search_types | The watchlist types that are searched against in the session. |
search_id | Unique id related to the AML search conducted. |
search_ref | Unique reference id related to the AML search conducted. |
url | A public URL that will display the results of the search that can be reviewed. |
raw_output | The JSON payload returned from our AML provider, It is base64 encode so will need to be decoded to access the JSON. |
Reports of checks
Below are examples to get the report recommendation and breakdown for each session check.
Object | Response | Description |
|---|---|---|
Report recommendation | N/A | A recommendation value, and recovery suggestion. |
Report recommendation value | e.g. REJECT | Returns only the recommendation value. |
Report recommendation reason | e.g. PHOTO_TOO_BLURRY | Returns only the reason of the value. If approved the value will be null. |
Report recommendation recovery suggestion | N/A | Returns only the recovery suggestion. If approved the value will be null. |
Report breakdown | N/A | A breakdown report on the session that has been completed including, sub-checks, results and details. |
Report breakdown sub check | e.g. data_in_correct_position | The completed sub-check. |
Report breakdown result | e.g PASS | The result of the sub-check completed. |
Report breakdown details | N/A | Extra information on the check if relevant. |
Report breakdown process | EXPERT_REVIEW, AUTOMATED | Indicates whether the sub-check was completed through automation or by a human reviewer. |
Got a question? Contact us here.