Hosted Flows Scope

Use cases

• Consumer onboarding
  • Traditional: Collects comprehensive information directly from the customer at the initial point of interaction. Customers are typically required to provide extensive personal details, such as name, address, date of birth, identification documents, and sometimes financial information.
  • Progressive: Instead of requiring users to complete all tasks upfront, this method introduces only the necessary steps at the appropriate time—minimizing friction and reducing the risk of abandonment. For example, a customer might initially be asked to provide only basic information to set up their account. Once the account is created, additional steps such as submitting further identification or verifying financial details can be introduced as needed, such as when initiating transactions or engaging in money movement.
  • Advanced Prefill: Prefill onboarding simplifies and expedites account creation by leveraging existing data. Rather than requiring users to manually enter all personal information, this method collects minimal input (e.g., name, email, address, or phone number) and uses an identity verification provider or pre-existing records to automatically populate additional fields. By matching the customer’s information against reliable databases or stored profiles, the system can efficiently complete the necessary details. This approach reduces friction, enhances the user experience, and significantly shortens onboarding time.
• Trust & Safety: Hosted Flows can be configured to handle step-up verification for a variety of trust and safety use cases by seamlessly triggering one-time passcode (OTP) verification, document verification, or selfie reverification before granting access or decisioning a transaction.

Performance characteristics

• Latency: Dependent on workflow steps; optimized for responsive UI rendering.
• Accuracy: Matches underlying RiskOS™ verification services.
• Device coverage: Responsive across mobile, tablet, and desktop.

Limitations

Hosted Flows are designed to be presented to end users in a WebView. Native Android and iOS Hosted Flows are not currently supported.