D Smith a11n

Hi @kprodoto !

Is it just on that one customer’s order, or on multiple orders from multiple customers? Do you have “Log Debug Messages” enabled within Stripe settings? https://docs.woocommerce.com/document/stripe/#section-2

The logs generated (which will be at WooCommerce > Status, if you click the “Logs” tab and then select the Stripe log from the drop-down) should give more insight into the failure.

If it’s just one customer, it’s likely an issue with that customer’s card. If it’s happening to a lot of customers, it’s worth checking the logs to see the reason for the failures.

Is this only happening with Subscription renewals or with other kinds of purchases as well?

Hi @wajeehahusain!

Can you just do a quick test with the theme switched to Twenty Seventeen and all plugins disabled besides Stripe and WooCommerce core? Just a temporary switch– that’s a crucial diagnostic step to determine the source of the scripting conflict. It may be, as it was for @micke84, an issue with a third-party plugin and theme in combination conflicting with Stripe.

Hi @giuliano61!

In general, please do start a new thread for your issue,

Are you seeing a fatal error with only Jetpack, our Google Analytics plugin, and Stripe plugins enabled and the theme switched to Twenty Seventeen?

Hi there! It is likely due to your account settings, yes.

Because this is a duplicate of , I’m going to close this thread to avoid confusion, but I would try https://www.ads-software.com/plugins/say-what/ and/or the Stripe language packs here: https://translate.www.ads-software.com/projects/wp-plugins/woocommerce-gateway-stripe/language-packs

Hi there!

Switching payment methods (or discontinuing the payment method) will indeed obligate those 50 subscribers to resubscribe; recurring payments won’t auto-switch from SEPA to Stripe if you’re using https://woocommerce.com/products/woocommerce-subscriptions/.

I would contact the Subscriptions plugin devs at https://woocommerce.com/my-account/marketplace-ticket-form/ for best practices as regards switching payment methods; I do think keeping WooCommerce and Stripe up-to-date is important.

Hi there!

I would look here to hook into the conditional for initiating 3DS verification:
https://github.com/woocommerce/woocommerce-gateway-stripe/blob/0f97be2a2838cc0069231ae614e779767bb47f43/includes/class-wc-gateway-stripe.php#L523

In general, that kind of customization is something a contract developer would be able to help you with. I recommend these folks: https://woocommerce.com/customizations/

Hi there!

Before rolling back versions, I would conflict test (as described here) to make sure that the issue is with WooCommerce/Stripe and not another plugin or your theme.

You can get all previous versions of Stripe available here: https://github.com/woocommerce/woocommerce-gateway-stripe/releases

With WooCommerce, I think version 2.6.14 should work with MySQL 5.5: https://github.com/woocommerce/woocommerce/tree/2.6.14

That’s from Feb 2, 2017, so I would look for a Stripe release about that time. But honestly, I would look for a host who offers up-to-date software before I went to the trouble of setting up a deliberately out-of-date site.

Hi @kbraeken!

I’m afraid this does sound like an issue with your third-party events plugin. If you test Bancontact or iDeal checkout with a simple product and the Modern Events Calendar plugin disabled, does it successfully check out?

Hi @andrewsxx! Have you tried the tests specified above, i.e. testing with only Stripe and WooCommerce core plugins active and changing your theme to Twenty Seventeen?

Hi @opryshok!

If you’re seeing this with vanilla Storefront and no plugins active except Stripe and WooCommerce core, can you please ensure that the versions of MySQL and PHP your site is running on are both at least version 5.6 and that your site has valid HTTPS?

Hi Jonas!

That is indeed correct; Stripe uses the Woo fields billing_first_name and billing_last_name.

Thanks @dannyvince!

As far as I’ve seen, this particular error has been in every case a scriping conflict with another plugin or theme code.

@broc93 Did that conflict testing resolve it?

Hi there!

@amylatka, that sounds like a scripting conflict. I recommend you (and other!) try the steps here: https://docs.woocommerce.com/documentation/plugins/woocommerce/troubleshooting/

…especially the Conflict testing. Please let us know the results! I would also make sure that your host has caching disabled on both the cart and checkout, as described here: https://docs.woocommerce.com/document/configuring-caching-plugins/

Please let us know the results! I do suspect this is a scripting conflict.

Hi there!

That class has indeed been deprecated as of a few versions ago to avoid errors– that’s just a notice. I would double-check that all the WooCommerce templates your theme is using are up-to-date. It’s also worth temporarily disabling all plugins except WooCommerce core and switching themes to see if there’s something else (perhaps caching or some code in your child theme’s functions.php?) calling on this deprecated class.