How to fetch a session token for ID Check verification
For a user to go through ID Check, you must first fetch a valid session token. This token establishes the authenticity throughout the verification process.
Each session token is short-lived and should be generated immediately before starting the verification process.
To get a session ID, your application’s server must make an API request to the GET /liveness/session endpoint.
For security, best practice is to fetch the session token from a protected server, never on the client.
When using ID Check alongside Verisoul’s platform, you can optionally pass a referring_session_id
parameter in your session request.
This parameter should be the session ID from the user’s current interaction with Verisoul’s platform, before they begin ID Check. By providing this context, Verisoul can make more informed risk assessments during the verification process.
Passing a referring session ID provides several benefits:
For more details on the API parameters, see the session endpoint. To learn about the additional risk signals available when using a referring session ID, refer to the referring session signals.
Once you have obtained a session token, you can proceed to navigate the user to ID Check to complete the verification process.