Understand Verification statuses and decisions
This video provides a clear explanation to help you navigate and understand every outcome with ease.
💡 Here’s what you’ll learn:
Verification Statuses explained. Understand what each status means, from "Pending" to "Approved" or "Declined," and how they reflect the progress of a verification.
Types of decisions. Learn the differences between decisions and how they are determined.
How to use this information. Discover how to leverage these insights to improve your verification processes and handle cases more efficiently.
This video will ensure you can interpret and act on every status and decision with confidence.
Watch now and get the clarity you need to master Veriff's verification outcomes!
Below you will find a deeper explanation of Statuses and Reasons behind decisions
Statuses
Session statuses help you understand in which part of the verification process your customers are. Session statuses can be divided into three categories.
Statuses sent via decision webhooks:
Approved
Your customer has received a positive conclusive decision from us. Accessing the session URL again will show the customer that nothing more is to be done.
Declined
Your customer has received a negative conclusive decision from us. Either fraud was detected or there was another severe reason for the person to be declined. Scroll down to learn more about possible reason behind decline.
Accessing the session URL again will show the client that nothing is to be done here. If you decide to give the client another try you need to create a new session.
Resubmitted
Resubmission has been requested. The verification process is not complete. Something was missing in the customer's session and they need to go through the flow again. The same session URL should be used for this purpose.
Expired The session will expire 7 days after having been created unless it gets a conclusive decision before that. The verification status will turn to expired if it has never been accessed by the customer. Accessing the session URL again will show the client that nothing can be done there. A new session should be created for the customer, if they decide to try ag The session URL remains functional for the entire session lifecycle, allowing users to resume verification if the session is still active and valid. Once the session has expired or been archived, a new session must be initiated, accompanied by a new verification link.ain.
Abandoned. Much like expired, abandoned status will be set after 7 days if the process has been started by the customer but has not been finished. Accessing the session URL again will show the customer that nothing can be done. A new session should be created for the customer, if they decide to try again. By understanding these conditions and following the recommendations above, users can better manage their sessions and ensure completion of the verification process. To resolve such sessions, users have two primary options: Each verification link is intended for a single session. Expired or abandoned links cannot be reused, necessitating the creation of a new session and link to proceed.
Resume an Existing Session: If still valid, the original session URL can be used to continue and complete the process.
Create a New Session: After exceeding the 7-day limit, the abandoned session cannot be resumed, necessitating the creation of a new session and sharing an updated session link. Here are specific conditions where a session may be considered "Abandoned": Verification links are designed for single use, ensuring the integrity of each session. If the session remains valid within the lifecycle, the same link can be reused to complete the verification process. However, once a session is marked as abandoned or expired, generating and sharing a fresh link is required.
Initial Data Entry Only: If a user enters only preliminary information (e.g., their name) without capturing document photos or selfies, the session is considered abandoned.
Partial Data Uploads: Even if the user uploads partial data, such as some document photos, the session remains "abandoned" if it is not completed within the designated period.
Inactivity or Expiration: Sessions that are not started or completed within 7 days of creation are also marked as "abandoned."
Statuses sent via event webhooks:
Started - the customer has opened the verification flow for the first time
Submitted - the customer has finished the verification flow by submitting their data and photos
Statuses we will not notify you about:
Created - the session is created and is ready to be accessed via URL
Preprocessed - the session is submitted and it has gone through our automated checks. It is waiting for a decision from our Specialist.
Checks dispatched - the session is being verified
Reasons behind decisions
Conditions for a positive conclusive decision or an approve
We give a positive conclusive decision (status approved, code 9001) when the customer has provided us with:
an upload of photos and/or a video
a valid document with a readable and matching data
a clear/good quality portrait photo
a portrait photo that corresponds to the customer's photo on the document
Reasons for a negative conclusive decision or a decline
We give a negative conclusive decision (status declined, code 9102) when
a physical document is not used
we suspect document tampering
we detect some suspicious behaviour
a customer showing the document does not appear to match the document photo
a velocity/abuse is present
a known fraud is present
We also give a negative conclusive decision (status declined, code "105 - Suspicious behaviour”) when
a user's gone through 10 resubmission attempts. After the 10th attempt, they'll get declined.
Reasons for inconclusive decisions or resubmissions
We give an inconclusive decision (status resubmission_requested, code 9103), when
the video and/or photos are missing
the customer's face is not visible/clear
the full document is not visible
images provided have poor quality
the document is annulled or expired
the document type is not supported
the document is expired
Tip! You could forward the resubmission reasons to your customers as an automatic notification in order to provide a clear overview of the result of their verification and help them to get verified during their next attempt.
Tips to Minimize Session Abandonment:
Set User Expectations. Clearly explain each step in the verification process and stress the importance of completing it in one session.
Communicate Permissions in Advance. Let users know about necessary permissions like camera and microphone access ahead of tim- Manage Link Validity. Inform users about the session lifecycle and encourage them to complete the process promptly to avoid the need for new verification links.e.
Monitor Timeframes. Encourage users to finish within the 7-day window to avoid expiration.