Skip to main content

Understanding verification flows

Build configurable journeys to get your users verified

Written by Liv Kohlen

The core feature of Vouchsafe is the verification flow.

It is a customisable set of steps that:

  • collects and validates evidence from your end user

  • runs background checks on that evidence and returns a result

You can make as many verification flows as you like for different business purposes.

For example, a financial services firm might have a standard KYC/AML flow, and a separate "enhanced KYC" flow for higher-risk consumers.

The more evidence a flow collects and background checks it does, the more tokens it will use.

How do you build a flow?

  1. Go to the Flows tab of the dashboard and select Create a new flow

  2. Choose a template or select Create your own to start from scratch. You can filter templates by industry, identity profile (M1A or M2C certified), and check type.

  3. Configure your checks - toggle on Identity verification, Address verification and any Enrichments you need

  4. Adjust settings in the Customise, Redirects, Send emails to user and Integrations sections as needed

  5. Select Save changes, then start requesting verifications by email, API or shareable link

What checks can a flow include?

Flows are built around three main blocks:

  • Identity verification - confirms who the user is. You can enable digital ID providers, photo ID acceptance, a video selfie requirement, and referee vouching.

  • Address verification - confirms where the user lives, using trusted data sources. You can optionally accept a supporting document as an additional method.

  • Enrichments - automated background checks that run against verified data. These include Online footprint analysis, Anti money laundering, and Radar, which protects every verification and cannot be disabled.

Always double-check whether there are specific regulatory requirements in your region.

What settings can I edit in a flow?

Each flow has a set of general settings that control how it behaves. These are optional, and sensible defaults have been selected.

Timeout. How many days a user has to complete their verification before it expires and needs to be restarted. Default value is 7 days.


Verify email addresses with OTP. Users must confirm their email with a one-time passcode before starting.

Redirects. URLs to send users to after key outcomes. If left blank, Vouchsafe's default end screens are shown. You can set custom redirects for when a user cancels or fails, when they finish but are still processing (for example, if they are waiting on their referee) and when they are automatically verified.

Send emails to user. You can choose to send Vouchsafe emails to users when they start and complete their verification. You can set a default reason for email invitations.

Webhook URL. Allows you to connect web applications and no-code tools to Vouchsafe. This URL receives a POST request whenever an outcome is decided.

Admin notification email. Sends an email to this address whenever an outcome is decided.

What are certified templates?

Templates are pre-configured flows built around common use cases and regulatory requirements.

When creating a new flow, you can filter templates by industry, identity profile (M1A or M2C certified), and check type. Select one as a starting point, then customise it to suit your needs.

Some templates are certified - these are built to meet the UK digital verification services trust framework and their core settings are locked to protect compliance.

You can add checks on top of a certified template, but you cannot change the locked configuration.

Did this answer your question?