Stripe Radar Is Blocking Legitimate Customers - What Should I Do?

If Stripe Radar is blocking legitimate customers, the answer is to understand why good customers are being caught - not to blindly lower risk thresholds or remove the action responsible. Both moves can raise approvals and fraud. Measure which actions drive declines, false-positive rate, and segment impact before you change anything.

One of the most common challenges I see with merchants using Stripe Radar isn't fraud getting through. It's legitimate customers being blocked.

I've seen this problem with merchants using Radar quite a few times.

A legitimate payment gets blocked. The immediate reaction is usually one of two things:

1. Lower the risk threshold
2. Remove or loosen the action responsible

Both might increase approvals - but they might also increase fraud. That's the problem with looking at the decline rather than the decision behind it.

Radar is powerful - but it doesn't know your business

Stripe Radar is a powerful fraud prevention tool. It combines machine learning with signals such as customer and payment history, device information, and transaction characteristics to assess risk.

Radar doesn't know your business as well as you do.

It doesn't inherently know that a high-value first order is perfectly normal for your customer base, or that international customers make up a large percentage of your legitimate revenue, or that a particular behaviour looks unusual globally but is completely normal for your merchant.

Your own actions can create the same problem

For example, a legitimate customer might ship an order somewhere other than their billing address, make an unusually large first purchase, purchase internationally, retry after an unsuccessful payment, or trigger a velocity or risk rule despite otherwise legitimate behaviour.

Individually, these can be useful fraud signals. But a useful fraud signal isn't automatically a good reason to decline a transaction.

Questions to ask when Radar blocks too many good customers

If Radar is blocking too many legitimate customers, I would start by asking:

• Which actions are generating the most declines?
• What percentage of those declines are false positives?
• Which customer segments are disproportionately affected?
• What happens if we adjust that action or threshold?
• How much additional fraud would we expect to capture or allow as a result?

Sometimes the right answer is changing an action. Sometimes it's moving borderline transactions from block to review or introducing additional verification. Sometimes it's combining several signals instead of making a decision based too heavily on one. Sometimes the existing rule is doing exactly what it should.

The important part is measuring the trade-off before changing it - because neither "Radar blocked it" nor "Radar scored it as risky" tells you whether that was the right decision for your business.

Your fraud tool provides the infrastructure. Your fraud strategy determines how effectively you use it.

If you want help measuring which Radar actions drive false positives on your data, see how it works, pricing, and the FAQ - or book a demo.

Reddit · r/stripe Is blocking legit payments for Stripe a normal thing nowadays? I have been using Stripe for 2 months now and once I started running ads for my store this week I have received 8 high risk payments which got blocked from Stripe. I don't know why this is happening.