This article provides a reference for Sumsub error codes and universal error codes returned by the API. For each error, you can find the corresponding HTTP status code and a description of the issue.
ImportantHTTP status codes are available in both the response headers and the response body, while
errorCodevalues are returned in the response body.
Mind that not all error responses include an errorCode. In many cases, the response contains only the universal errorCode and an error message describing the issue.
|
Sumsub |
Error name |
Universal |
Description |
|---|---|---|---|
|
Upload errors Errors related to document and file uploads. For more information about document requirements, refer to this article. |
|||
1000 |
|
409 |
Applicant uploaded the duplicate document (image, video). |
1001 |
|
400 |
Applicant exceeded the maximum allowed number of uploaded documents. Adding new is not allowed. |
1002 |
|
400 |
Uploaded file size exceeds the allowed limit (more than 64MB). |
1003 |
|
400 |
Uploaded file is empty and cannot be processed (0 bytes). |
1004 |
|
400 |
Uploaded file is corrupted or cannot be read (for example, PDF file is uploaded as JPEG). |
1005 |
|
400 |
Uploaded file format is not supported (for example, a TIFF image). |
1006 |
|
409 |
Applicant is being checked. Adding new data is not allowed. |
1007 |
|
409 |
Uploaded file does not meet the required size requirements specified in the global settings. |
1008 |
|
409 |
Applicant has been marked as deleted/inactive. No action is allowed to change the status. |
1009 |
|
409 |
Applicant has received a FINAL rejection. Adding new data/files is not allowed. |
1010 |
|
409 |
Applicant attempted to upload a document type outside the configured document set. |
1011 |
|
400 |
Uploaded file is encrypted and cannot be processed. |
|
Errors that occur when attempting to change settings in |
|||
2010 |
|
400 |
WebAuthn request is invalid. |
2011 |
|
400 |
Error occurred while registering a WebAuthn authenticator. |
2012 |
|
400 |
WebAuthn authenticator has already been registered. |
2013 |
|
400 |
WebAuthn authentication failed. |
2014 |
|
400 |
Provided password has been identified as compromised and cannot be used. |
2015 |
|
403 |
Session was invalidated because the IP address changed. |
2017 |
|
403 |
Access is not allowed from the provided country. |
2018 |
|
401 |
Provided password is incorrect. |
2019 |
|
403 |
Requested action requires two-factor authentication. |
2020 |
|
401 |
Session has been invalidated and is no longer valid. |
2021 |
|
401 |
Session has been invalidated due to inactivity. |
2022 |
|
401 |
Session has expired because the maximum session duration was reached. |
2023 |
|
401 |
Session has been invalidated because a security mismatch was detected. |
2024 |
|
401 |
Session has been invalidated because the user logged in from another session. |
|
Flow errors Errors related to applicant status transitions and flow rules. For example, attempting to perform an action that is not valid for the applicant's current state. |
|||
3000 |
|
409 |
Attempt to change the applicant's status against the logic — the applicant is already in the required state. |
3001 |
|
409 |
Attempt to change the applicant's status against the logic — the applicant is already in a final state. |
3002 |
|
409 |
Attempt to change the applicant's status against the logic — the applicant is not in the Requires action state. |
|
API authentication errors Errors related to API access and security validation. |
|||
4000 |
|
401 |
Invalid format of the X-App-Token value. |
4001 |
|
401 |
App token does not exist (for example, test env. token used on production). |
4002 |
|
401 |
Private part of the token (after dot) does not match public part. |
4003 |
|
401 |
Signature encoded value does not match the request content. |
4004 |
|
401 |
X-App-Access-Ts does not match the number of seconds since Unix Epoch in UTC. |
4005 |
|
401 |
Invalid authentication header values were provided. |
4006 |
|
401 |
Not all required authorization headers were provided. |
4007 |
|
401 |
Invalid authentication parameters were provided. |
4008 |
|
400 |
Applicant failed CAPTCHA verification. |
|
API usage errors Errors caused by incorrect API usage on the client side. |
|||
5000 |
|
409 |
Attempt to blacklist the applicant that is already blocked in your Client lists. |
5001 |
|
409 |
Attempt to whitelist the applicant that is already whitelisted. |
|
Rate limits errors Errors caused by exceeding request, usage, or verification limits. |
|||
6000 |
|
429 |
Maximum number of SMS verification attempts has been reached. |
6001 |
|
429 |
SMS verification attempts are being made too frequently. |
6002 |
|
409 |
SMS delivery is not available for the specified region. |
6003 |
|
400 |
Provided phone number is invalid. |
6004 |
|
409 |
SMS cannot be sent because the recipient has unsubscribed from receiving messages. |
6005 |
|
429 |
Maximum number of SMS messages allowed in the Sandbox environment has been reached. |
6006 |
|
429 |
Maximum number of OTP requests has been reached. |
6007 |
|
400 |
Provided email address is invalid. |
6008 |
|
429 |
Maximum number of applicants allowed in the Sandbox environment has been reached. |
6009 |
|
429 |
Daily limit for Video Ident calls in the Sandbox environment has been reached. |
6010 |
|
429 |
Monthly limit for Video identification calls in the Sandbox environment has been reached. |
6011 |
|
429 |
Too many applicant action requests are currently pending. |
|
Sign up errors Errors that may occur during account registration. |
|||
7000 |
|
409 |
Account with the provided details already exists. |
7001 |
|
409 |
Registration with the provided email address is not allowed. |
7002 |
|
409 |
Registration with the provided company name is not allowed. |
7003 |
|
409 |
Provided promo code is invalid. |
7004 |
|
409 |
Client with the provided details already exists. |
7005 |
|
409 |
Registration with the provided email domain is not allowed. |
|
License key validation errors Errors related to license key validation and limitations. |
|||
7500 |
|
400 |
Provided VAT number is invalid. |
7501 |
|
400 |
Provided VAT number could not be verified as valid. |
8000 |
|
402 |
License key usage limit has been reached. |
8001 |
|
401 |
Login is not allowed for this license key. |
8002 |
|
402 |
Requested checks are not allowed for this license key. |
|
Document errors Errors related to document requirements. |
|||
9000 |
|
409 |
Required document masking has not been applied. |
|
Processing data errors Errors related to processing and validating submitted data. |
|||
9001 |
|
409 |
Provided GPS location could not be verified. |
|
e-KYC errors Errors that may occur during the Non-Doc Verification (e-KYC) process. |
|||
9100 |
|
409 |
Provided data is invalid for the e-KYC verification. |
9101 |
|
409 |
Usage of the selected e-KYC channel is not allowed. |
9102 |
|
409 |
Selected e-KYC channel returned an unexpected error. |
9103 |
|
409 |
Selected e-KYC channel is currently experiencing technical difficulties. |
9104 |
|
409 |
Selected e-KYC channel could not find matching data. |
9105 |
|
409 |
Maximum number of e-KYC verification attempts has been exceeded. |
9106 |
|
409 |
Payment for the e-KYC verification could not be completed. |
9107 |
|
409 |
Violations were found during the e-KYC verification. |
|
e-SIGN errors Errors that may occur during the QES Verification (e-SIGN) process. |
|||
9400 |
|
409 |
No documents were provided for e-SIGN verification. |
9401 |
|
409 |
No input data was provided for e-SIGN verification. |
9402 |
|
409 |
Applicant must pass KYC verification before using e-SIGN. |
9403 |
|
409 |
Selected e-SIGN channel is currently experiencing technical difficulties. |
|
KYB errors Errors that may occur during Business Verification (KYB) process. |
|||
9501 |
|
409 |
No KYB data source is enabled for the requested verification. |
9502 |
|
400 |
Provided data is invalid for the KYB verification. |
9504 |
|
409 |
Selected registry is currently experiencing technical difficulties. |
9505 |
|
400 |
Number of beneficiaries exceeds the allowed limit. |
9506 |
|
400 |
Number of matching results exceeds the allowed limit. |
|
Wallet verification errors Errors related to wallet ownership verification. |
|||
9600 |
|
400 |
Wallet signature verification failed. |
|
Common WebSDK errors Common errors returned by the WebSDK. |
|||
9700 |
|
400 |
Provided contact data is invalid. |
|
100XX - reserved for common errors |
|||
|
104XX - reserved for Sumsub Id errors |
|||
|
Reusable KYC errors Errors related to Reusable KYC eligibility, partner configuration, and data sharing. |
|||
10501 |
|
400 |
Applicant is not eligible for reusable KYC with the selected partner. |
10502 |
|
400 |
Provided partner ID is invalid. |
10503 |
|
400 |
Provided share token is invalid. |
10504 |
|
400 |
Provided share token cannot be used for reusable KYC. |
10505 |
|
400 |
Reusable KYC is disabled. |
10506 |
|
400 |
Applicant is not eligible for reusable KYC reuse. |
10507 |
|
400 |
Applicant has not passed verification for further reuse. |
10508 |
|
400 |
Applicant is not active for further reuse. |
10509 |
|
400 |
Applicant verification type is not supported for reusable KYC. |
10510 |
|
400 |
Applicant does not have a required identity document or selfie. |
10511 |
|
400 |
Applicant does not have a required Liveness check. |
10512 |
|
400 |
Required documents do not match reusable KYC requirements. |
10513 |
|
400 |
Provided document type is not compatible with reusable KYC. |
10514 |
|
400 |
Identity document is too old for reusable KYC. |
10515 |
|
400 |
Proof of address document is too old for reusable KYC. |
10516 |
|
400 |
Applicant age does not meet reusable KYC requirements. |
10517 |
|
400 |
Capture settings are not compatible with reusable KYC requirements. |
10518 |
|
400 |
Applicant email address does not match reusable KYC data. |
10519 |
|
400 |
Applicant phone number does not match reusable KYC data. |
10520 |
|
400 |
Applicant copying for reusable KYC is disabled. |
10521 |
|
400 |
Sumsub ID account is inactive. |
10522 |
|
400 |
Applicant data is not suitable for reusable KYC. |
10523 |
|
400 |
Document subtype is not compatible with reusable KYC. |
10524 |
|
400 |
Provided identity document is inactive. |
10525 |
|
400 |
Questionnaire data is not suitable for reusable KYC. |
10526 |
|
400 |
Share token environment does not match the current environment. |
|
Sumsub ID Connect errors Errors that may occur when using Sumsub ID Connect. |
|||
10600 |
|
401 |
Profile associated with the Sumsub ID Connect token could not be found. This could be because the profile was deleted. |
10601 |
|
401 |
Profile associated with the Sumsub ID Connect token has been blocked and cannot be used. |
10602 |
|
401 |
Profile associated with the Sumsub ID Connect token has revoked the connection between their Sumsub ID and your app. |
10603 |
|
401 |
Sumsub ID Connect token is malformed or expired. |
10604 |
|
403 |
Sumsub ID Connect is not enabled for your client key. |