Verify & Enroll User
Validate uniqueness and authenticate users with ID Check
Once an ID Check session is complete, use the Verisoul API to verify or authenticate the user.
Verify
First, verify the authenticity of the session and document by calling the /verify-id endpoint. The endpoint provides three values to help interpret the risk of the user and their document:
- Decision -> an overall decision; Real, Suspicious, or Fake
- Risk Score -> a 0-1 number score representing the overall risk of the user
- Risk Flags -> an array of string flags that summarize the risky aspects of the user’s session
See here for the full set of risk flags
For more nuanced decisioning you can also interpret the other risk signals captured in the session.
Device and Network Signals
Device and network Signals are information about the user’s exact device and connecting network.
| Name | Description |
|---|---|
| device_risk | Device likely emulator, VM |
| proxy | ID Check on a proxy IP |
| vpn | ID Check on a VPN IP |
| datacenter | ID Check on a datacenter |
| tor | ID Check on a TOR IP |
| recent_fraud_ip | ID Check on an IP reported as fraud |
| device_network_mismatch | Device user agent is inconsistent with connecting network fingerprint |
Document Signals
Document Signals refers to the authenticity of the identity document.
| Name | Description |
|---|---|
| id_age | Age of user calculated by the date of birth on ID |
| id_face_match_score | Match level of face on ID and face scanned. 1.0 is highest match |
| id_barcode_status | Status of the barcode on the identity document |
| id_face_status | Status of the face on the identity document |
| id_text_status | Status of the text information on the identity document |
| is_id_digital_spoof | Whether the identity document has been digitally spoofed |
| is_full_id_captured | Whether ID Check was able to capture the full document |
| id_validity | Whether identity document presented is authentic or fake |
Referring Session Signals
Referring Session Signals will only be present if you initialized the session with a referring_session_id parameter.
| Name | Description |
|---|---|
| impossible_travel | Referring session geolocation is far from ID Check geolocation relative to timespan |
| ip_mismatch | Referring session IP different than ID Check session IP |
| user_agent_mismatch | Referring session user agent different than ID Check session user agent |
Multi Accounting
ID Check will calculate any potential matches based on five identifiers captured during all sessions.
| Match Type | Description |
|---|---|
| browser | ID Check session was completed on the same browser session |
| ip_address | ID Check session shares the same ip address |
| face | ID Check session shares the same face |
| document_name | ID Check session shares the same name and date of birth |
| document_number | ID Check session shares the same document type and number |
Enroll
Use Enroll to tie the session to your account identifier. You must do this to detect multi-accounting. By enrolling an account, Verisoul will know to match future sessions against enrolled accounts to help you prevent repeat devices, repeat faces, and repeat IDs from signing up.
API Reference
For complete details on all available endpoints and parameters, see the ID Check API Reference.