Once a verification process is completed, the verification result will include information about the ID document and user, and a recommendation on how to proceed. The status of the verification session and the result can be obtained via API.
Verification Data Retention Period: Transmit’s identity verification API retains verification data for a standard duration of 90 days. This encompasses the facility to retrieve verification specifics via the API or to review them using our administrative portal. The information cannot be accessed or restored once the retention period expires and verification data is deleted. If customers desire to adjust the retention period, they can initiate the process by reaching out to our support team and specifying their preferred duration for data retention.
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.
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.
When a verification process is completed, the verification result provides a recommendation on how to proceed. The recommendation reflects the level of assurance provided by all the verification 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:
||User has adequately proven their real-world identity and there's a low risk of fraud|
||Additional checks are required (e.g., manual review) since at least one check didn't succeed. See note below|
||Risk was deemed to high to proceed at all (e.g., clearly forged document or malicious network)|
By default, only the
DENYvalues are returned since we review verifications manually whenever additional review is required. However, if you'd like to perform your own manual review in these cases, talk to your Transmit representative about enabling the
If the verification process didn't successfully verify the user's identity (recommendation is either
DENY), the result includes a human readable explanation of why (as the
The status of the verification session 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.
||Before the first user interaction in a hosted experience|
||Required images (document and selfie) are being added and validated|
||Verification is being processed after receiving all required images (document and selfie)|
||Verification was completed (even if the checks didn't pass)|
||Process must be repeated (e.g., some data couldn't be extracted due to poor image quality)|
||An unexpected technical error occurred (e.g., communication error)|