#bharattekade-3ds
1 messages · Page 1 of 1 (latest)
@vivid harbor 3D Secure is not guaranteed to actually be needed, so that's normal.
i required OTP popup when customer save card details. how can we do
do you explicitly want to force the customer to complete 3D Secure when setting up their card even if it's not required?
yes
it's important to make sure you understand this. Stripe would consider it a feature, not a bug. The card doesn't always need to be authenticated upfront when saving, it depends on the country and some other factors. If you want to force it you can, but it might lead to some customers giving up.
how can i do if i required
you'd have to use a Radar rule to force it to be required : https://stripe.com/docs/payments/3d-secure#three-ds-radar
You don't need a custom rule to do what you want. You want to turn on the 3DSecure is supported for this card rule on that page
it is already enabled
Then your integration will require the 3DS flow for any and all cards that support it.
If you don't see it with a given card, it's because the card doesn't support 3DS.
actually you need to enable it for SetupIntents
it is showing popup for OTP in test mode