Use cases
Customer onboarding
Verify new customers remotely before the first deposit, order or account.
The job
Online services need to know who is signing up. The verification should be quick for the user and give your team a result it can act on.
The flow
- Start. Your backend creates a session for your onboarding scenario.
- Document. The user photographs an ID. The document is read and checked for fraud. See document verification.
- Selfie and face match. The selfie is matched to the document portrait. See face verification.
- Liveness. The user moves the face through two ovals. See liveness.
- AML screening. Sanctions, PEP and adverse media are screened, and profiles can be monitored daily. See AML screening.
- Result. Your system reads the status or receives a webhook.
Scenario setup
In the no-code scenario editor you choose the steps, documents and countries, set thresholds and rules, and add the AML step. Start from a template and adjust.
What your system receives
A session status and a list of results for each step. The dashboard shows the session log, with export and manual decision. See session statuses.
Next
Try the interactive tour, read the quick start, or check the pricing.
Questions, answered plainly
Can I add AML screening to onboarding?
Yes. International AML screening can run in the same flow. It is billed separately, at $0.40 a check.
What if the user starts on a desktop?
Hand the user to a phone with a QR code, or send a one-time link.
How do I get the decision?
Read the session status through the REST API, or receive the SESSION_COMPLETE webhook. You can also make a manual decision in the dashboard.