--- updatedAt: 2026-10-01T13:46:13.000Z agentTools: projectIndex: https://docs.sumsub.com/llms.txt --- # Reset verification steps # Overview Use this method in scenarios where it is required for the applicant to go through a particular verification step—[verification type](https://docs.sumsub.com/sumsub/docs/understand-verification-types) an applicant has to complete—again. In effect, the method deactivates the specified step in the SDKs, allowing it to be re-initiated and new data to be collected. ### Notes - Not all verification steps can be reset. See the list of [available steps for reset](#available-steps-to-reset) below. - Resetting the `APPLICANT_DATA` step also clears the applicant's taxpayer data in `fixedInfo.tins`: the `tin` value is cleared if the step defines `tin`, and the `country` value if it defines `taxResidenceCountry`. Entries left fully empty are removed, and `tins` is removed entirely once empty. The step then returns to a documents-requested state, prompting the applicant to resubmit the data. - Resetting the `PHONE_VERIFICATION` step also clears the applicant's confirmed phone number stored in the top-level `phone` field, in addition to deactivating the phone-confirmation check. After the reset, the phone step no longer pre-fills the previously entered number in the SDK, and the applicant must enter and confirm a number again. The `info.phone` (extracted) and `fixedInfo.phone` (provided) numbers are stored separately and remain unaffected. ## Required permissions To use this method, your [app token](https://docs.sumsub.com/sumsub/docs/app-tokens) must have the following [permissions](https://docs.sumsub.com/sumsub/docs/user-roles#permissions): * **Reset applicants** * **Moderate applicants** # 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` A verification type 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](https://docs.sumsub.com/sumsub/docs/identity-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` A verification type where applicants need to complete any of the following **Selfie** options: If you need an applicant to pass two steps of the above, add the 2nd selfie step to the verification level.
`SELFIE2` Same as **SELFIE**. Used in case you need to add another **Selfie** option to the verification level.
`PROOF_OF_RESIDENCE` [Address verification](https://docs.sumsub.com/sumsub/docs/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.
`PAYMENT_METHODS` A verification type where applicants confirm which payment methods they use — bank card, bank account, e-wallet, or crypto wallet.
`QUESTIONNAIRE` A verification type where applicants are required to fill in the pre-configured [questionnaire](https://docs.sumsub.com/sumsub/docs/questionnaire). Note that you cannot add this step to the verification level if no questionnaire is [created](https://docs.sumsub.com/sumsub/docs/questionnaire-get-started) in your system.
`PHONE_VERIFICATION` A verification type where the [applicant’s phone number is checked](https://docs.sumsub.com/sumsub/docs/email-and-phone-verification) to verify whether it is blocklisted or not, and how much risk the specified phone number poses.
`EMAIL_VERIFICATION` A verification type where the [applicant's email address is checked](https://docs.sumsub.com/sumsub/docs/email-and-phone-verification) 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](https://docs.sumsub.com/sumsub/docs/no-document-verification).

### Note The `COMPANY_BENEFICIARIES` step cannot be reset. To remove a beneficiary applicant from the company's control and ownership structure, use the [following method](https://docs.sumsub.com/sumsub/reference/unlink-beneficiary-from-company-kyb-20). # Request example ```curl curl -X POST \ 'https://api.sumsub.com/resources/applicants/62164ddf8a86e20bbd280000/resetStep/PHONE_VERIFICATION' \ -H 'X-App-Token: ' \ -H 'X-App-Access-Sig: ' \ -H 'X-App-Access-Ts: ' ``` # Response explained If the request is successfully sent and processed, you will get the following response: ```json { "ok": 1 } ``` If the request fails, you will receive an HTTP response containing an error code along with a message explaining the error. For example: ```json { "description": "Applicant with id 63e099da46199a0000000000 doesn't have a step IDENTITY2", "code": 409, "correlationId": "8459080186aa5aaea8dc4e0000000000" } ``` # OpenAPI definition ```json { "openapi": "3.1.0", "info": { "title": "sumsub-api", "version": "1.0" }, "servers": [ { "url": "https://api.sumsub.com" } ], "components": { "securitySchemes": { "sec0": { "type": "apiKey", "name": "X-App-Token", "in": "header", "x-default": "" } } }, "security": [ { "sec0": [] } ], "paths": { "/resources/applicants/{applicantId}/resetStep/{idDocSetType}": { "post": { "summary": "Reset verification steps", "description": "", "operationId": "reset-single-verification-step", "parameters": [ { "name": "applicantId", "in": "path", "description": "Unique applicant identifier in the Sumsub system.

This identifier is a random combination of 24 digits and lowercase Latin characters. It is automatically generated when the applicant is created on the Sumsub side, and can be found in the [Dashboard](https://cockpit.sumsub.com/checkus/#/applicants/individual?limit=10&page=0).

If the `applicantId` is unknown to you, use the [Get applicant data (externalUserId)](https://docs.sumsub.com/sumsub/reference/get-applicant-data-via-externaluserid) method to fetch it.", "schema": { "type": "string" }, "required": true }, { "name": "idDocSetType", "in": "path", "description": "Specify the identifier of the [verification step](#available-steps-to-reset) to be reset.", "schema": { "type": "string", "enum": [ "COMPANY_DATA", "COMPANY_DOCUMENTS", "APPLICANT_DATA", "IDENTITY", "IDENTITY2", "IDENTITY3", "IDENTITY4", "SELFIE", "SELFIE2", "PROOF_OF_RESIDENCE", "PROOF_OF_RESIDENCE2", "PAYMENT_METHODS", "QUESTIONNAIRE", "PHONE_VERIFICATION", "EMAIL_VERIFICATION", "E_KYC" ], "default": "IDENTITY" }, "required": true } ], "deprecated": false } } }, "x-readme": { "headers": [], "explorer-enabled": true, "proxy-enabled": true }, "x-readme-fauxas": true } ```