Handout

Sumsub
User
Verification
Course
Module 2

Setting Up a Secure
& High-Converting
Verification Flow
Sumsub User Verification Course 2
Module 2 Session 1:
Integration types and
Global settings

In this module, we move to how verification is actually built

inside Sumsub. The key idea is that no two verification journeys
are identical: businesses differ by risk, audience, and regulatory
requirements, so the setup needs to be flexible.

Integration options ↘ Software Development Kit, or SDK. Sumsub provides

WebSDK for desktop and mobile browsers, plus native
software development kits for iOS and Android. There are
also plugins for React Native, Flutter, and Cordova. The
SDK includes the verification steps, while the Dashboard
configuration defines what the user actually goes through.

↘ Application Programming Interface, or API. Some clients build

their own user journey and send collected data to Sumsub
for verification via API. This gives full control over design, but
needs more development work.

↘ Unilink. A secure link sent by email, text, or chat that opens a

hosted verification flow. Results are visible in the Dashboard
and can be routed to channels like client backend, email,
Slack, or Telegram.

Sumsub User Verification Course 3

 Global Global Settings are top-level configurations that define how
settings verification behaves across cases. For this module, the focus is
on settings under User Verification, AML Screening, and Data
Comparison.

Examples of what can be controlled:

↘ Minimum and maximum permitted age

↘ Duplicate rules, such as whether one person can have

more than one approved verification

↘ Identity document acceptance by country, document type,

and subtype

↘ Data comparison logic

↘ Proof of address configuration

Takeaway Integration defines how the journey enters your product.

Global settings define the guardrails that shape security
and user experience across every verification.

Sumsub User Verification Course 4

Module 2 Session 2:
Level creation

A verification level defines what a user must do to get verified.

Think of it as a checklist of steps. For example, ID + selfie, or ID
+ selfie + proof of address + questionnaire. Every applicant goes
through a level during onboarding. 

Why levels exist ↘ Not all users are the same. Levels let you create different
journeys for different cases: low-risk vs high-risk, standard
onboarding vs extra checks after onboarding. 

↘ Example setup:
1 Standard level: identity document + selfie

2 High-risk level: identity document + selfie +

proof of address + questionnaire 

How to create a level 1 Go to Integrations → Verification Levels → Individuals

2 Click Create level

3 Add a name and description

4 Choose level type: Standard or Applicant actions

for post-onboarding checks 

Sumsub User Verification Course 5

 Common steps ↘ Identity document
you can add
↘ Selfie for liveness and matching

↘ Proof of address, with optional geolocation

↘ Questionnaires for extra data like occupation

or source of funds

↘ Phone and email verification

↘ Non-document verification where supported

↘ Video identification for higher-risk cases

↘ Database validation for cross-checking data 

Takeaway Levels are the building blocks of verification. They let you
design different journeys for different risk profiles without
forcing every user through the same process.

Watch the level creation tour within Sumsub here

Sumsub User Verification Course 6

Module 2 Session 3:
UI customization and
questionnaires

Once the logic is built, the next step is making the flow feel like
part of your product, and collecting any extra data you need.

UI customization Sumsub lets you customize how the applicant journey looks
in WebSDK and MobileSDK: colors, fonts, buttons, logo, and
step instructions, all from the Dashboard, without coding. 


Typical setup flow 1 Open Customizations → Create customization

2 Create WebSDK customization

3 Name it, optionally add a description

4 Optionally import styles from your website 

Common controls ↘ Theme mode: light, dark, or both

teams use
↘ Reducing friction by skipping screens like welcome,
warning, or instructions

↘ Mobile behavior: force mobile, disable switching, hide

progress bar, remove borders

↘ Supported languages for the flow

↘ Fine-tuning in tabs like Logo and colors, Texts,

Images, Buttons

Sumsub User Verification Course 7

 Questionnaires Questionnaires collect additional onboarding information,
such as employment, source of wealth, or investment
knowledge.

How they’re structured:

↘ Built from sections with titles and optional descriptions

↘ Each section has a unique ID used for API calls and

conditional logic

↘ Questions support multiple answer types, including file

upload for supporting documents 

Two useful capabilities:

↘ Conditional logic using AND and OR to show extra sections

only when needed

↘ Risk scoring inside questionnaires by assigning risk values to

certain answers 

Takeaway Customization reduces drop-off by keeping verification

on-brand and clear. Questionnaires let you collect and
structure the extra data that risk and compliance
often require.

Watch the UI customization tour within Sumsub here

Sumsub User Verification Course 8

Module 2 Session 4:
Risk scoring &
automation

Once levels are built, risk scoring makes the flow more
intelligent. It turns multiple applicant signals into a single
indicator of trust that can be used to drive automation. 

What can influence Signals can include country, device data, phone and email,
risk scoring behavior, and verified results such as document information,
plus selfie-related indicators like whether the person was
alone, holding a phone, or asleep. 

How it works 1 As a user starts verification, predefined rules assign

weights to signals

2 Example: adding points when a VPN is detected or when

a phone number has been used before

3 Points are summarized into a total score for the applicant 

Sumsub User Verification Course 9

 What the score is ↘ Automatically approve low-risk users
used for
↘ Route high-risk users into a higher-security level

↘ Trigger actions like tagging or creating an Enhanced Due

Diligence case in case management 

! Important note: risk scoring does not change the verification

result by itself, it’s used in automation logic.

Takeaway Risk scoring and automation make verification adaptive: they

help teams handle scale, focus manual effort where
it matters, and keep flows flexible as risk patterns change.

Sumsub User Verification Course 10

Module 2 Session 5:
Workflow builder

Workflow Builder is where everything connects: levels,

conditions, actions, and manual review. It’s a no-code
visual tool that lets teams build complete verification flows
on a canvas. 

Core building 1 Level step: connects the verification levels you created
blocks
2 Condition: decides when a specific path should trigger

3 Action: applies tags, adds notes, or creates a case

4 Review step: controls manual review and blocking logic 

Common ↘ Country-based routing: applicants from Germany can

use cases be routed to video identification to comply with BaFin
requirements 

↘ Conversion optimization: users from Brazil, Indonesia,

India, or Nigeria can be routed to non-document verification
to improve pass rates 

↘ Combining approaches: the same workflow can include

both document-based and non-document verification,
switching via conditions 

Sumsub User Verification Course 11

 Case creation Workflow Builder can trigger automatic case creation for
case management, including blueprint selection and
assigning compliance officers immediately. 

Takeaway Risk scoring and automation make verification adaptive:

they help teams handle scale, focus manual effort where
it matters, and keep flows flexible as risk patterns change.

Watch the Workflow Builder tour within Sumsub

Sumsub User Verification Course 12

Sumsub
is looking
forward to
seeing
you soon!

Sumsub User Verification Course 13

 © Sum and Substance Ltd. (UK), 2026.
All rights reserved. Company number 09688671.