---
title: "Verification session decisions | Veriff.com"
slug: "verification-session-decisions"
description: "Understand session decisions in Veriff, including approval, decline, and resubmission limits. Learn how to fetch and manage session outcomes effectively."
updated: 2025-02-25T11:01:35Z
published: 2025-02-25T11:01:35Z
---
> ## Documentation Index
> Fetch the complete documentation index at: https://devdocs.veriff.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Verification session decisions
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)*](/v1/docs/verification-session-decision-codes-table)*for overview of possible reasons why the end-user was not approved*
*→ See*[*Granular reason codes (table)*](/v1/docs/granular-reason-codes)*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](/v1/docs/decision-webhook) payload
- Query the [GET sessions/{sessionId}/decision](https://veriff-dev-documentation.document360.io/apidocs/v1sessionsiddecision-1)[↗] 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](https://help.veriff.com/en/articles/3492920-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](https://veriff-dev-documentation.document360.io/apidocs/v1sessions)[↗] endpoint.
---
## Verification session lifecycle (diagram)
This is returned after the end-user's data has been analysed and the system has reached a conclusion about the end-user's verification session.
Can be `approved`, `declined`, `resubmission_requested`, `expired` or `abandoned`.
Only if previously agreed with Veriff, you may also be receiving `review`.
A session during which the end-user is verified. It starts when a session is created, it can contain several attempts (i.e. steps of uploading media, sending additional data etc.) and it ends when a conclusive decision (“approved”, “declined”, “expired”/”abandoned”) is granted.
Each verification session receives an unique ID, aka the **session ID**, which can be added to the API URL when making API requests.
Veriff customer back-office, a dashboard where you can see your end-users' verification data.
Depending on your setup, you may be required to access the environment via station.veriff.com or hub.veriff.com. Always **check your sign-up email** and make sure that you **log in via correct address**.
Integration which is **automatically created for every customer who onboards** with Veriff. It is **used for development** purposes, and verification sessions that are created **will not count towards paid usage**.
The `Webhook decision URL` is automatically created.
**Veriff will not provide statuses** for sessions created in test integration, you need to set them **manually in the Veriff Customer Portal**.
## Related
- [Integrations](/how-to-create-an-integration.md)
- [Decision webhook](/decision-webhook.md)
- [Verification session decision codes (table)](/verification-session-decision-codes-table.md)
- [Granular reason codes (table)](/granular-reason-codes.md)