3D Secure not enforced

Can you please provide more details on how it’s not working? Are you seeing any particular errors? What happens when you try to use the 3D Secure functionality?

The payment simply go through without 3D secure, although the credit cards used normally “trigger” 3D Secure on other websites.
So no error messages or anything, it all happens as if the 3D Secure option was not checked.

There are 4 possible 3DS states.

1. Not Supported – 3DS will not trigger.
2. Recommended – 3DS will trigger.
3. Required – 3DS will trigger.
4. Optional – 3DS will not trigger.

For optional, we don’t force customers to go through 3DS for better conversion rates by default. So perhaps this is what you’re seeing. However you can choose to override that by using hooks. Please see the hooks/filters documentation here https://docs.woocommerce.com/document/stripe/#filter-hooks and look for the hook wc_stripe_require_3ds You can probably use add_filter( 'wc_stripe_require_3ds', '__return_true' ); in your child theme functions.php file. Make sure to backup your site before making any code related changes.

Hi,

I used the filter, thank you.

But If I look at the settings, and hover on the “?” next to 3D Secure checkbox, it is said that the parameter is set on “recommended”… So it all remains a mystery.

Anyway, how can I know it works now ? Does it work on test orders too maybe, with a special card number ?

Thanks,
Camille

Dear support,

Camille is right : there is something tricky.

On the woocommerce stripe gateway backoffice it’s proposed 3D secure with the status “recommended”
I make test on “test mode” but with this card 4000 0000 0000 3089 the system never ask me for 3d secure. Charge sucessed.
It works with 4000 0000 0000 3063. In test mode there is a redirection to the stripe 3D secure test page.

Is the 3d secure only required for transaction under stripe radar ?
How can we test in live mode ?

Best regards.
Jér?me.

@camilleaugey the 4 states of handling as I mentioned above is assuming you have the 3D secure setting enabled. When enabled, it forces even recommended states to go through 3DS. That leaves only optional state which does not go through 3DS. Then you introduce the filter, which also forces optional state to also go through 3DS. I hope that makes sense.

You can test them with these cards https://stripe.com/docs/testing#3ds-cards

We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.