Configure Stripe payment_method_options.card.request_three_d_secure to 'any' versus 'automatic' and understand when each is appropriate

Steps

1. When creating or confirming a PaymentIntent, set payment_method_options.card.request_three_d_secure to 'automatic' to let Stripe and the issuer decide whether a challenge is needed based on risk signals
2. Set the same field to 'any' to always request 3DS regardless of risk, which is required when you want a liability shift on every transaction even when frictionless flow would be allowed
3. Understand that 'any' may increase decline rates if the issuer cannot complete 3DS (e.g., card not enrolled) — Stripe will still attempt the charge in that case
4. Use 'automatic' for typical consumer checkouts where frictionless flow reduces friction; use 'any' for high-value or regulated use cases where liability shift is mandatory
5. Monitor charge.outcome and three_d_secure on resulting Charges to measure authentication rates and adjust the strategy per market
6. Verify against current Stripe docs for the exact enum values and any regional differences in how 'automatic' behaves under PSD2 versus non-EU issuers