We use Woocommerce Stripe Payment Gateway plugin. Stripe.js is enabled and working properly as well as Stripe Radar feature. But there is an important limitation on the plugin.
It’s quite important for us (and I guess for most of the companies/retailers that use it) to manage to set up Stripe Radar “Rules” in order to prevent as many frauds as possible and be notified in most of the common scenarios (we used to do so when using Woocommerce plugin for Braintree).
Your support team told me that it’s important that you should be aware of this feature and hopefully implement it in future updates in the short term 🙂 Looking forward to your reply and hope that the rest of the community see this as a must-have too.
Thanks!
Closed
Last updated: August 15, 2022
Log in to comment on this feature request.
If a payment processed using a wrong CVV, that doesn’t have anything to do with the plugin. I’d recommend you double check your Stripe Radar rules settings. If you’re not using Radar rules, contact Stripe and ask them why the payment processed when an incorrect CVV was entered.
We need this too. I can’t believe that in todays fraudulent online world a simple address and postcode check is not a standard part of this plugin.