# Radar for Setup Intents

By default, Radar doesn’t scan if you set up a Payment Method for future use without a charge. Because of this, Stripe allows for Radar and [Radar for Fraud Teams](https://stripe.com/us/radar/fraud-teams) to be enabled for [SetupIntents](https://stripe.com/docs/api/setup_intents). Request 3DS, Allow Rules, and Block rules can be evaluated against Setup Intents, however Radar for Setup Intents **does not support** Review rules.
### Enable Radar for Setup Intents
To enable Radar for SetupIntents, go to the [Radar settings](https://dashboard.stripe.com/radar/settings) in your Dashboard and toggle **Use Radar on payment methods saved for future use**. This applies Radar rules to payment methods created using the [Setup Intents API](https://stripe.com/docs/payments/setup-intents). **You will be charged per SetupIntent confirmation attempt, including SetupIntents generated by Subscriptions created with** [**non-payment invoices**](https://stripe.com/docs/billing/subscriptions/payment#non-payment)**.**
For more recommendations to optimize your Radar Integration, see our [Radar Optimizations](https://stripe.com/docs/radar/integration#recommendations) documentation.
### Default Radar rules for Setup Intents
Prior to November 2024, the default Radar rules `Block if CVC verification fails` and `Block if postal code verification fails` were evaluated for all Setup Intents, regardless of a user’s Radar settings. This behavior was inconsistent with evaluation of other Radar rules, which are only triggered for Setup Intents if a user had enabled Radar for Setup Intents.
We have rolled out a change that only enforces the default CVC verification and postal code verification block rules when Radar is enabled for Setup Intents.