Second screen
kills conversion
Every interruption in signup costs users you already paid to acquire.
By use case
Onboarding that clears in one call
Identity, ownership and screening inside the signup request — so the applicant meets one screen and you keep a full decision record.
What you switch on
What this use case needs switched on
Identity and screening are one step, not two systems.
Why this matters here
Every second you add at signup, you pay for twice.
Once in conversion, and again in the queue — because a slow check invites a batch, and a batch invites a backlog. The alternative is not a weaker control; it is the same control, completed inside the request.
One threshold
for every segment
A retail applicant and a corporate counterparty judged by the same number.
Duplicates
onboarded twice
The same person arrives under two spellings and becomes two files.
1
Call at signup
150 ms
Median response
0
Extra screens for the user
−66%
Alerts after resolution
Workflow · Sideways
Scroll to advance
The workflow, step by step
-
Step 01
Resolve before you check
The applicant is matched against existing records first, so you screen a person rather than a form.
-
Step 02
Verify identity or ownership
Natural persons through KYC; companies through KYB down to beneficial owners.
-
Step 03
Screen in the same call
Sanctions, PEP and adverse media at the threshold set for that segment.
-
Step 04
Approved and in scope
The customer is registered for monitoring in the same flow, with the decision recorded.
complead / onboarding / resolve
- Applications today4,182
- Matched to existing318
- Resolve time11 ms
complead / kyc
- Verified3,864
- Referred112
- Owners traced2.8 avg
complead / screening / search
- Screened4,182
- Threshold0.85 retail
- Median148 ms
complead / monitoring / register
- Approved4,070
- Registered4,070
- Decision ownerrecorded
Resolve
Verify
Screen
Approve
What you answer to
What CDD actually requires
Four obligations, not one form: identify, verify, understand the purpose, and monitor. Programmes drift on the last one because it never finishes.
Read the compliance guides
Regulator
Identification and verification before service
At onboarding
Supervisor
Risk-based approach, documented
Ongoing
Regulator
Enhanced diligence where risk is higher
Per relationship
Auditor
Retrievable decision per customer
5–10 years
Case study · Banking
Read the case study
A digital bank cut its alert queue by two thirds
The fix was not a better threshold. Four systems held the same customer under six spellings; resolving them before screening removed most of the noise before any rule ran.
−66%
Alerts per month
0
Extra signup screens
1 day
To first live call
Cross-family links
Where teams like yours go next
FAQ
Before you ask us
Can this run synchronously?
Yes — median 150 ms, which fits inside the request your signup form already makes.
Can thresholds differ by segment?
Yes, and they should. Retail and corporate applicants carry different score bands, each recorded with its rationale.
What about non-Latin names?
Matching is transliteration-aware across Latin, Cyrillic, Arabic, Greek and Chinese, without converting to one script first.
What happens to referred applicants?
They open as a case with an owner and a reason, not as a stalled signup nobody owns.
See it inside your own signup flow
Bring a sample of applications. We will show you what clears in-call and what today’s process would have queued.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data