Get started

Adjust verification steps for different types of users.

Configure your verification levels to collect information about your applicants in a user-friendly manner:

  1. Set up WebSDK or MobileSDK integration.
  2. In the Dashboard, open the Individuals page and click Create level.
  3. Configure general level settings and add required steps, define ID document parameters, set watchlists settings, use integration abilities, review execution flows, and many more.
  4. Test your level to see how it behaves.
  5. Go live.

Set general level information

Set the name and optional description for your levels and configure additional options, such as a privacy note text, a list of countries that you might want to include or exclude, and so on.



Level name

Provide the name that you want to use for the new level.

New version of WebSDK

Enable this toggle to use WebSDK 2.0.


Provide an optional description.


Select an SDK type that you want to use:

  • Standard — for standard applicant verification, for example, to onboard new applicants.
  • Applicant actions — to perform additional verification that may be triggered by specific applicant activities. For example, every time your applicants make a transfer or payment, they are asked to confirm their identity by passing an action check. You can use actions for Liveness & Face match, payment method, short video fragment, questionnaire, and selfie checks.
  • Module — allows you to perform a Liveness & Face match check only.

Action type

[Available only when Type is Applicant actions]

Select which action should occur:

  • Face auth — for a Liveness check. Requires a photo or video selfie.
  • Additional verification — for any additional checks, such as questionnaires, payment methods, short video fragments, and so on.

Supported ID documents

Select the Use custom ID documents settings checkbox to set the requirements for passport, ID card, driving license and residence permit verification. When selected, the Custom ID Documents Settings section becomes available.

Countries and territories

Select the countries that are accepted at this level. The applicant will be rejected if their country of residence or document information is not among the listed countries.

Source key

Select a source key that you might have configured. This drop-down list is available only if you have at least one source key configured in your environment.


Select the Use custom Watchlist settings checkbox to enable and configure the Custom Watchlist settings to override the default search criteria for AML screening configured in Global Settings.

Applicant Insights

Select the following checkboxes to activate extra checks:

Customer emails

Select the Send email about verification statuses checkbox to notify your applicants every time their verification status changes. Such notifications are sent automatically by email.

Transaction monitoring settings

Select the Create KYC transactions during onboarding checkbox to calculate the onboarding risk score of your applicants.

Visibility configuration

Select the Level should only be available on production environment checkbox to make the level available only in production mode.

This option is available only in production mode.

Privacy link

Enter the link to your own privacy policy note (if any). The link will be added to the agreement screen in Web SDK.

If you want to use the default privacy note, leave the Privacy link field blank.

Privacy note text

Enter a custom privacy text to be shown to your applicants on the agreement screen in Web SDK. To use the default privacy text, leave this field blank.

Configure required steps

On the Required Steps tab, configure verification level steps that your applicants must pass:

  1. Click Add new step and from the drop-down list, select a verification type and verification method. Each step has its own verification type. For example, you may want to create two steps; the first one would be of the Identity document verification type with the File Upload verification method and the second one would be Selfie with Advanced Liveness Check. For more information about the available verification types and methods, see Understand verification types.

  2. [Optional] Select the Video Ident checkbox if you want your applicants to confirm their identity in a video interview with an operator:

    1. From the Select document types that can be uploaded drop-down list, select which documents an applicant can upload. Such documents are taken from the identity documents; make sure to create a step with the Identity document verification type beforehand. Otherwise the drop-down list will be empty.
    2. From the Select steps to follow outside of video identification drop-down list, select the steps an applicant must pass outside the video identification. You can select the steps from those added with the Add new step button beforehand. The steps outside the video identification are used to verify what you cannot check with the video identification. For example, a phone number, email and questionnaires.
  3. Click Save.



Video Ident requires a Selfie verification type to be added as a step along with the Web camera photo verification method (recommended).

Map SDK customization

In the SDK Setup section, select an SDK customization that you want to use.

When configuring a customization, you will be able to set colors and styles exactly as you want them to appear to your applicants. You can also add instructions and tips for each of your verification steps and then preview the resulting verification flow with just a few clicks.

Define custom document settings

Configure document verification settings that are unique for your level:

  1. In the General section, enable the Use custom ID documents settings checkbox.
  2. On the Custom ID documents settings tab, expand a continent and select a country.
  3. Configure the settings as necessary.

Set watchlist settings

Configure search criteria for AML screening that are unique for your level.



To use this option, enable the Use custom Watchlist settings checkbox in the General section.

To customize watchlist settings:

  1. In the General section, enable the Use custom Watchlist settings checkbox.

  2. On the Custom Watchlist settings tab, specify categories of PEPs and persons in watchlists:

    1. PEP Class 1 — persons among heads of state or those from national parliaments and national governments.
    2. PEP Class 2 — persons from regional governments, regional parliaments.
    3. PEP Class 3 — persons from senior management and the board of SOEs.
    4. PEP Class 4 — mayors and members of local city councils.
    5. Unclassified PEP — other PEP categories including all the classes above.
    6. Sanctions, Warnings, and Fitness & Probity — persons found in sanction lists, watchlists or those not compliant with the Standards of the Fitness and Probity Regime. Enable or disable the included check boxes to turn on/off the options separately:
      1. Warnings — monitoring persons in sanctions and watchlists.
      2. Wanted Fitness & Probity — monitoring persons who are not compliant with the Standards of the Fitness and Probity Regime.
  3. From the Adverse Media General drop-down list, select types of compromising published information and/or voiced in media and related to applicants.

  4. From the Fuzziness drop-down list, select how strictly the name matching should be performed.

  5. Select the Delegate manual review tasks for ongoing monitoring checkbox if you want all approved applicants in AML lists to be sent to your compliance officers for manual review.

  6. Click Save to save the settings or Cancel to discard changes.

Use integration code

You can use automatically generated integration code to integrate with our WebSDK. Just save the level and this functionality becomes immediately available to you on the Integration Code tab.

import snsWebSdk from '@sumsub/websdk';

 * @param accessToken - access token that you generated on the backend with levelName: basic-kyc-level
function launchWebSdk(accessToken) {
    let snsWebSdkInstance = snsWebSdk.init(
            // token update callback, must return Promise
            () => this.getNewAccessToken()
            lang: 'en', //language of WebSDK texts and comments (ISO 639-1 format)
        .on('onError', (error) => {
          console.log('onError', payload)
        .onMessage((type, payload) => {
          console.log('onMessage', type, payload)

    // you are ready to go:
    // just launch the WebSDK by providing the container element for it

Use WebSDK permalinks

If you have not yet integrated Sumsub into your website, you can still let your applicants pass identity verification by generating and sending them a direct permanent link to our WebSDK. You can generate the link on the WebSDK permalinks tab.



This section is available only when you edit an existing verification level; when you create a new level, the section is not shown.

Review checks execution flow

Once you save the level, you can open the Checks Execution Flow tab to see the sequence of steps, in which the level will be operating.

Test your level

Try out your levels before letting your applicants use them to ensure maximum level performance:

  1. Find a level that you want to run.
  2. On the right-hand side of the level record, click Run level in new tab.
  3. Go through your level to see how it behaves.

Manage level settings

You can manage the level settings as follows:

  • Edit level settings. Lets you adjust your existing levels according to your current business specification.
  • Remove any level that you have configured previously. Lets you declutter your environment by removing level that are no longer in use.
  • Copy level configuration. Lets you inherit the selected level settings in case you want to create a new level but with some differences to the parent one.