Stripe Radar False Positives: Fix Blocked Legit Payments (2026)

Some links in this article are affiliate links. We may earn a commission if you sign up to Whop through our links, at no extra cost to you. Read our affiliate disclosure.

You launch a course, run a flash sale, or open a coaching cohort. Payments come in, then you notice a few legitimate buyers never made it through checkout. That is the Stripe Radar false positives problem, and creators who sell courses, coaching, or paid communities hit it far more than typical online stores.

Radar is a machine-learning fraud filter that scores every Stripe transaction. It is good at catching real fraud, but its model is trained on e-commerce, so high-ticket sales, first-time buyers, and international cards (all normal for creators) read as suspicious. This guide shows how to diagnose your block rate, tune Radar, and decide when to stop tuning altogether.

How Stripe Radar works (risk scores 0 to 100)

Every transaction gets a risk score, and the default block threshold is 75. Radar sits between the customer's checkout action and the actual charge. It scores each payment from 0 to 100 using signals from millions of businesses on the Stripe network:

• Card fingerprint: has this card been used for fraud on other Stripe merchants?
• IP geolocation: does the buyer's IP location match the card's issuing country?
• Device fingerprint: is this a known device or a suspicious browser configuration?
• Velocity: how many transactions has this card or email attempted in a short window?
• Email analysis: is the address disposable, newly created, or tied to past fraud?
• Behavioral signals: did the buyer copy-paste the card number (common with stolen cards)?

By default, Radar blocks scores above 75. Scores between roughly 50 and 75 can go to a review queue (with Radar for Fraud Teams) or pass with a warning flag. Scores below 50 pass normally. This works for typical e-commerce and works poorly for creator purchase patterns.

Why Stripe blocks legitimate payments from creators

Your business breaks four patterns Radar treats as fraud signals, even when every sale is real. Radar's training data skews toward traditional e-commerce, so anything that deviates reads as risk:

• High ticket prices: a $997 course or $2,000 coaching package trips the "unusually high amount" signal that a normal store rarely sees.
• First-time buyers: on a launch, most buyers are new, so Radar has no prior history to trust and scores every signal cold.
• International buyers: a Thai buyer on a US card, or a European on a VPN, mismatches issuing country and IP and trips several signals at once.
• Launch spikes: going from 20 transactions a week to 200 in a day looks exactly like a card-testing attack to the model.

The real cost of false declines

False positives are invisible losses. Unlike chargebacks (which show up with dollar amounts), false declines happen silently: the buyer is turned away, and you never see the attempted payment.

• Customer frustration: a declined legitimate buyer rarely tries again; they assume the problem is their card and move on.
• Cart abandonment: during a launch window, purchase intent is time-sensitive, so a decline now means the sale is gone for good.
• Skewed analytics: false declines make your sales page look like it is underperforming when the real problem is at the payment layer.

How to check your Stripe Radar false positive rate

Stripe does not label false positives, but the block rate is a reliable proxy. In the Stripe Dashboard:

1. Go to Payments.
2. Click Analytics (or Radar in newer dashboards).
3. Read the block rate: the share of attempted transactions Radar blocked.
4. Filter blocked payments by status to see each block, its risk score, and the rule that triggered it.

• 0.5% to 2%: normal for most e-commerce businesses.
• 3% to 8%: common for creator businesses, for the reasons above.
• Above 5%: review blocked transactions manually; you will likely find real buyers.
• Over 80% of your review queue approved: your review rules are triggering too broadly.

If false declines coincide with holds, reserves, or compliance inquiries, our guide to Stripe high-risk classification explains what triggers escalated scrutiny.

Stripe Radar rules tuning: 5 fixes to recover revenue

Custom rules can Block, Review, or Allow a transaction; the fixes below shift borderline creator payments away from Block. Basic custom rules work on the free tier; review queues and advanced attributes require Radar for Fraud Teams ($0.07 per screened transaction).

1. Allow-list your repeat buyers. Add emails and card fingerprints of returning customers so they bypass scoring. On Fraud Teams, automate it: a :customer_purchases: > 1 rule set to Allow trusts any Stripe allow list customer who has bought before. This is the highest-impact change for memberships and communities, where members should never be blocked on renewal.
2. Raise your block threshold to 80 or 85. Write a rule that allows scores below your new threshold. You accept slightly more risk, but for digital products the recovered legitimate revenue far outweighs the incremental fraud. Alternatively, switch the action to Review for scores between 65 and 85 to keep a safety net.
3. Route medium risk through 3D Secure. For scores between 40 and 65, request 3DS instead of blocking. The buyer authenticates (bank app or SMS) and you gain liability-shift protection. This is the exact scenario (high-ticket, new, international) where false positives peak. See our chargeback prevention guide for using 3DS strategically.
4. Enrich transaction metadata. Pass customer name and email (via the Customer object), product type, account age, and prior purchases through payment_intent.metadata. When Radar sees a 30-day-old account with 12 logins, the score drops versus an anonymous card-not-present charge.
5. Review blocked payments weekly. Filter payments by status "Blocked" and look for patterns by country, product, or launch timing. Each pattern is a custom rule waiting to be written: 15 blocked UK cards in a week where you sell to the UK is a clear allow-rule signal.

When to upgrade to Radar for Fraud Teams

At $0.07 per screened transaction, Fraud Teams costs $70 at 1,000 monthly transactions and $700 at 10,000. It adds the tools the free tier lacks:

• Manual review queues: a third action (Review) alongside Block and Allow, so borderline payments get approved instead of auto-declined.
• Advanced rule attributes: customer lifetime value, total purchase count, and time since first purchase.
• Allow and block lists: granular lists for emails, card fingerprints, IPs, and card BINs.
• Risk insights: a breakdown of why a transaction received its score.

Under 500 transactions a month with a block rate below 3%, the free tier is usually enough. Past 500 monthly transactions or a block rate above 5%, the review queue alone recovers more than the $0.07 per transaction costs.

When Radar is not enough: the merchant of record option

Tuning rules, maintaining allow lists, and reviewing blocks weekly is ongoing operational work that competes with your actual business. Merchant of Record (MoR) platforms take the opposite approach: they screen fraud at the platform level, so it is their problem, not yours.

Whop operates as a merchant of record for digital products, courses, communities, and coaching. Its model is trained on creator-economy transactions rather than general e-commerce, so the false positive rate for these categories is structurally lower than what you get tuning Stripe Radar yourself.

• Just 2.7% + $0.30 per transaction. No subscription required. No hidden costs.
• Whop automatically handles and fights disputes on your behalf.
• Whop helps protect from holds and account closures because compliance reviews trigger at predictable revenue milestones.
• Iman Gadzhi made $25M+ on Whop. TJR runs $1M/month. Airrack hits $250K/month.

If Radar flags have compounded into account actions, our guide on Stripe account bans covers what happens next.

What to do next

Stripe Radar false positives are not a bug; they are a general fraud model applied to non-general purchases. The fix is calibration, not abandonment: check your block rate, allow-list repeat buyers, raise the threshold to 80-85, route scores of 40-65 through 3D Secure, enrich metadata, and review blocks weekly.

If that maintenance outweighs the value of your time, a merchant of record like Whop handles fraud prevention at the platform level. Either path works. The wrong choice is ignoring the problem and losing 5-10% of your revenue to an algorithm that does not understand your business.

Frequently asked questions

What is a good false positive rate for Stripe Radar?

Most payment processors consider a false positive rate below 2% acceptable for general e-commerce. For digital product creators (courses, coaching, communities), rates between 3-8% are common because the purchase patterns naturally trigger fraud signals. If your block rate exceeds 5%, you are almost certainly losing legitimate revenue and should review your Radar rules. Check your block rate in the Stripe Dashboard under Payments, then Analytics.

Does Stripe refund me for transactions that Radar blocks incorrectly?

No. Stripe does not charge you for blocked transactions, but it also does not compensate you for the lost revenue. A blocked transaction never processes, so there is no fee and no refund. The cost is entirely in lost sales that you never see. This is why monitoring your block rate matters: you cannot recover revenue from customers who were turned away at checkout and never came back.

What is the difference between Stripe Radar and Radar for Fraud Teams?

Stripe Radar (free) comes with every Stripe account and provides basic machine-learning fraud scoring plus a limited set of default rules. Radar for Fraud Teams costs $0.07 per screened transaction and adds manual review queues, advanced custom rules (using attributes like customer lifetime value and purchase velocity), and allow/block lists. For most creators processing fewer than 500 transactions per month, the free tier is sufficient. Once you scale past that, the $0.07 per transaction is worth it for the additional control.

Can I recover a sale after Stripe Radar blocks it?

Not directly. Once Radar blocks a payment attempt, the customer sees a generic decline message. You can reduce the impact by setting borderline transactions to "review" instead of "block," which holds the payment for your manual approval rather than declining it outright. If you know a blocked customer personally, you can ask them to retry (ideally from the same device and IP) after you have added their email or card fingerprint to your allow list.

Does 3D Secure reduce false positives?

Yes, but with a tradeoff. When you route a flagged transaction through 3D Secure instead of blocking it, the customer gets a chance to authenticate and complete the purchase. If they pass authentication, the transaction processes and you receive fraud liability protection from the issuing bank. The tradeoff is conversion friction: 3D Secure adds a step to checkout, and approximately 10-15% of customers abandon at the authentication screen. Use 3DS selectively for medium-risk transactions rather than applying it globally.

Why do international transactions trigger Stripe Radar more often?

Stripe Radar weighs several signals that international transactions frequently trigger: mismatch between the card-issuing country and the IP address country, use of VPNs (common in countries with internet restrictions), unfamiliar BIN ranges (bank identification numbers), and shipping/billing address inconsistencies. For creators selling globally, these signals generate a disproportionate number of false positives. The fix is to create custom rules that lower the risk weighting for your most common buyer countries rather than relying on Radar defaults.

Last reviewed: 2026-05-22. Stripe Radar features and pricing are current as of 2026. Radar for Fraud Teams costs $0.07 per screened transaction per Stripe's published pricing. False decline revenue impact estimates are based on published industry research, not Stripe disclosures. Nothing here is legal or financial advice. WhatPayment may earn a commission on certain links. Read our affiliate disclosure.