Generating shareable verification links

Updated on 19.02.26
7 minutes to read
Copy link

Overview

You can generate shareable, one-time-use verification links directly from SEON. These links enable you to initiate verification sessions for specific users without requiring them to go through your application’s standard workflow integration.

Shareable verification links are ideal for scenarios such as manual onboarding, re-verification requests, customer support-initiated verifications or internal testing.

 

Use cases

Shareable verification links are ideal for teams that need to initiate verification sessions without a full technical integration. Common use cases include:

  • Manual customer onboarding: Operations teams can send verification links directly to new customers.
  • Re-verification requests: Trigger additional verification for existing users flagged for review.
  • Customer support scenarios: Support agents can generate links during calls or chat sessions.
  • Testing and QA: Quickly test workflow configurations without building test harnesses.

For teams with developer resources who want to automate link generation, SEON also provides a Workflow API for creating verification sessions programmatically.

 

How it works

When you generate a shareable verification link:

  1. A unique session is created tied to a specific workflow and pre-populated with user data you provide.
  2. The link opens a SEON-hosted verification page where the user completes the workflow steps.
  3. The session appears in Workflow runs immediately, allowing you to monitor progress.
  4. Results are delivered via webhooks and visible in SEON once the user completes the flow.

Each link can only be used once. After the user completes or abandons the session, the link becomes invalid.

 

Workflow configuration

Once you select a workflow, the form dynamically displays fields based on the workflow’s configuration. Required fields are marked with an asterisk (*). The required information varies depending on your workflow configuration.

Common fields include:

FieldDescription
User IDA unique identifier for the user in your system
User full nameThe user’s complete name
User date of birthThe user’s date of birth
User email addressEmail address for notifications or matching
User phone numberPhone number for verification or matching

SEON only requests the information necessary for the selected workflow to complete successfully. This ensures you provide exactly what is needed without collecting unnecessary data.

 

Best practices

  • Pre-populate accurate information: Ensure the user information you provide matches what the user will present during verification. Mismatches between pre-populated data and submitted documents or database records may result in failed checks.
  • Communicate expiration to users: When sharing the link, inform users that it expires in one week and can only be used once. This helps prevent confusion if they attempt to access an expired or already-used link.
  • Monitor pending sessions: Regularly review sessions in Pending status to identify links that were generated but never used. Consider following up with users or investigating potential delivery issues.
  • Use descriptive user IDs: When populating the User ID field, use a consistent identifier from your system (such as a customer ID or account number) to easily correlate SEON sessions with your internal records.