Stripe Radar Blocking Legitimate Payments

How to fix it

Try these in order — the most common fix is first.

1. 1. Find the rule

   Copy steps
   1. Open the payment and look at the Radar outcome, rule and risk level
   2. Check Radar > Rules metrics for estimated false positive rate
   Did this fix it? Yes No

2. 2. Narrow broad rules

   Copy steps
   1. Replace broad rules with ones combined with risk level, e.g. only block when risk_level is elevated
   2. Switch block rules to review rules first to see what you are catching
   Did this fix it? Yes No

3. 3. Test safely

   Copy steps
   1. Use Test rule against 6 months of payments
   2. Set traffic allocation to 0% for shadow mode, then increase gradually
   Did this fix it? Yes No

4. 4. Allow rules

   Copy steps
   1. Allow rules override other rules and require contacting Stripe to enable
   2. Add risk_level != 'highest' to any allow rule
   Did this fix it? Yes No

Symptoms

Real customers are declined with generic errors, sales drop after enabling rules, and payments show as blocked by Radar.

Why it happens

• Default high-risk rules blocking edge cases
• Overly broad custom block rules (for example blocking every non-US card)
• CVC or postal code block rules on wallets or issuers that do not support them
• Account-level risk signals

This guide also covers

• stripe radar blocking legitimate
• stripe radar false positive
• stripe payment blocked
• stripe radar rules

Other Stripe errors

• Stripe Account Under Review: What to Do
• Stripe Payouts Paused or Pending: Why and How to Fix
• Stripe 'Your Card Was Declined' (generic_decline, do_not_honor)
• Stripe authentication_required / 3D Secure Decline
• Stripe Webhook Signature Verification Failed
• Stripe Webhooks Not Firing or Failing (302, 400, 500, Timeout)
• Stripe Dispute Lost: What Happens and Can You Appeal
• Stripe Account Restricted: Verification Information Required