Electric

[drifting stratus]

The first parameter will request that the issuing bank make the 3DS challenge. The radar rule is an additional layer that helps ensure 3DS authentication is run when creating Payment Methods with Setup Intents.

[subtle sequoia]

does this mean that if I use payment_method_options[card][request_three_d_secure] during SetupIntent creation, and also turn on that radar rule, the user will be 3ds challenged twice when adding a PaymentMethod via a SetupIntent?

My interpretation of all this is:

• first 3ds occurs when the SetupIntent is created
• second 3ds occurs when PaymentMethod is attached

am I understanding this correctly?

[drifting stratus]

No there would be a single 3DS challenge and the result of that would be stored in Stripe

[subtle sequoia]

and if I had the radar rule toggled off, no 3ds challenge would occur in that same scenario above?

[drifting stratus]

If you requested when creating the Setup Intent as we mention here: https://stripe.com/docs/payments/3d-secure#manual-three-ds Stripe will still request 3DS if the card used supports it.

[subtle sequoia]

ok, thank you!

is there any way to confirm that a 3ds challenge occured during a setup intent?

[coral ridge]

👋 Hopping in here!

You can expand the latest_attempt on the Setup Intent (https://stripe.com/docs/api/setup_intents/object#setup_intent_object-latest_attempt) and check payment_method_details.card.three_d_secure (https://stripe.com/docs/api/setup_attempts/object#setup_attempt_object-payment_method_details-card-three_d_secure) for that information