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

1. Set up the WebSDK or MobileSDK integration.
2. In the Dashboard, open the Individuals page and click Create level.
3. Configure verification steps, set configuration, configure document settings, configure AML Screening, use integration abilities, review execution flows, and many more.
4. Test your level to see how it behaves.
5. Go live.

Configure verification steps

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

1. Provide a name and optional description that you want to use for the new level.
2. Select the level type:
   • 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 more information about applicant actions, see this article.
3. Select the Enable WebSDK 2.0 for this level toggle to use the WebSDK 2.0.
4. From the Database Validation drop-down list, select one or multiple solutions for identity document and personal data validation against external data sources. For more information, see this article.
5. Select SDK translation. You can configure translations, as described in this article.
6. Select SDK customization. When configuring 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:
7. Enable Video Identification and select the document types that can be uploaded.
8. Configure verification steps as required.

🚧

Limitation

We do not support Proof of Address checks in levels with Video Identification. If you need to have Proof of Address checks after Video Identification checks, create a separate level for Proof of Address and use Workflow Builder to change the level once Video Identification is approved.

Set configuration

On the Configurations tab, set up the level settings from the left-hand menu.

Location settings

In Location settings, you can configure access controls and restrictions for applicant verification based on their location:

1. In the Country restriction for verification steps section, configure the countries that are accepted (or restricted) at this level and select the verification steps where the filter should be applied. Mind that this setting always affects the Applicant data and Identity document steps by default, and these steps cannot be excluded.
2. In the IP settings section, configure verification access to control applicants’ IP addresses by allowing or blocking selected countries.
3. In the USA resident settings section, select the checkbox to decline applicant profiles that belong to USA residents automatically.
4. In the VPN detection section, enable the checkbox to pause verification when a VPN is detected. Verification will resume once the applicant disables their VPN.

Fraud prevention

In the Fraud prevention section, you can enable checks across email, phone, IP, geo, and device signals to spot fraud early and allow only trusted users to continue.

1. In the Device intelligence section, enable the checkbox if you want to collect device signals during verification for suspicious activity detection.
2. In Applicant Insights, select the options to enable the following checks:
   1. Email insights — to enable email risk assessment.
   2. Phone insights — to enable phone risk assessment.
   3. IP insights — to enable advanced IP check.
   4. AI suspicious name check — to enable AI checks that determine whether the applicant's name is considered suspicious. If the applicant's name falls under the AI criteria, the applicant profile receives any of the following risk labels: Famous person, Strange name.

AML Screening

In the AML Screening section, you can turn off or customize AML screening.

1. Clear the Enable AML screening checkbox in case you do not need it for this level. By default, the checkbox is enabled.
2. In the Custom AML screening section, select the checkbox if you want to provide custom AML settings for this level. By default, global AML screening settings are applied.
3. From the Choose the provider you’d like to use for AML screening dropdown list, select a provider for your custom AML screening settings.
4. In the Search configuration section, select whether the search is done by warning types or with a custom search profile.
   1. To configure search by warning types, use the checkboxes to select the categories you want to include in the screening, such as Sanctions, Warnings, Fitness & Probity, and Politically Exposed Persons (PEPs). From the Adverse Media General dropdown list, select the types of adverse media to be considered.
   2. To configure search by custom search profiles, enter a profile identifier. For more information about AML Screening configuration, refer to this article.
5. In the Name matching criteria section, select how strictly names should be matched during AML screening at this level.
6. From the Choose whether to enable auto-screening for AML dropdown list, select whether auto-screening should be enabled, disabled, or set to default. If enabled, select the Delegate manual review tasks for ongoing monitoring checkbox if you want to send all approved applicants found in AML lists to your compliance officers for manual review.

ID document settings

You cannot customize the ID document settings during level creation; adjustments are only possible afterward. Once the level is set up, configure the document verification settings as required.

Advanced settings

In Advanced settings, you can configure advanced options such as notifications, environment, and data processing preferences:

1. Select a source key from the dropdown list. This option is available only if you have at least one source key configured in your environment.
2. From the Email notifications dropdown list, select when notifications should be sent to your applicants. You can select any of the following options:
   1. Send when applicant is approved.
   2. Send when applicant requires resubmission.
   3. Send when applicant is rejected.
3. In the Applicant scoring section, enable the checkbox to calculate the risk score of your applicants.
4. In the Visibility configuration section, select the checkbox to make the level available only in Production mode.
5. Select the Disable automatic checks checkbox if you want to review each applicant yourself manually. Mind that this option stops all automatic checks.
6. Select the Skip consent screen checkbox to allow your applicants to pass verification without forcing them to accept the terms and conditions. Mind that this option is only available for Questionnaire and/or Applicant data steps. If your verification level includes any other steps, this option will not be displayed. For more information, see this article.
7. In the Custom consent for data processing section, choose how to display consent on the agreement screen in the WebSDK:
   1. Default — no additional consent link or text will be shown.
   2. Link — provide a link to your personal data processing consent (if any) to be added to the agreement screen.
   3. Text — provide a custom processing consent text to be displayed to your applicants on the agreement screen.

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 upon clicking the Integrations button.

import snsWebSdk from '@sumsub/websdk';

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

  // you are ready to go:
  // just launch the WebSDK by providing the container element for it
  snsWebSdkInstance.launch('#sumsub-websdk-container')
}

Use WebSDK permalinks

If you have not yet integrated with Sumsub, you can still let your applicants pass verification by generating and sending them a direct link to our WebSDK.

To generate a link:

1. Open any of your existing verification levels.
2. Click Verification links and follow the instructions.

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 performance:

1. Find a level that you want to run.
2. Click Run level.
3. Go through your level to see how it behaves.

Manage level settings

You can manage your verification levels as follows:

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