---
updatedAt: 2026-11-02T15:41:33.000Z
agentTools:
  projectIndex: https://docs.sumsub.com/llms.txt
---

# Protect e-commerce and loyalty program sign-ups from fraud 

Implement a verification flow to defend your platform against bots and fake accounts.

As digital technology grows rapidly, it sometimes becomes a real weapon in the hands of dishonest users or entire organized illegal schemes. Many online e-commerce platforms are now a perfect target for various fraudster attacks:

* Bot sign-ups.
* Fake accounts created for coupon or loyalty fraud.
* Promo abuse via disposable identities.
* Account farming using emulators, cloned apps, and anti-detect browsers.

At Sumsub, we care about safety and transparency within the digital business environment and suggest implementing a powerful adaptive flow that will eliminate fraud at an early stage, while staying effortless for genuine users. Combine our solutions via Workflow Automation to create the sign-up flow.

* **Fraud prevention**. Include various checks to collect and verify essential data at sign up:
  * [Digital footprint checks](https://docs.sumsub.com/sumsub/docs/digital-footprint-checks) for contact data (email and phone) validation and online presence assessment.
  * [Device intelligence](https://docs.sumsub.com/sumsub/docs/device-intelligence) for device behavior analysis.
  * [Advanced IP check](https://docs.sumsub.com/sumsub/docs/advanced-ip-check) for estimating all risks and patterns associated with the user IP address.
* **Identity verification**. Add [documentary checks](https://docs.sumsub.com/sumsub/docs/identity-verification) and include [Liveness](https://docs.sumsub.com/sumsub/docs/liveness) to resolve risky corner cases that require complete user verification.

# Create sign-up verification flow

Combine the checks into the sign-up scenario built around safety: to catch bots and fake accounts early, without adding friction for legitimate users.

## Step. 1 Create verification levels

The current scenario requires two separate verification levels, each covering a specific stage of the journey:

* **Initial sign-up verification level** for collecting and validating contact data, and running the Fraud prevention checks listed above.
* **Identity verification level** for performing user verification with an identity document and selfie when suspicious patterns are detected.

Add the initial sign-up verification level:

1. [Create the verification level](https://docs.sumsub.com/sumsub/docs/configure-verification-levels) that includes both the **Email verification** and **Phone verification** [steps](https://docs.sumsub.com/sumsub/docs/verification-steps).
2. Configure the **Fraud prevention** checks in the level:
   1. Go to the **Configurations** tab.
   2. Enable the following checkboxes: **Email insights**, **Phone insights**, **IP insights**, and **Capture device data**.
   3. [Set up](https://docs.sumsub.com/sumsub/docs/configure-verification-levels#configure-verification-steps) the rest of the level settings as required.

<Callout icon="📘" theme="info">
  ### Note

  The verification steps should be placed in the exact order described above. Otherwise, level creation is blocked.
</Callout>

<Image src="https://files.readme.io/5aca233c5ff6cebb30203627edc5e770a8480d4f412467b4031ee8341e880223-Sign-up_level.png" width="80%" framed={true} />

<br />

<Image src="https://files.readme.io/b3d89d1c411f627a9aa47111e43ce1a179288b8cf843e9432106e8235bab475c-Sign-up_level_2.png" width="80%" framed={true} />

Add the identity verification level:

1. Create the verification level that includes both the **Identity document** and **Selfie** steps.
2. In the **Identity document** step, set any suitable document types.
3. In the **Selfie** step, select the **Advanced liveness check** option.
4. Configure the rest of the level settings as required.

<Image src="https://files.readme.io/092c5b3f0795fed197a0eef7fc4e32eea0b4ead8118eee197f7b51309fb4428b-Sign-up_level_kyc.png" width="80%" framed={true} />

## Step 2. Add initial node to collect and assess contact data

Go to Workflow Automation to place the level node, which launches the verification flow. To add the [Level step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#add-level-step) node:

1. In the Dashboard, go to **Configurations** → **Workflow automation** → [Active workflow](https://cockpit.sumsub.com/checkus/sdkIntegrations/workflows/active).
2. Navigate to the **Standard** tab and go to the **Draft** view.
3. Add **Level step** to the canvas and attach the initial sign-up verification level by selecting it from the list.

<Image src="https://files.readme.io/f7a1616861f5efe75220b109c29b5b09c61aa692736d208fb7ba7130b36cc4a8-Node_1.png" framed={true} />

## Step 3. Send suspicious users for identity verification

Adjust the verification flow so applicants showing some questionable signs are required to pass identity verification.

Set up the [conditions](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#build-conditions):

1. Click on the initial node created earlier and select **Condition** as the next step.
2. Select the **If** logical operator.
3. From the **Field** drop-down list, select the `checks.email.nonDisposable` parameter.
4. Set the logical condition to **equals** and specify `RED` as the value below.
5. Within the same branch, add more conditions for other checks and their fields:
   1. Click **Or group** and configure the conditions:
      1. From the **Field** drop-down list, select the `checks.phone.blacklisted` parameter.
      2. Set the logical condition to **equals** and specify `RED` as the value below.
   2. Click **Or group** and configure the conditions:
      1. From the **Field** drop-down list, select the `checks.all.ip.vpns` parameter.
      2. Set the logical condition to **contains** and specify `RED` as the value below.
   3. Click **Or group** and configure the conditions:
      1. From the **Field** drop-down list, select the `applicant.riskLabels.deviceCheck` parameter.
      2. Set the logical condition to contains any and select the following values: `virtualMachine`, `emulator`, `jailbroken`, `rooted`, and `locationSpoofing`.

<Callout icon="📘" theme="info">
  ### Note

  If you plan different outcomes for some conditions, add another branch instead of using **Or** groups.
</Callout>

<Image src="https://files.readme.io/619e559ccca88159a120eb308bd2a79e559afaede7a81ef11f281ef518bcb03e-Node_2.png" framed={true} />

Configure the identity verification path:

1. Within the added **Condition** node, select [Action](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#configure-actions) as the next step.
2. Select the type of action: **Manage tags**.
3. Select the **Add tags** checkbox.
4. From the drop-down list below, choose the required tags to assign.
5. Click **Choose next step** and add the **Level step** node.
6. Within the added **Level step** node, select the identity verification level.

<Image src="https://files.readme.io/67836631021c024bfa7b3e27e60b8f4634d02ac6fc9f09a250814f5a9cec5e63-Node_3.png" framed={true} />

## Step 4. Set up fraudster rejection

Add nodes to reject applicants whose device behavior genuinely indicates a high-risk user. Configure the rejection path:

1. Within the **Condition** node, add and adjust another condition branch:
   1. Click **Add new branch** and select the **If** logical operator.
   2. From the **Field** drop-down list, select the `applicant.riskLabels.deviceCheck` parameter.
   3. Set the logical condition to **contains** any and select the following values: `tampering`, `antiDetectBrowser`, `badBot`, `fridaTool`, `clonedApp`, and `mitmAttack`.
2. Click **Choose next step** and select **Action**.
3. Configure the **Action** node:
   1. Select the type of action: **Manage tags**.
   2. Select the **Add tags** checkbox.
   3. From the drop-down list below, choose the required tags to assign.
4. Within the **Action** node, click **Choose next step** and select [Review step](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#set-up-review-steps).
5. In the **Review step** configuration, identify the type of terminal step: select **Final reject**.
6. Specify reasons or add labels to explain the decision.

<Image src="https://files.readme.io/2402ccc84af5394a480b43c63885e8700729f0fd2c20c02946ec99dfbdb74399-Node_4.png" framed={true} />

## Step 5. Start using flow

Once the flow is created and configured, you can save the draft, perform test verification, and publish the flow to run the checks:

1. Save the draft and experiment with your flow — [create copies and conduct tests](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#create-multiple-versions-of-your-workflow).
2. [Publish the flow](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#publish-your-flow-and-go-live) to go live once the flow configuration is tested.

## Step 6. Receive verification results

[Get verification results](https://docs.sumsub.com/sumsub/docs/get-started-with-workflow-builder#review-verification-results) via the [webhooks](https://docs.sumsub.com/sumsub/docs/user-verification-webhooks) or view them in [applicant profiles](https://docs.sumsub.com/sumsub/docs/review-results-in-applicant-profile).

The configured flow kicks in only when the findings signal danger and takes the appropriate action, while genuine sign-ups remain completely unnoticed.

Looking to explore fraud prevention solutions beyond this workflow? [Get in touch](https://sumsub.com/free-demo/) with our team to discuss your platform's needs.