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, etc.)
• 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

Once verification is set, it might 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

Create a verification level in the Dashboard:

1. Go to Integrations → Applicant levels (Individuals) and click Create level.
2. Scroll down and set up the steps your applicants must take to get verified with actions. Make sure your steps include only any of the following verification methods:
   1. Selfie
   2. Payment methods
   3. Questionnaire
   4. Phone verification
   5. Email verification
3. On the Steps tab, from the Type drop-down list, select Applicant actions.
4. Continue with setting up the level as required and save your changes when done.

📘

Note

If you include Identity document and/or any other verification steps that have not been mentioned above, you will not be able to select the Applicant actions option.

Step 2: 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 3: View verification results

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