Session decision is sent once the verification process is complete and there is a decision about the genuineness of the session.
The session decision can be approved, declined ,resubmission_requested, expired, abandoned or review
This info is sent in the webhooks, and are part of some GET API calls payloads.
For non-approved sessions, Veriff shares the reasons why the end-user was declined or asked to resubmit.
→ See Verification session decision codes (table) for overview of possible reasons why the end-user was not approved
→ See Granular reason codes (table) for expanded list of possible reasons why the end-user was not approved
Fetch decisions
There are several options to fetch the decision(s) of a verification session:
Manually: the Verifications page in the Veriff Customer Portal
Check the decision webhook payload
Query the GET sessions/{sessionId}/decision[↗] endpoint
Trigger decision manually for testing
You can trigger decisions for test integration sessions. Log in to Veriff Customer Portal to see the Forcing the status and data of the verification session when testing[↗] article in Veriff Knowledge Base.
Cap on the number of resubmissions
One end-user can resubmit their data up to 9 times. This means that the 10th attempt is automatically declined, and code 539 - Resubmission limit exceeded is sent. If you wish to allow the end-user to retry verification, you need to create a new session for them using the POST /sessions[↗] endpoint.
Verification session lifecycle (diagram)
