Use Stripe Radar's radar_options to request 3DS authentication on specific transactions based on custom risk criteria

Steps

1. When creating or confirming a PaymentIntent, pass the radar_options parameter with a rules_config or by setting radar_options.session referencing a Stripe.js Radar session token collected from the client
2. Stripe Radar rules can be configured in the Dashboard to trigger 3DS based on attributes such as charge amount, card country, email domain, or custom metadata fields you attach to the PaymentIntent
3. To request 3DS via a Radar rule, create a rule in the Radar Dashboard with the action 'Request 3D Secure'; the rule fires when the PaymentIntent attributes match the conditions you define
4. The PaymentIntent will enter requires_action state when the Radar rule fires 3DS; handle next_action the same way as any other 3DS challenge
5. Monitor your Radar rule hit rates and 3DS completion rates in the Stripe Dashboard to tune thresholds and avoid unnecessarily high challenge rates
6. Combine Radar rules with payment_method_options.card.request_three_d_secure to have both a programmatic override and Radar-driven automation; verify which takes precedence in current Stripe documentation