Stripe Radar now bills more screened renewals and payment methods — without raising the per-screen rate

Effective October 21, 2026, Stripe expanded billable Radar screening to supported payment methods that had previously been screened without the paid-tier fee and to each screened renewal in a Stripe Billing subscription rather than only its first payment. Stripe's current documentation confirms Radar Standard, Plus and Pro charge per screened transaction across one-off, recurring, invoice and subscription lifecycle payments. Stripe says the per-screen transaction price did not change. Radar Lite remains included at no additional charge for merchants on standard payments pricing.

A SaaS business can face a higher fraud-screening bill without any headline per-unit price rise. A merchant with thousands of subscription renewals or significant digital-wallet and buy-now-pay-later volume should forecast how many previously unbilled screenings are now chargeable. The correct optimisation is not automatically to disable fraud controls: merchants must weigh marginal fees against fraud exposure, disputes and lost revenue.

Stripe's support notice describes paid Radar screening extending beyond cards, ACH and SEPA to all supported payment methods, including digital wallets, additional bank debits, BNPL and eligible stablecoin rails. Stripe Billing renewals beyond the first payment are also in scope. The per-screen rate itself is unchanged, so impact depends on merchant mix and volume.

Stripe's current Radar documentation says the first subscription payment and first payment after a payment-method change are always screened and charged under paid tiers. After that, merchants can configure how many successful renewal cycles are screened; skipped renewals are not charged. A new payment method resets the screening sequence. Teams should confirm exact settings in their Dashboard rather than assume all renewals must always be screened.

The no-additional-charge Radar Lite tier remains included for merchants on standard Payments pricing, with basic card fraud and card-testing protection. The new chargeable-surface description concerns paid Radar Standard, Plus and Pro screenings; avoid conflating the paid-tier expansion with a fee imposed on every Stripe user.

Export paid Radar-screened transaction counts by method and billing cycle, compare against pre-October volume, and multiply additional billable screenings by the account's actual contracted rate. Consider one-off, recurring, failed attempts and payment-method changes. Stripe bills when Radar screens an authorization or charge, not only successful purchases.

Stripe's live documentation establishes present billing semantics, while its support notice and independent small-business reporting establish the October 21 transition. Exact dollar impact depends on account plan, region, custom pricing, transaction mix and renewal settings. A lower screening count can reduce fees but also reduces fraud visibility.