How to configure fraud rules radar on Stripe

intermediate 8 min read Updated 2026-03-18

Quick Answer

Stripe Radar fraud rules can be configured through the Stripe Dashboard by navigating to the Radar section and creating custom rules based on risk factors like card country, IP address, and transaction patterns. You can set rules to block, allow, or review transactions automatically based on your defined criteria.

Try Stripe Full Stripe Review

Prerequisites

Active Stripe account with payments enabled
Admin access to Stripe Dashboard
Basic understanding of fraud indicators and risk factors
Stripe Radar enabled on your account

Step-by-Step Instructions

Access Stripe Radar in Dashboard

Log into your Stripe Dashboard and navigate to Radar in the left sidebar. Click on Rules to access the fraud rules configuration page. You'll see a list of existing rules and the option to create new ones.

Ensure you have the necessary permissions to modify Radar settings, as this typically requires admin access.

Review Default Machine Learning Rules

Examine the built-in ML-powered rules that Stripe provides by default. These include rules for 3D Secure, CVC verification, and risk score thresholds. You can enable or disable these by toggling the switches next to each rule.

Start with Stripe's default rules before creating custom ones, as they're based on extensive fraud data analysis.

Create a Custom Rule

Click Add rule to create a new custom fraud rule. Choose from rule types: Block (decline payment), Allow (approve payment), or Review (flag for manual review). Enter a descriptive name for your rule in the Rule name field.

Use clear, descriptive names for your rules to make them easy to identify and manage later.

Define Rule Conditions

Set up your rule logic using Stripe's rule builder. Common conditions include:

:ip_country: for IP-based location filtering
:card_country: for card issuing country
:risk_score: for Stripe's machine learning risk assessment
:email_domain: for email domain restrictions

Use operators like is, is_not, is_in, or is_greater_than to define your criteria.

Start with broader rules and gradually refine them based on your fraud patterns and false positive rates.

Set Rule Priority and Testing

Configure the rule priority by dragging it to the appropriate position in your rules list. Higher rules execute first. Enable Test mode to simulate the rule's behavior without affecting live payments. Review the estimated impact shown in the rule preview.

Always test new rules in test mode first to understand their potential impact on legitimate transactions.

Configure Advanced Options

Set up advanced options including rule exceptions for specific customers or situations. Configure time-based conditions if needed, and set up velocity rules to detect rapid-fire transaction attempts. Enable email notifications for rule triggers if desired.

Consider creating exception rules for trusted customers or business partners to avoid blocking legitimate high-value transactions.

Activate and Monitor Rules

Click Add rule to save and activate your configuration. Monitor rule performance in the Radar > Overview section, where you can see metrics like blocked payments, false positives, and accuracy rates. Regularly review and adjust rules based on performance data.

Set up regular reviews of your rule performance to optimize for both fraud prevention and customer experience.

Common Issues & Troubleshooting

Rule is blocking legitimate customers

Check the rule conditions and consider adding exceptions for trusted customer segments. Review the false positive rate in Radar analytics and adjust thresholds or add :is_not conditions for legitimate patterns.

Radar rules not appearing or saving

Verify that Stripe Radar is enabled on your account and you have sufficient permissions. Check that your rule syntax is correct and all required fields are filled. Contact Stripe support if the issue persists.

High false positive rates on new rules

Start with Review actions instead of Block to manually assess flagged transactions. Gradually tighten rule conditions based on actual fraud patterns rather than assumptions.

Rules not triggering as expected

Check rule priority order as higher rules may override lower ones. Verify that rule conditions match the actual transaction data format. Use the Test mode to debug rule logic with sample transactions.

Prices mentioned in this guide are pulled from current plan data and may change. Always verify on the official Stripe website before purchasing.

Visit Stripe View Stripe Pricing