# 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 Standard, Radar Plus and Radar Pro 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 the 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
The default Radar rules `Block if CVC verification fails` and `Block if postal code verification fails` only apply to SetupIntents when Radar for SetupIntents is enabled — consistent with how all other Radar rules behave.