The decision of the verification session can be approved, declined, resubmission_requested, expired, abandoned, and review.
In case the session was declined or resubmission_requested, we send:
Reason code in
verification.reasonCodestringReason description in
verification.reasonstring
This info is sent in the webhooks, and are part of some GET API calls payloads.
Session decision: declined
If the verification.status returned the declined reason, see the table below for possible reason codes and descriptions.
If you do not see the reason code here, see the Granular reason codes (table).
Code in | Description in |
|---|---|
102 | Suspected document tampering |
103 | Person showing the document does not appear to match document photo |
105 | Suspicious behaviour |
106 | Known fraud |
108 | Velocity/abuse duplicated end-user |
109 | Velocity/abuse duplicated device |
110 | Velocity/abuse duplicated ID |
112 | Restricted IP location |
113 | Suspicious behaviour - Identity Farming |
Session decision: resubmission_requested
This table contains values for verification.reasonCode in case the verfication.status returned resubmission_requested.
If you do not see the reason code here, see the Granular reason codes (table).
Code in | Description in |
|---|---|
201 | Video and/or photos missing |
204 | Poor image quality |
205 | Document damaged |
206 | Document type not supported |
207 | Document expired |
Cap on the number of resubmissions
One 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.