striperadarbillinginvoluntary churnsaas metrics

Stripe Used to Bill Radar Once Per Subscriber. Since October 21, It Bills Once Per Renewal.

Stripe now charges Radar fees on every subscription renewal, on every payment method — not just a customer's first card charge. The math changes by billing cadence.

XY
22 November 2026 · 8 min read

Every Stripe account running Radar has had the same quiet assumption baked into its unit economics: you pay to screen a customer once, at signup, and after that the relationship is free to protect. That assumption stopped being true on October 21, 2026. Stripe's update to Radar's local payment method and Billing coverage didn't change what Radar screens — it was already evaluating every renewal in the background. What changed is that Stripe now sends you a bill for it, on every payment method it supports, not just the one your checkout page defaults to.

Key stat
$0.05
Stripe's starting Radar rate per screened transaction — a fee that, since Oct 21, 2026, can now hit the same subscriber every renewal instead of once
Source: Stripe Pricing (stripe.com/pricing)

What actually changed on October 21

Two separate limits came off at the same time, and it's worth treating them as two different changes even though they landed in the same notice. The first is about payment methods: Radar pricing used to apply only to cards, ACH, and SEPA Direct Debit. Everything else — wallets, bank debits outside those two rails, buy now pay later, stablecoins — got screened for free, by default, because Radar's fraud model runs globally whether or not Stripe is charging you for a given method. The second is about Stripe Billing specifically: Radar pricing used to apply only to the first payment in a subscription. A renewal was screened the same way the first charge was, and it simply never showed up as a line item.

Before Oct 21, 2026After Oct 21, 2026 (or Jan 22, 2027, by notice date)
Payment methods billedCards, ACH, SEPA Direct Debit onlyAll Stripe-supported methods — wallets, bank debits, BNPL, stablecoins included
Subscription events billedFirst payment onlyEvery transaction: renewals, trial conversions, first charge after a payment method change
Custom Radar rulesScoped to the methods you were already screeningApply to all payment methods by default — narrow with payment_method_type to opt a rule back out
Per-transaction rateUnchangedUnchanged — same rate, applied to a much larger set of transactions

Source: Stripe, "Updates to Radar for LPMs and Billing coverage and pricing (October 2026)".

Note what didn't move: your actual per-transaction Radar rate is the same number it was in September. Nobody's screening got more expensive on a per-screen basis. What got more expensive is how many times a single subscriber gets screened over the life of their subscription, and that number was always hiding in your billing cadence, not in anything Stripe just announced.

Why a monthly subscriber now costs 12x more to screen than an annual one

Run the math on what "first payment only" versus "every payment" actually means across a year, and the gap isn't uniform — it's entirely a function of how often a given subscriber renews. An annual plan generates one payment a year whether you're on the old policy or the new one, so nothing changes for it: the first payment was always the only payment, and it still is. A monthly plan generates twelve. Under the old rule, eleven of those twelve renewals were free. Under the new one, all twelve are billed.

Radar-billable events per subscriber per year, before vs. after Oct 21
Monthly billing12x
Quarterly billing4x
Semi-annual billing2x
Annual billing1x (no change)

Calculated from Stripe's Oct 2026 Billing screening policy — multiplier is the increase in Radar-billable events per subscriber per year versus the pre-Oct-21 rule.

That's the part worth sitting with if you're running a low-ARPU, high-frequency consumer product rather than an annual B2B contract. We've written before about how annual subscribers churn at roughly a third the rate of monthly ones — this is a second, unrelated reason annual billing is structurally cheaper to run, stacked on top of the retention advantage rather than caused by it. A $9/month consumer app and a $900/year contract can carry the identical Radar rate per screen and still end the year with wildly different total screening bills, purely because of how many times Stripe touches the card.

The payment methods that just joined the fee schedule

The methods Stripe named as newly in scope are digital wallets, bank debits, buy now pay later, and stablecoins. If your subscription base skews toward any of those — and we've covered several of them as blind spots in their own right, from Klarna renewals to SEPA Direct Debit to wallet-funded checkouts — this is the first time Stripe has priced fraud screening on them the same way it prices a card. Custom Radar rules move with the same scope change: a rule you wrote months ago, assuming it only ever touched card traffic, now evaluates every payment method by default unless you've gone back and added a payment_method_type condition to narrow it. That's worth auditing on its own, separate from the cost question — a rule tuned against card-testing patterns and applied unmodified to a bank debit or a BNPL charge is scoring a transaction type it was never built to understand.

The lever Stripe actually gave you, and the trade-off hiding inside it

Stripe didn't ship this change without an escape hatch. The Dashboard now lets you cap Radar screening at a fixed number of billing cycles per subscription — screen the first three renewals, say, and stop paying for the rest. The first payment on any subscription is always screened regardless of that setting, and the same is true the moment a customer changes their payment method, since that's functionally a new card entering the relationship. Anything Stripe doesn't screen, it doesn't bill for.

The trade-off is the part a lot of teams will skip past on a first read. Capping screening at cycle three doesn't just cap your Radar bill — it caps your fraud visibility at cycle three too. A stolen card that sails through signup clean and only starts generating disputes once the fraudster has settled in for a few renewals is exactly the pattern Radar's ongoing screening exists to catch, and it's also exactly the pattern a cycle cap stops watching for right when it starts to matter. If you're going to use the cap, the right place to set it isn't "whatever keeps the invoice flat" — it's wherever your own dispute data says fraud on a subscription actually tends to surface, which for most subscription businesses is later than three cycles in, not earlier. Our break-even math on a retention offer makes a related point from the other direction: a number that looks like savings on one line of your P&L isn't actually savings if it moves the cost somewhere worse, like unrecovered fraud disputes you'd have caught with the screen you just turned off.

The opt-out window is closing, not open-ended

Stripe will exclude newly covered payment methods from your billing on request, but the window has a hard deadline tied to when your account was notified: October 21, 2026 for accounts notified before October, January 22, 2027 for accounts notified during October. Miss it, and the methods stay in scope indefinitely — there's no second request. Methods Radar was already screening and billing for you before this update, meaning cards, ACH, and SEPA, were never eligible for exclusion in the first place; the opt-out only ever applied to the newly added ones. If any part of your payment mix runs through a method you'd rather keep unscreened and unbilled, this is the one window to make that call, and it isn't indefinite.

None of this changes whether Radar is worth running — fraud screening on a renewal still prevents the exact kind of involuntary churn that never shows up as a decline your dunning stack can react to. What it changes is the arithmetic behind a decision a lot of subscription businesses never had to make before: how much of your margin per renewal is now a fraud-screening line item, and whether that number is still smaller than what an unscreened chargeback would have cost you instead. Run your actual renewal volume and current Radar rate through our gross margin calculator before you touch the cycle-cap setting — and if you're evaluating whether a cancellation flow or a cost control like this one is the better place to protect margin on your lowest-ARPU plans, that's exactly the kind of trade-off CancelFlow is built to help you see clearly instead of guessing at.

Frequently asked questions

Does Stripe charge Radar fees on every subscription renewal now?+

Yes. Before October 21, 2026, Stripe only billed Radar screening on the first payment in a subscription — renewals were screened the same way but never generated a Radar charge. Stripe's October 2026 policy update extended billing to every transaction in a subscription: renewals, trial conversions, and the first charge after a customer updates their payment method, all at your existing per-transaction Radar rate.

Which payment methods does Stripe Radar bill for now?+

All of them. Radar pricing used to apply only to cards, ACH, and SEPA Direct Debit. The October 2026 update extended both screening-based pricing and custom Radar rules to every payment method Stripe supports, including digital wallets, bank debits, buy now, pay later methods, and stablecoins. Local payment methods are charged at the same per-transaction rate as cards.

Can I limit which billing cycles get screened to control the cost?+

Yes. Stripe's Dashboard lets you cap Radar screening to a set number of billing cycles per subscription, so you screen the first few renewals and stop paying for it after that. The first payment on any subscription is always screened, including the first charge after a payment method change, and you're never billed for a cycle Stripe doesn't screen.

Can I opt out of the new payment-method coverage?+

Only within a window, and only for methods you weren't already paying to screen. Stripe will exclude newly covered payment methods on request, but the deadline depends on when your account was notified of the change — October 21, 2026 for accounts notified before October, January 22, 2027 for accounts notified during October. Payment methods Stripe was already billing before the update aren't eligible for exclusion either way.

Try CancelFlow

Stop losing subscribers today

One script tag. One function call. A live cancellation flow in under 10 minutes.

Start free trial →
← All postsHome