#padek
1 messages · Page 1 of 1 (latest)
The card issuer and your radar rules determine whether a 3DS is needed for a transaction. This isn't an error, but a scenario that your applicaiton need to handle.
https://stripe.com/docs/payments/3d-secure#when-to-use-3d-secure this is how you handle a 3DS
okay creating a setupIntent then creating a paymentMethod but then cofming that setupIntent with payment_method_options = any then using the PM to create a PaymentIntent will be a correct flow and make sure all cards have been authenticated?
A 3DS will still be required even if the same card is authorised successfully before.
In another words, there's no way to avoid 3DS. Your integration should already be ready to handle a 3DS when requested.
okay okay, also if Request 3DS if 3D Secure is required for card rule, is disable will the cards that need that verification are still able to complete a paymentIntent ?
No. If you disable it, the payment that requires 3DS won't be succeeded.
okay thank you il take a closer look and handle the 3DS, thank you for your time