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.

• 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.

1. Log into the IPQS dashboard.
   
   
2. In the navbar on the left, select Fraud Flows.
   
   
3. Click New Flow.
   
   
4. Select the first validation step for your flow. We recommend starting and ending your flow with Form Page steps. Use the first to explain what the user will do, and the last to confirm the verification is complete.
   
   • Form Page
   • Proxy/VPN
   • Device Fingerprint
   • Phone Validation
   • ID Verification
     
     
5. Most validation steps do not require any configuration. However, the Form Page step requires you to design the form.
   1. Click Add Field.
   2. From the Type menu, select the type of field (e.g., "Text Field", "Email Field").
   3. If applicable, enter a name for the field and a placeholder value. For example, you could name an email field "Your email address" and give it a default value of "user@example.com".
      
      
6. To add additional steps to the flow, click Add Step.
   
   
7. You can customize the appearance of your flow by clicking Styles. This menu allows you to select from various default styles, or create your own by entering your own CSS.
   1. Click New
   2. In the Style Name field enter a name for the style.
   3. In the Stylesheet CSS field, enter custom CSS.
   4. Click Save.
      
      
8. When you are finished creating the flow, click Save.

You can also duplicate an existing flow by clicking Clone to the right of a flow.

Click directly on the flow you want to edit.

Click Delete to the right of the flow you want to delete. You will be asked to confirm deletion of the flow. Flows can't be recovered once deleted.

End users complete Fraud Flows in a hosted web experience accessed through a unique link. Generate this link using the /initiate  endpoint, then send it to the user automatically from your system (for example, via email or SMS).

Endpoint

/api/fraud-flows/initiate/{{api_key}}/{{flow_request_id}}

Request parameters

Response parameters

Response example

You can check the status and retrieve the results of a flow using the /status endpoint.

Endpoint

/api/fraud-flows/status/{{api_key}}{{link_request_id}}

Request parameters

Response parameters

Response parameters - Custom forms

For detailed information about response parameters for each flow, see Response Parameters.

Response example - In progress

Response example - Success