Introducing Fraud Flows: Build Hosted User Verification Workflows with IPQS


Build branded, low-code verification workflows that combine fraud checks, identity verification, and custom user inputs.

IPQS has released Fraud Flows, a low-code and no-code way to build hosted user verification experiences using IPQS fraud detection and validation products.

Fraud Flows lets teams create a verification process made up of one or more steps, customize what users see, and send users a link to complete the process. Teams create and manage Flows in the Fraud Flows UI, giving them a central place to configure verification checks, form fields, styling, and delivery options.

Build Verification Workflows Without a Separate Front End

A Fraud Flow can combine multiple IPQS products within the same hosted verification experience. Available checks include Proxy & VPN Detection, Email Verification, Phone Number Validation, Device Fingerprinting, and ID Verification.

Teams can also add custom form fields to collect information directly from the user, such as an email address, phone number, or other application details. You can customize styling so the verification experience matches the organization's brand.

Once a Flow is ready, you can send its link by SMS or email, or place it wherever verification is needed. Examples include account recovery pages, customer support workflows, and onboarding processes.

Most Fraud Flows steps can run in the background, reducing the amount of interaction required from legitimate users. When ID Verification is included, the user is prompted to photograph an ID and take a selfie. The submitted ID and selfie are validated and compared for a match as part of the Flow.

Review Results or Connect Them to Your Own Systems

After a user completes a Flow, teams can review the results for each step in the IPQS dashboard. Results can also be retrieved programmatically, allowing a business to make automated decisions within its own systems based on the completed verification process.

This structure lets teams combine several verification signals in one hosted experience while still supporting their existing review and decision processes.

Where Fraud Flows Can Be Used

Fraud Flows can support verification at several points in the user lifecycle.

For account recovery, a Flow can confirm a user's risk profile during password reset or recovery before allowing sensitive account changes.

Customer support teams can send a verification link during support interactions before discussing account details or performing account actions.

During account registration and onboarding, Fraud Flows can run checks such as proxy risk, device signals, email validation, and phone validation in the background. You can add stronger verification when needed.

Fraud Flows can also be placed before high-risk account actions such as changing a password, updating an email address or phone number, enabling two-factor authentication, or changing payout and billing details.

For workflows that need stronger identity assurance, ID Verification can combine an ID check with a selfie comparison. The Fraud Flows documentation identifies KYC-style checks, account recovery, onboarding, high-risk account actions, financial access, marketplaces, and regulated user actions as situations where this type of verification may be useful.

Custom form elements also let teams build application- and form-based workflows directly within Fraud Flows. Examples include university applications, eligibility checks, and internal approval workflows.

Fraud Flows can also support manual review and escalation. A Flow link can be triggered when a user meets internal risk rules, so teams can collect additional verification signals before approving, denying, or sending the user for manual review.

For promotions and other abuse-prone events, teams can verify users during coupon redemption, free trials, referrals, and similar activities where duplicate or automated submissions may occur.

Add ID Verification When Stronger Identity Assurance Is Needed

You can add ID Verification to any Flow that requires the user to provide stronger proof of identity. Unlike steps that can run in the background, this step requires active user participation.

The user photographs an ID and takes a selfie. Fraud Flows then validates the submitted ID and compares it with the selfie for a match.

Because ID Verification is part of the same hosted experience as the other Fraud Flows steps, teams can combine identity checks with other verification signals within a single Flow.

Get Started with Fraud Flows

Fraud Flows provides a hosted way to combine IPQS verification products, custom user input, branded styling, ID checks, and result retrieval within a single configurable process.

Teams can create and manage Flows from the Fraud Flows UI, distribute verification links through the channels that fit their workflow, and review completed results in the IPQS dashboard or retrieve them programmatically.

Visit the Fraud Flows documentation to learn how to create your first Flow.

Share this article


Speak with IPQS: (800) 713-2618

Enhance Your Fraud Signals

Start fighting fraud now with 1,000 Free Lookups! or schedule a demo to see how IPQS can enrich fraud scores for IP, email, phone, and device risk across your user journey.