We strongly recommend using Radar to dynamically trigger 3D Secure. Manual 3D Secure is for advanced users integrating Stripe with their own fraud engine.

The simplest way to request 3D Secure is using Radar to dynamically request 3D Secure based on risk level and other requirements. However, you can also request 3D Secure based on logic from your own fraud engine.

To request 3D Secure for one-time payments or future off-session payments, the process is the same. Supply the request_three_d_secure parameter in the card payment_method_options when creating or confirming a PaymentIntent or SetupIntent. When the parameter is provided, Stripe attempts to perform 3D Secure. This overrides any dynamic 3D Secure Radar rules on the PaymentIntent or SetupIntent.

When to provide payment_method_options[card][request_three_d_secure]='any' depends on when your fraud engine detects risk. For example, if your fraud engine only inspects card details, you know whether to request 3D Secure before you create the PaymentIntent or SetupIntent. If your fraud engine inspects both card and transaction details, provide the parameter during confirmation—once you have more information. Then pass the resulting PaymentIntent or SetupIntent to your client to complete the process.

Explore the request_three_d_secure parameter’s usage for each case in the API reference: