Method Signature
Parameters
The ticket identifier that defines the workflow configuration and steps to execute. This ticket is typically generated by your backend system and contains the workflow definition.
Return Value
Returns a Promise that resolves to aFadWeb4Response object containing the workflow results.
The workflow execution results
Event type indicating workflow completion or user cancellation
FadSDK.Constants.EventModule.PROCESS_COMPLETED- Workflow completed successfullyFadSDK.Constants.EventModule.MODULE_CLOSED- User closed the workflow
Usage Example
How It Works
The Fad Web 4 module provides a ticket-based workflow orchestration system:- Ticket Generation: Your backend generates a workflow ticket that defines the steps to execute
- Workflow Execution: The SDK executes each step in the workflow based on the ticket configuration
- Step Coordination: Multiple biometric modules can be chained together (e.g., document capture → liveness detection)
- Result Aggregation: Results from all steps are collected and returned in a unified response
Use Cases
Complete KYC Workflows
Chain document capture, liveness detection, and verification in a single flow
Custom Verification Paths
Configure different verification steps based on user type or risk level
Multi-Step Onboarding
Guide users through complex onboarding processes with multiple validation steps
Compliance Workflows
Ensure regulatory compliance with predefined, auditable verification sequences
Configuration
The workflow configuration is managed server-side through the ticket system. Contact your FAD SDK administrator to:- Define workflow steps and their sequence
- Configure step-specific parameters
- Set validation rules and thresholds
- Customize user interface elements
Notes
The
startFadWeb4() method requires null as the token parameter in the FadSDK constructor, as authentication is handled through the ticket system.