Two-stage questionnaire then KYC

The job

Some services need a form before an identity check: the details of an applicant, a referral source, a few answers that decide which verification applies. The form should come first, so the identity check is started only for applicants who got through it.

The flow

Stage one: the questionnaire. The user fills in the form. The record stays idle while the form is unfinished.
The event. When the form is filled in and committed, the record becomes success and the QUESTIONNAIRE_COMPLETE webhook reaches your backend.
Your rules. Your backend looks at the answers and decides whether the applicant goes on. This step is yours.
Stage two: the verification. Your backend starts the full KYC session. The user completes the document, selfie and liveness steps. See KYC.
The result. The session status is read through the API, or the SESSION_COMPLETE webhook announces it.

Scenario setup

The questionnaire is a step in the scenario editor. It is the first stage of a two-stage flow. See the questionnaire product page for what it collects.

What your system receives

The questionnaire record with its status, and later the verification session with its results. See session statuses and webhooks.

Read the quick start, or talk to us about your form.

Questions, answered plainly

What does the first stage collect?

Name, birth date, email, phone and the custom fields that you define.

How does my backend know the first stage is done?

The QUESTIONNAIRE_COMPLETE webhook announces it. The questionnaire record changes from idle to success when the form is filled in and committed.

What does the first stage record?

That the form is complete. The verification is the second stage.

Can I skip the second stage for some users?

That is your decision. Your backend starts the full KYC session only when your rules say so.