As part of enhanced due diligence, you might want to to request additional actions from customers who have already completed their onboarding process but are engaging in financial activity, based on transaction data.

For this purpose, you can create rules that request your applicants to perform certain actions. For example, to pass a Liveness check based on the applicant activity by changing the applicant level or asking applicants that reach a specific deposit amount threshold to pass a selfie check or provide proof of funds.

📘

Note

• When creating such rules, you must remember that the results of the required actions need to be checked before the transaction status is updated.
• To trigger Applicant actions during the onboarding process without scoring, you can use Workflow Builder instead.

Create rules and change applicant level

To change the verification level based on applicant actions:

1. Create a rule that will be a catalyst to trigger the level change.
2. Specify the rule condition and transaction type to trigger the rule.
3. In the Affect applicant section, select Change level and choose the level.

Once the rule is triggered, it will change the level as selected and set the transaction status to Awaiting User. This will stop scoring until the applicant completes the flow at the new level.

As you configure the action to change the applicant level, you also need to create two additional rules that will be triggered once the action is completed, in order to update the transaction status and prevent repeated requests for the same action:

1. Create two additional rules and select the Stop on match checkbox for both.
2. Configure the first rule condition as:
   If
   ->
   Field
   ->
   applicant.Action.review.Review.Answer
   ->
   equals
   ->
   Value
   ->
   GREEN
    
3. Configure the second rule condition as:
   If
   ->
   Field
   ->
   applicant.Action.review.Review.Answer
   ->
   equals
   ->
   Value
   ->
   RED
    
4. Set the Rule priority field for both rules.

Without these rules, the same action may be triggered multiple times (for example, if the applicant resubmits the same data).

⚠️

Important

The Stop on match rules must have a higher priority than the rule that triggers the action. This ensures they are evaluated first and can stop further processing.