Verification result

Once a verification process is completed, the verification result will include a recommendation on how to proceed. In identity verification flows which include document verification, the result also includes information about the ID document and user. The status of the session and the result can be obtained via API calls.

Note

Mosaic retains verification data for a standard duration of 90 days. During this time, data can be retrieved via API or viewed in the Admin Portal. After 90 days, verification data is permanently deleted. To adjust the retention period, reach out to your Transmit Security representative.

Document info

Document information is extracted from the ID document that was used in the verification process. If the verification process was completed successfully, this data is considered verified. This data includes the document type, and additional data that depends on the document type (see supported types). For example, it may include:

issuing country or region
when it was issued
user's name and birthday
user's unique identifier (e.g., passport number)
document identifier (e.g., passport serial number)

See all document data.

Personal info

The verification result includes information about the real-world identity of the person in this session. It's based on data extracted from the ID document, or determined as part of the selfie check. If the verification process was completed successfully, this data is considered verified. For example, it may include:

user's name
user's gender
user's age

See all personal data.

Recommendations

When a process is completed, the result provides a recommendation on how to proceed. The recommendation reflects the level of assurance provided by all the checks performed in the session. For a hosted solution, this includes real-time risk detections based on the context, such as device, network, behavior, etc. (see Fraud detection). The following recommendations may be returned:

Recommendation	Description
`ALLOW`	User has adequately proven their real-world identity and there's a low risk of fraud.
`CHALLENGE`	Additional checks are required (e.g., manual review) since at least one check didn't succeed.
`DENY`	Risk was deemed to high to proceed at all (e.g., clearly forged document or a selfie mismatch).

Note

If the verification process didn't successfully verify the user's identity (recommendation is either CHALLENGE or DENY), the result will include failed checks with reasons such as age_mismatch or document_damaged.

Verification status

The status indicates the progress of the verification process. If your desktop page hands off the process to a mobile device (for example, using a QR code), the desktop page can use the status to display the progress of the mobile flow. In an API-based flow, the status indicates if the verification processing has completed and a result is ready.

Status	When returned
`pending`	Before the first user interaction in a hosted experience
`capturing`	Required images (document and selfie) are being added and validated
`processing`	Verification is being processed after receiving all required images (document and selfie)
`complete`	Verification was completed (even if the checks didn't pass)
`recapture`	Process must be repeated (e.g., some data couldn't be extracted due to poor image quality). Only when verifying identity with documents
`error`	An unexpected technical error occurred (e.g., communication error)

When reviewing verification sessions in the Admin Portal, you'll see statuses in a more aggregated way: Incomplete, Pass, Challenge, Deny, or Error.