Table of contents
Overview
Use this method to change a verification level and/or reset specific verification steps.
This endpoint is useful when your verification requirements change after an applicant has already started the process. For example, if you initially required only an ID document and a selfie, but now need to collect proof of address, you can use this method to adjust the flow accordingly.
Depending on your use case, you can do the following:
- Change a verification level.
- Change a verification level and reset one or several verification steps in the new level.
- Reset a specific verification step of the level.
This method supports both individual and company applicants. Refer to the request examples below for implementation details.
Attention
Make sure to check the applicant status before applying the method. You will not be able to use it if
reviewStatusof the applicant ispending,queuedoronHold.
Note
If you are using our SDKs, you can initialize it with suitable
levelNameonaccessTokenand SDK will change the level automatically.
Request examples
Below, you can see the request examples for different usage scenarios where the method can be applied.
Change verification level
To change a verification level for a specific applicant, submit the applicant identifier (applicantId) along with the name of a new level (name) you want to assign to the applicant as shown in the examples below.
curl -X POST \
'https://api.sumsub.com/resources/applicants/5f80e6b7155a6336271e4677/moveToLevel?name=kyc-with-poa' \
-H 'Content-Type: application/json' \
curl -X POST \
'https://api.sumsub.com/resources/applicants/5f80e6b7155a6336271e4677/moveToLevel?name=basic-kyb-level' \
-H 'Content-Type: application/json' \
In the response, pay attention to the following updated fields:
requiredIdDocs— configuration of steps for the applicant to complete verification.levelName— the name of the new verification level that you have assigned for the applicant.
Change level and reset steps
You can also change a verification level and reset one or several verification steps in this new level. To do this, submit the applicant identifier (applicantId) along with the name of a new level (name) and the docSets object with all idDocSetType attributes that have the value(s) representing the step(s) to reset as shown in the examples below.
Notes
- For individual applicants, you can add the
“resetOnlyIfUnsuitable”: trueparameter to theidDocSetTypeto enable flexible step reset. This parameter is only applicable to the following steps:IDENTITY,IDENTITY2,IDENTITY3,IDENTITY4,PROOF_OF_RESIDENCE,PROOF_OF_RESIDENCE2,SELFIE,SELFIE2,QUESTIONNAIRE.- For company applicants, you may include the
companyDocsGroupDefinitionsobject to reset only specific sub-steps.
curl -X POST \
'https://api.sumsub.com/resources/applicants/5f80e6b7155a6336271e4677/moveToLevel?name=kyc-new-level' \
-H 'Content-Type: application/json' \
-d '{
"docSets": [
{
"idDocSetType": "IDENTITY",
"resetOnlyIfUnsuitable": true // Enable flexible reset
},
{
"idDocSetType": "PROOF_OF_RESIDENCE" // Enable reset
}
]
}'
curl -X POST \
'https://api.sumsub.com/resources/applicants/5f80e6b7155a6336271e4677/moveToLevel?name=kyb-new-level' \
-H 'Content-Type: application/json' \
-d '{
"docSets": [
{
"idDocSetType": "COMPANY_DATA"
},
{
"idDocSetType": "COMPANY_DOCUMENTS",
"companyDocsGroupDefinitions": [
"legalPresence",
"companyDetails"
]
}
]
}'
Reset verification steps
To reset only a verification step or a few steps, submit the applicant identifier (applicantId) along with the current level name (name) and the docSets object with all idDocSetType attributes that have the value(s) representing the step(s) to reset as shown in the examples below.
This method differs from another dedicated endpoint in that it allows resetting multiple verification steps simultaneously. See the list of available steps for reset below.
Notes
- For individual applicants, you can add the
“resetOnlyIfUnsuitable”: trueparameter to theidDocSetTypeto enable flexible step reset. This parameter is only applicable to the following steps:IDENTITY,IDENTITY2,IDENTITY3,IDENTITY4,PROOF_OF_RESIDENCE,PROOF_OF_RESIDENCE2,SELFIE,SELFIE2,QUESTIONNAIRE.- For company applicants, you may include the
companyDocsGroupDefinitionsobject to reset only specific sub-steps.
curl -X POST \
'https://api.sumsub.com/resources/applicants/5f80e6b7155a6336271e4677/moveToLevel?name=kyc-new-level' \
-H 'Content-Type: application/json' \
-d '{
"docSets": [
{
"idDocSetType": "IDENTITY",
"resetOnlyIfUnsuitable": true // Enable flexible reset
},
{
"idDocSetType": "PROOF_OF_RESIDENCE" // Enable reset
}
]
}'
curl -X POST \
'https://api.sumsub.com/resources/applicants/5f80e6b7155a6336271e4677/moveToLevel?name=kyb-level-name' \
-H 'Content-Type: application/json' \
-d '{
"docSets": [
{
"idDocSetType": "COMPANY_DATA"
},
{
"idDocSetType": "COMPANY_DOCUMENTS",
"companyDocsGroupDefinitions": [
"legalPresence",
"companyDetails"
]
}
]
}'
Available steps to reset
The following table details the verification steps available for reset.
| Step | Description |
|---|---|
COMPANY_DATA | Only dedicated for company applicants (KYB 2.0). It represents the Company required step for verification. The step configuration depends on what is set in the associated verification level. |
COMPANY_DOCUMENTS | Only dedicated for company applicants (KYB 2.0). It represents the Company required step for verification. Depending on the step configuration in the associated verification level, it can have one or more document groups for verification. |
APPLICANT_DATA | Type of verification where applicants need to provide personal data in the fields pre-configured when adding the Applicant data step to the verification level. For example, you could select the field types from the predefined list and request such data as the first name, last name, phone number, date of birth, tax residence country, and so on, or add custom fields to request additional information. |
IDENTITY | ID verification where applicants must submit a photo of identity document to be verified. This type is added to the verification level as the Identity document step. When adding this step, you can request to submit an ID card, passport, driver’s license, and residence permit as an identity document either all or some of them at one step, or configure additional steps (IDENTITY2, IDENTITY3, IDENTITY4) for each document. ⚠️ Mind that if you have selected all the available document types in one step, you will not be able to add another IDENTITY step to the level. |
IDENTITY2 | Same as IDENTITY. Used in case you decide to add a separate required step to the verification level for each document or some of them. |
IDENTITY3 | Same as IDENTITY. Used in case you decide to add a separate required step to the verification level for each document or some of them. |
IDENTITY4 | Same as IDENTITY. Used in case you decide to add a separate required step to the verification level for each document or some of them. |
SELFIE | Type of verification where applicants need to complete any of the following Selfie options:
|
SELFIE2 | Same as SELFIE. Used in case you need to add another Selfie option to the verification level. |
PROOF_OF_RESIDENCE | Address verification where applicants are required to provide proof of residency. At this step, the option of using geolocation is available. If you need an applicant to provide one more document for residence confirmation, add the 2nd proof of address step to the verification level. |
PROOF_OF_RESIDENCE2 | Similar to PROOF_OF_RESIDENCE. Used in case you need to add another Proof of address step to the verification level.Mind that the option of using geolocation for PoA is unavailable at this step. |
QUESTIONNAIRE | Type of verification where applicants are required to fill in the pre-configured questionnaire. Note that you cannot add this step to the verification level if no questionnaire is created in your system. |
PHONE_VERIFICATION | Type of verification where the applicant’s phone number is checked to verify whether it is blocklisted or not, and how much risk the specified phone number poses. |
EMAIL_VERIFICATION | Type of verification where the applicant's email address is checked to verify its credibility, whether it is blocklisted or not, and how much risk the specified email address poses. |
E_KYC | Non-doc type of verification where applicants are verified through government databases and official bank verification systems without documents. For more information, see Non-Doc Verification. |
Note
The
COMPANY_BENEFICIARIESstep cannot be reset. To remove a beneficiary applicant from the company's control and ownership structure, use the following method.
Response explained
The response is a JSON object representing the applicant profile, enriched with structured data.
You can see the response structure, possible content with descriptions, and examples of response on this page.