An applicant action is an additional check that you can configure in your verification level settings. Actions can be triggered by specific events performed by applicants.

For example, every time your applicants make a transfer or payment, they are asked to confirm their identity by passing an action check.

Why do you need to use applicant actions

Applicant actions might be used as post-onboarding checks that provide an additional layer of security when your applicants perform some activities after they have passed initial verification.

These are the most popular and effective practices of using the applicant actions in your verification:

• Requesting a Liveness check when the applicant makes a financial operation or any action associated with the account (a password reset, Two-Factor Authentication, and so on)
• Performing a Payment method check when the applicant adds a new means of payment.
• Asking to fill out a questionnaire when the applicant withdraws a huge amount to clarify the information about this transaction.

📘

Note

The Sumsub's Transaction Monitoring solution also offers the ability to set triggers and define further actions while checking transactions. To do so, you have to create custom rules that will ensure an extra level of security within many cases.

How applicant actions work

An applicant action scenario depends on the configuration of your verification level. The following verification steps can be included:

• Selfie
• Payment methods
• Questionnaire
• Phone verification
• Email verification
• Travel Rule: recipient information

Once verification is set, it will generally look as follows:

1. An applicant performs a particular action.
2. The action triggers the established check, and the applicant is asked to pass additional verification.
3. Once done, the verification results are displayed in the applicant profile.

📘

Note

Passing an action check does not affect the current applicant verification status.

Add applicant actions to verification level

To configure applicant actions, you have to create a verification level, make adjustments in the level settings, and set up the SDK.

Step 1: Create and configure verification level

In the Dashboard, create a verification level:

1. Go to the Integrations section, open Applicant levels (Individuals) and click Create level.
2. In the pop up window, select Applicant actions and click Continue.
3. In the created level, set up the steps your applicants must take to get verified with actions. You can select any of the following verification methods:
   1. Selfie
   2. Payment methods
   3. Questionnaire
   4. Phone verification
   5. Email verification
   6. Travel Rule: recipient information
4. Continue with setting up the level as required and save your changes when done.

📘

Note

Once you select the Applicant actions level type, the level type cannot be changed afterwards.

Step 2: Configure verification level

To set up configurations for Applicant actions, on the Configurations tab, select the level settings from the left-hand menu.

Note that the configurations for Applicant actions are limited compared to the standard levels due to the nature of the Applicant actions structure.

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 will affect the payment methods check by default.
2. In the IP settings section, configure verification access to control applicants’ IP addresses by allowing or blocking selected countries.
3. 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.

Advanced settings

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

1. In the Visibility configuration section, select the checkbox to make the level available only in Production mode.
2. Check the Disable automatic checks box if you want to review each applicant manually. Mind that this option stops all automatic checks.

Step 3: Initialize SDK

To initialize the WebSDK for using applicant actions:

1. Generate an access token using this API method and specify the following parameters of the verification level to be passed to the WebSDK:
   1. externalActionId
   2. userId
2. Install an NPM package or use the CDN version of the script and launch it with the accessToken you have generated at the previous step.

Step 4: View verification results

Find the applicant action check results in the applicant profile or get it via webhooks.