About Fraud Flows

Rate this article:

X

Select all that apply:

The content is confusing or hard to follow.

There is missing information or code.

There is inaccurate or outdated information.

This page did not solve my problem.

I would like to speak with someone about this.

Email:

Submit Feedback

About Fraud Flows

Fraud Flows is a low-code / no-code way to build a hosted user verification experience using IPQS fraud detection and validation products. Fraud Flows allow you to assemble a “Flow” made up of one or more verification steps, customize the end-user experience, and then send a link to the user to complete the verification.

Fraud Flows are created and managed entirely within the Fraud Flows UI. You can:

• Select the IPQS products you want to run during the Flow.

  • Proxy & VPN Detection API
  • Email Verification API
  • Phone Number Validation API
  • Device Fingerprint API
  • ID Verification

• Add custom form fields to capture end-user input (such as email, phone number, or other application details).

• Customize styling so the verification experience matches your brand.

• Send a Flow link via SMS, email, or place the link anywhere you want (such as in an account recovery page, support workflow, or onboarding process).

Most Fraud Flows Steps run in the background to reduce friction for legitimate users. If you include ID Verification, the user will be prompted to photograph an ID and take a selfie, which will be validated and compared for a match. 

When the user completes the Flow, you can review the results for each Step in your IPQS dashboard or retrieve the results programmatically to make an automated decision in your own systems.

Fraud Flows Use Cases

• Account Recovery Verification: Confirm a user’s risk profile during password reset and recovery workflows before allowing sensitive account changes.

• Customer Support User Verification: Send a verification link during support interactions to validate a user before discussing account details or performing account actions.

• Account Registration & Onboarding: Reduce fake signups by running checks in the background (proxy risk, device signals, email and phone validation) and escalating to stronger verification only when needed.

• High-Risk Account Actions: Add verification Steps before actions like changing a password, updating an email or phone number, enabling 2FA, or updating payout and billing details.

• Identity Verification (KYC-Style Checks): Use ID + selfie verification for workflows that require stronger identity assurance, such as financial access, marketplaces, or regulated user actions.

• Applications & Form-Based Workflows: Build a full application experience directly in Fraud Flows using custom form elements (such as university applications, eligibility checks, or internal approval workflows) without building a separate front-end form system.

• Manual Review & Escalation Paths: Trigger a Fraud Flow link when a user trips internal risk rules, allowing you to collect additional verification signals before approving, denying, or routing to manual review.

• Promotions & Abuse Prevention: Validate users during coupon redemption, free trials, referrals, and other high-abuse events where fraudsters commonly create duplicate or automated submissions.

ID Verification

ID Verification can be added to a Flow when your verification process requires stronger identity assurance. Unlike other types of Steps that can run in the background, ID Verification requires the user to actively participate in the verification process by photographing their ID and taking a selfie.

The submitted ID and selfie are then validated and compared for a match as part of the Flow. This allows you to incorporate identity verification into the same hosted experience as your other Fraud Flows Steps rather than requiring a separate verification process.

ID Verification can be useful for workflows where validating other signals alone is not sufficient, including KYC-style checks, account recovery, onboarding, high-risk account actions, and other situations where you want additional assurance about the identity of the user completing the Flow.

Parts of Fraud Flows

• Flow: A verification process consisting of multiple Steps the user is directed through.

• Step: The individual stages of a Flow, such as Phone Verification and Device Fingerprinting.

• Link: The URL for a specific Flow. There can be multiple links associated with a Flow depending on the delivery method.

• Session: When a user goes to a Link and begins going through the Flow.

• Branch: An automatic redirect from a Flow to a URL or different Flow.

Next Steps

Learn how to create a Flow.