Scenario editor

What it does

A scenario is the definition of a verification flow: which steps the user goes through, which documents and countries you accept, and which thresholds and rules apply. The scenario editor lets you build it in the dashboard without code, and the decision engine applies your rules to the results.

What you can set

• Steps. Document, selfie, liveness, the questionnaire step and the AML step are all choices in the scenario. See document verification, face verification, liveness, questionnaire and AML screening.
• Documents and countries. The documents and countries that your flow accepts. See supported documents.
• Anti-fraud and liveness options. For example, session video can be switched on as an option of the liveness step.
• Thresholds and rules. The age window, from 16 to 100, is one threshold. See age check.
• Scenario options. Repeat-user search and lists. See face search.
• Callbacks and retention. The webhook options and the retention of session data are set per scenario. See data controls.

Templates

Start from a template and change what you need.

• Passport.
• Passport with a selfie holding the passport.
• Passport with liveness.

How it fits your integration

1. Build the scenario in the dashboard and note its identifier.
2. Your backend creates a session with that identifier through the REST API.
3. The user completes the steps in the widget.
4. Your backend reads the result, or a webhook tells it the session is complete.

One scenario per flow

Keep a separate scenario for each flow that differs in steps, documents or rules. A light scenario can serve sign-up, and a fuller one can serve a payout. Two examples are gaming player verification and high-value payments and payouts.

Next

The quick start walks through building a scenario and creating the first session.