Verification sessions
Statuses, declines, retries, sessions stuck in review, and how to read a result.
9 articles
Reading a result
- What each session status meansA verification session moves through statuses like Not Started, In Progress, In Review, Approved and Declined - here's what each one means, what to do about it, and why even a decided session can change again.
- How to read a verification resultA session result is a status plus a result per check plus a list of warnings - the warnings are the part that tells you what actually happened.
- Why a verification was declinedA session is declined when one or more checks fail - here's how to find the specific reason and decide whether to decline, resubmit, or approve manually.
When something goes wrong
- Sessions stuck in review, and how to reduce themIn Review means the automated checks finished but flagged something a person has to settle - it never resolves by itself. Here's how to clear the queue and lower the rate.
- Letting someone try a verification againTwo ways to give a user a second attempt - request a resubmission of just the failed steps, or start a brand new session. Which one depends on the session's current status.
- When a session never finishesAbandoned, Expired and stuck In Progress sessions all mean the person never completed the flow - here's how to tell which, and the usual causes worth fixing.
- Duplicate accounts and face searchLiveness automatically compares each face against everyone you have already verified and against your blocklist - here's what the duplicate flags mean and how to stop flagging legitimate returning users.
- Fixing a name or field that was read wrongOCR misread a surname, swapped the address for the name, or left a field as "unknown". Support can't edit it for you, but you have three ways to fix it - the user data review step, the update-data API, and a resubmission of the ID step.