Workflows

SEON workflows is a unified identity verification orchestration platform that lets you design, deploy and manage end-to-end user verification journeys all from one place. Instead of integrating multiple products separately, Workflows provides a single, powerful solution to combine identity verification, fraud prevention and AML compliance.

This no-code orchestrator allows you to build and adapt customer journeys quickly, respond to new fraud threats and optimize for conversion without requiring developer resources.

Identity verification in SEON follows a three-stage journey:

1. Build: You create workflow templates in the Workflows page using a visual, drag-and-drop editor. Each workflow defines the verification steps, conditions and routing logic for a specific use case — for example, a KYC onboarding flow for European users or a re-verification flow for high-risk accounts. You can create as many workflows as you need for different jurisdictions, customer segments or business scenarios.
2. Execute: When a user begins a verification session, the workflow runs in real time. Each step in the workflow — data checks, document verification, selfie capture, AML screening — generates its own transaction record. This means every verification step is scored, logged and fully auditable, just like any direct API call.
3. Monitor: Completed and in-progress verification sessions appear in the Transactions page under the Workflow runs tab. From here, you can see every workflow that has been executed, filter by specific workflows or by status (Approved, Declined, Review, Pending, Abandoned), and drill into any session to investigate the full verification journey.

This no-code orchestrator allows you to build and adapt customer journeys quickly, respond to fraud threats and optimize for conversion without requiring developer resources.

Workflows bring together all of SEON's powerful capabilities into a single, orchestrated solution.

Building and deploying an identity verification workflow is a simple, three-step process.

1. Design your flow: Use the visual workflow editor to build verification journeys by dragging and connecting nodes. Each node represents a specific action or check in the verification process. See the building a workflow page for detailed guidance on each node type and how to configure conditions.

2. Define conditions: Use conditional nodes to create intelligent routing logic. Build conditions using data fields from across the SEON platform, including risk scores, document check results and device attributes.

3. Deploy and monitor: Once saved, your workflow is immediately available. Monitor real-time session status, view detailed results for each node and search and filter runs from the Workflow runs tab. See reviewing workflow runs page for a complete guide to investigating verification sessions.

Every step in a workflow generates a transaction in SEON. This is an important architectural concept to understand:

• Each workflow step (data check, document verification, selfie verification, address verification) creates its own transaction record.
• These transactions appear in the Transactions tab, linked to the Workflow run. Their action types reflect the workflow step — for example, workflow_data_check, workflow_document_verification or workflow_selfie_verification.
• All existing signals, rules and scoring apply to each transaction, just as they would with direct Fraud API calls.
• Transactions within a workflow run are connected, allowing you to see the full verification journey from a single session.

This means a workflow with multiple verification steps generates multiple transactions, each with its own fraud assessment. The Transactions page gives you the granular, step-by-step view. The Workflow runs tab gives you the aggregated, session-level view with a single status per user journey. See the reviewing workflow runs page for guidance on when to use each view.

Tip: Transactions created through IDV workflow runs can be added to a blacklist, whitelist or custom list via the Lists API. When creating these entries, you can use values such as the face, ID number, name or address associated with the transaction.

• One SDK for all capabilities: Access the full suite of SEON’s identity verification and fraud prevention tools through a single integration, reducing development time and complexity.
• Visual workflow builder: Design and deploy complex identity verification workflows using an intuitive drag-and-drop editor. No coding required.
• Complete visibility: Track every step of the user journey in real-time from a centralized dashboard, gaining full insight into session status and verification outcomes.
• Flexible decision logic: Route users dynamically based on risk, geography, behavior or any custom data point to balance security and user experience.

Fully score-driven and rule-aware branching

Any signal generated within the platform can be used to drive workflow logic. Fraud scores, state changes, default rules and fully custom rules are all available as branching conditions.

Every workflow step is executed through the Fraud API, ensuring that scores are consistently generated, evaluated, and reused across the entire flow. This enables precise, deterministic decisioning without duplicating logic outside the workflow.

Reusable AML configuration via search profiles

AML checks can be configured once and reused seamlessly across workflows. Existing AML Search Profiles define how an AML check should run, including sources, thresholds, and matching logic.

Within the workflow editor, users simply select the desired search profile, and the AML step automatically follows that configuration. This eliminates reconfiguration, reduces errors, and ensures AML checks remain consistent across workflows and use cases.

Flexible, high-accuracy data sourcing across steps

For checks that require richer input data to achieve maximum accuracy (such as AML or Selfie checks), users have full control over where that data comes from:
Reuse data collected in previous workflow steps (e.g., extracting personal details from an ID check and passing them into AML)

Provide data programmatically at session start, without requiring prior SEON steps

This unlocks powerful use cases:

• AML optimization: Most required AML data can be automatically sourced from an ID verification step, reducing friction and improving match quality.
• Standalone selfie authentication: Customers can perform selfie verification even without prior SEON usage by supplying a reference face image when triggering the session. The newly captured selfie is then compared against that reference, simply by configuring the method in the workflow editor.

Workflows can be configured to handle a wide range of scenarios. Here are a few examples:

The true power of workflows emerges when you combine multiple conditions, verification steps and routing logic into a single flow. Consider a multi-jurisdiction onboarding workflow designed for a company operating across multiple European markets:

Step 1: Pre-screen with data enrichment
The workflow begins with a Data check node that runs email, phone, IP and device intelligence. This happens in the background before the user is asked to provide any documents, allowing you to catch obvious fraud signals early.

Step 2: Device fraud detection
A Condition node checks whether SEON's rules have flagged the user — for example, whether the device has been seen in multiple registrations (a common multi-accounting signal). If a device fraud rule fires, the workflow immediately declines the user without proceeding to document capture, saving verification costs.

Step 3: Country-based routing
For users who pass the pre-screen, a Condition node checks the user's country and routes them to jurisdiction-specific verification paths. Different countries have different regulatory requirements, accepted document types and age thresholds.

Step 4: Country-specific verification
Each country path includes its own Document verification node configured for locally accepted ID types, followed by country-specific conditions. For example:

• A Greece path requires document verification, then checks whether the user's IP country matches Greece, and validates that the user is over 21 (the legal age for certain regulated activities in Greece).
• A Portugal path requires document verification, then checks that the user is over 18, and evaluates the document verification result to route Approved users forward, send Review cases to manual review and decline failures.
• An "else" path for unsupported countries declines the user.

Step 5: AML screening
For users who pass document verification and country-specific checks, an AML node runs sanctions, PEP and adverse media screening using a pre-configured AML Search Profile. The AML check automatically sources the user's personal details — name, date of birth, nationality — from the data extracted during document verification in the previous step, eliminating the need for the user to re-enter information. A Condition node then evaluates the AML result: clear matches proceed to approval, potential matches are routed to manual review and confirmed hits are declined.

Step 6: Final decision
Each branch terminates with an End Workflow node that assigns the appropriate status: Approve, Decline or Review.

This type of workflow allows a single integration to handle complex, multi-market compliance requirements while keeping the user experience as frictionless as possible for each jurisdiction.