How to integrate workflows

Integrate SEON workflows into your web application to create seamless, secure and fully automated identity verification journeys. This guide provides a technical overview for developers on the primary integration methods, from our full-featured Web SDK to API-triggered workflows, and explains how to use webhooks to receive real-time results.

SEON provides flexible integration patterns to fit your existing technology stack and development resources.

The SEON Web SDK is the fastest and easiest way to integrate workflows into your application. It provides a pre-built, customizable user interface that handles the entire verification process.

• Guided document and selfie capture: Instructions and real-time feedback to ensure high-quality image capture.
• Automatic mobile handoff: Seamlessly transfers the session to a mobile device when a camera is unavailable.
• Real-time status updates: Keeps your application informed of the user's progress.

All workflow logic and configuration live in SEON, so you can update your verification flows without changing any code in your application.

When a user starts a verification session on a device without a camera (e.g., a desktop computer), the SEON SDK automatically handles the mobile handoff process to prevent user drop-off.This is enforced by default via the integration as camera quality on desktop computers is limited compared to cell phones, which deliver an easier customer experience and high performance.

1. A QR code is displayed on the desktop screen.

2. The user scans the QR code with their mobile device to transfer the session.

3. The session resumes on the mobile device at the exact step where the user left off.

4. Desktop updates in real-time as the mobile steps are completed, ensuring a seamless experience.

Receive real-time notifications for key workflow events by configuring a webhook endpoint. This allows you to automate downstream actions in your system, such as updating a user's status, triggering an email or initiating a manual review.

Delivery and retry logic

Webhooks are sent immediately when an event occurs.
If your endpoint does not respond with a 200 OK status, SEON will retry up to 5 times with exponential backoff.

You can configure a dedicated webhook endpoint for workflows, separate from the Fraud API.

Payload structure

The webhook payload is a comprehensive JSON object containing the full session context, eliminating the need for follow-up API calls. It includes:

• Session ID and final status
• All data from every node in the workflow path
• Document, selfie and proof of address check results
• Fraud API and device intelligence data
• A timeline of events with timestamps

Security and best practices

• Verify signatures: Always validate the webhook signature to ensure the request is from SEON.
• Use HTTPS: Your webhook endpoint must use a secure HTTPS connection.
• Respond quickly: Acknowledge receipt with a 200 OK status immediately and process the payload asynchronously to avoid timeouts.
• Handle idempotency: Design your webhook handler to prevent duplicate processing in case of retries.