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:
  1. Decision -> an overall decision; Real, Suspicious, or Fake
  2. Risk Score -> a 0-1 number score representing the overall risk of the user
  3. 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.
NameDescription
device_riskDevice likely emulator, VM
proxyID Check on a proxy IP
vpnID Check on a VPN IP
datacenterID Check on a datacenter
torID Check on a TOR IP
recent_fraud_ipID Check on an IP reported as fraud
device_network_mismatchDevice user agent is inconsistent with connecting network fingerprint

​
Document Signals

Document Signals refers to the authenticity of the identity document.
NameDescription
id_ageAge of user calculated by the date of birth on ID
id_face_match_scoreMatch level of face on ID and face scanned. 1.0 is highest match
id_barcode_statusStatus of the barcode on the identity document
id_face_statusStatus of the face on the identity document
id_text_statusStatus of the text information on the identity document
is_id_digital_spoofWhether the identity document has been digitally spoofed
is_full_id_capturedWhether ID Check was able to capture the full document
id_validityWhether 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.
NameDescription
impossible_travelReferring session geolocation is far from ID Check geolocation relative to timespan
ip_mismatchReferring session IP different than ID Check session IP
user_agent_mismatchReferring 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 TypeDescription
browserID Check session was completed on the same browser session
ip_addressID Check session shares the same ip address
faceID Check session shares the same face
document_nameID Check session shares the same name and date of birth
document_numberID 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.