Developer Advisory: Stripe API Issues in WooCommerce Stripe Payment Gateway 9.5.0 Developer Advisories

Update:

May 22, 2025: WooCommerce Stripe Payment Gateway 9.5.2 has been released to address this issue. You can update through the WordPress dashboard or download the updated version from WordPress.org.

Details

We are currently investigating an issue where some WooCommerce sites running the WooCommerce Stripe Payment Gateway extension are making too many network requests to Stripe. This is related to the account syncing feature that was updated in version 9.5.0 of the extension.

We’ve temporarily rolled back the stable flag of WooCommerce Stripe Payment Gateway to 9.4.1 to counteract the potential for rate limiting from Stripe’s API. We are working to deploy an update to the extension and will follow up on this post with more details as they become available.

How can I tell if this affects me?

Affected sites are seeing increased admin screen load times and potential timeouts when attempting to interact with Stipe. If you are currently running WooCommerce Stripe Payment Gateway version 9.5, you are at an increased risk of being affected.

If you’re not using the WooCommerce Stripe Payment Gateway plugin but are using WooPayments, there should be no issues with your store and no additional action needed at this time.

What action should I take?

Until a point release is added to WooCommerce Stripe Payment Gateway, we recommend rolling the extension back to version 9.4.1 by manually downloading it from WordPress.org and uploading it via the Add New Plugins screen.

What we are doing

We are working on an update to the extension and collaborating with Stripe to ensure stability going forward. Check back with this post or follow @developwoo on X/Twitter for the most up-to-date information.

14 responses to “Developer Advisory: Stripe API Issues in WooCommerce Stripe Payment Gateway 9.5.0”

Sol

May 19, 2025

So an update at 3am on Saturday (my local time) knocked out my Stripe capability on my Woocommerce store. 9.5.0 also caused false positives in the “you are not connected” message in the woocommerce dashboard.

I manage multiple Woocommerce accounts for clients, all of them are using Stripe and after updating to 9.5.0 I received this message on many of theses websites:

“Your customers cannot use Stripe on checkout, because we couldn’t connect to your account. Please go to your settings and use the Configure Connection button to connect.”

However, when I try to reconfigure the connection, I go through the connection process and it then says:

“We couldn’t connect to your account, it seems like the live API keys we’ve saved for you are no longer valid. Please use the Configure connection button below to reconnect.”

Some of them are successful, but when I try to reconnect certain accounts, it says the account is ineligible as it’s managed by another platform (in this case it was Xero). I understand the Stripe has been purchased by Xero and there are issues if a user has both a Xero account and a Stripe account for the same organisation (Unified accounts). this causes a huge headache trying to solve.

I can’t see any of the API Keys to see what’s going on. In the end I had to create new Stripe accounts causing a lot of downtime.

Thanks for the faulty software. While I appreciate the Stripe plugin is free, there should be better checks in place to prevent such issues.

Reply
1. Brian Coords
  
  May 29, 2025
  
  Hey Sol, We’ve recently released another update to the Stripe Gateway plugin – 9.5.2. Can you test out the latest version and let us know if you’re still seeing issues connecting to Stripe?
  
  Reply
  1. REALTALK
    
    July 26, 2025
    
    NO this is STILL Not loading at all when STRIPE is used with WOO. Did you see/test this yourself? This has stopped working and checkout won’t load on WOO or STRIPE. As of July 26 this issue is NOT RESOLVED.
    
    Reply
    1. Pi
      
      July 28, 2025
      
      Hi there, I’m sorry you are still having trouble with the Stripe plugin. Unfortunately, we haven’t received other reports of folks still struggling after the update.
      
      It’s important that you have the latest version of the WooCommerce Stripe Payment Gateway.
      
      It is also possible that there are additional plugins on your site that could be interfering. A good practice, since your issue persists even after a fix was releases, would be to do a Conflict Test, to determine where the issue might be coming from.
      
      Please let us know what version of WooCommerce and what version of the WooCommerce Stripe Payment Gateway you are running, as well as what you found during the conflict test.
      
      Reply
      1. Natacha
        
        July 30, 2025
        
        This is happening for us also – plugin version 9.7.1
        
        We are migrating to another Stripe plugin because we cannot wait for a solution and the ongoing problems.
      2. REALTALK
        
        July 30, 2025
        
        Yes we did conflict test.
        But the issue is us, we see stripe not working in iOS less than v15.
        Can you post about this or ensure that it’s HIGHLY visible to users.
        
        After we search to see this then we realize we can’t us it in iOS 15 + Stripe don’t work.
        
        thanks!
Assiba

May 19, 2025

Merci ! J’ai passé une heure avec le service d’aide woocommerce sans succès, avec votre solution le message d’erreur a disparu !

Reply
Paul

July 29, 2025

Hello we noticed this problem of slowness while using stripe on our site with the version 10.0.4 of woocommerce what to do please ?

Reply
Natacha

July 30, 2025

The problem is back. Plugin version 9.7.1

We have excessive API Calls to payment_method_configurations causing 429 errors. Then a 500 error.

User eventually sees “There was an error processing your order. Please check for any charges in your payment method and review your order history before placing the order again.”

Reply
REALTALK

July 31, 2025

what version works and tested w/ Stripe, this is a pain. Should really test before releases. thx.

Reply
Pi

July 31, 2025

Hi folks, we’ve noted the uptick in issues and are talking with our internal team to flag this. We’ll reach back out when we have more information.

Reply
Dale du Preez

July 31, 2025

Hi @Natacha, @REALTALK, and @Paul, I am reaching out from the Stripe plugin development team, and we’re really sorry that you’ve had issues after the most recent release. Payment gateways need to “just work”.

Can you share more details with us via our support team at https://woocommerce.com/my-account/contact-support/ or via the support forums at https://wordpress.org/support/plugin/woocommerce-gateway-stripe/ ? We really want to get to the bottom of these issues as quickly as possible, but we haven’t reproduced or witnessed the problems in the last few releases, so we need to help to make sure we get to the bottom of things. If you have concrete steps to reproduce the issue, you are also welcome to file a bug report via our GitHub repo at https://github.com/woocommerce/woocommerce-gateway-stripe/.

Reply
Kevin Hector Fumusa

July 31, 2025

Hi Dale,
i’ll be doing a report of my own, we’ve been using stripe for years now and as we are not the small website with an ftp, it was a shocker to pass dev & stage phases without problems and then crash on production once traffic hit.
Once on production the issue managed to send our customer & subscription platform before on a fixed 504 (gateway timeout), up to it didn’t manage to crash 5-6 c6a.large aws instances.

You can’t be calling your API to check on it every time wordpress is booted up, event when payments are not used. That’s the big issue

Reply
REALTALK

July 31, 2025

Your “developer” response is quite typical of devs who don’t want to do work to fix their own product and leave it to customers may I suggest

Debug tool and use it?
The product isnt working as intended you’ve had an uptick on complaints and say oh send us more info, we sent you info the product doesn’t work – GO TEST YOUR PRODUCT as its intended to insure it works
Stop using AGILE as a reason to release buggy code and not properly testing and then leave it to the end-user to “tell you what’s wrong?” then pay me and I will be a TESTER!
This is not an acceptable response!
Fix your product so people can use it or disable it and stop working on things that don’t work. Why not? Because you need the job, we don’t!
Other tools can work so stop releasing into the market if you don’t know how to release a PCI tool that works for customers

STOP asking customers to “replicate” errors and get a proper debugging tools into play.

The “it works for us” is so bad… and will only hurt your company. Do better.

Reply