A business believes Radar for Fraud Teams is blocking too many charges. Which of the following actions should they take?

• A. Review any custom Stripe Radar rules which may be blocking charges
• B. Increase the block threshold to allow more charges to succeed
• C. Disable Radar temporarily
• D. Switch to a different payment processor

Answer: (A)

The scenario tests how to reduce false positives in Stripe Radar by tuning your existing setup. Radar makes decisions based on a combination of built-in risk signals and your own custom rules. When too many legitimate charges are being blocked, the best first move is to inspect and adjust those custom rules that are causing the rejections.

By reviewing each rule and its conditions, you can identify why legitimate customers are being blocked, then tweak or disable problematic rules, or refine their criteria. This targeted adjustment preserves fraud protection while improving the approval rate for real orders. It’s a precise fix that addresses the behavior causing the blocking without broad, risky changes.

Loosening the system by increasing the block threshold would reduce the strictness overall and could let more fraud slip through. Disabling Radar temporarily removes protection entirely, which is unsafe. Switching to a different processor shifts the burden but doesn’t solve the underlying misconfigurations and involves extra work.