Stripe recommends 3D Secure authentication.
The Payment Intents API itself has the ability to accept 3D Secure payments, but Stripe’s response was that it depends on the plugin implementation to be in a position to perform 3D Secure authentication for payments in the “requires_action” state.
Is there any configuration required to implement 3D Secure?
Best regards.
Translated with DeepL.com (free version)
]]>
No Checkout Form, estou usando a valida??o no campo do telefone. Isso pode causar algum conflito com o plugin?
to sell PDFs and subscriptions on our website https://simplylondonrelocation.com/. However when users use a card that requires 3DSecure, no 3DS authentication request shows in the browser. We have turned off every other plugin on our site and still, the issue remains. Could you please help?
One thing we see in the Chrome console is a “Refused to apply inline style because it violates the following Content Security Policy directive: “style-src ‘self'”. Either the ‘unsafe-inline’ keyword, a hash (‘sha256-1bd1ss83rhoRESXnUSD+xUzVPZzKrKQPYKkWOj5TJIc=’), or a nonce (‘nonce-…’) is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the ‘unsafe-hashes’ keyword is present. “ error message. This seemingly does not come from our own site (we do not have a CSP in place, and when we added one including the hash for tests, the error was still there).
Could you please let us know what might be causing the issue?
Many thanks
Gilda ]]>
as I see here, some users already have the same problem. When paying by credit card, no 3D Secure query appears – so orders are not completed correctly. We are annoying customers and losing a lot of money.
I had already chatted with WooCommerce support. They dismissed it and referred me to Stripe.
Now I was able to do another test in a different browser. In Safari it worked – the above test was under chrome. i also made a short video of the behavior that i can provide.
]]>I’m using your plugin to manage payments on our website.
During the last few days we are experiencing issues with payments that are declined by our customers’ banks due to the transaction not being compliant with PSD2 directives.
Currentily we are running the latest version of WooCommerce, WooCoommerce Subscriptions and WooCoommerce Gateway Stripe.
Stripe support suggested it may be a matter of Stripe API version not being the latest (the plugin uses version 2019-09-09).
Do you have any suggestions?
Regards,
Luca