Hi Piet!
Since this is a Stripe for WooCommerce issue, would you mind opening a new thread on the Stripe Payments forum? I’m adding the link below so my colleagues can help you further:
https://wordpress.org/support/plugin/woocommerce-gateway-stripe/
I’ll be closing this one, as it’s exclusively for WooCommerce Core issues.
Thank you!
Dear Gabriel ( @gabrielfuentes )
Many thanks for your reply.
This is the plugin we use for Stripe payments:
https://wordpress.org/plugins/woo-stripe-payment/
I contacted the developer of this plugin and he advised that he believes it is a core WooCommerce bug rather than specific to Stripe.
However, I posted the same in the forum you suggested.
Many thanks for your help.
Piet
Hi Piet!
Thanks for confirming which plugin you’re using. I assumed it was the official WooCommerce Stripe one, which is why I pointed you there, so sorry about the mix-up.
I don’t think the answer you got from that plugin’s support team is right though. Looking at the log you shared:
On September 9, 2026, the /feed/ URL returned a 500 error with the following message: Call to undefined function PaymentPlugins\Stripe\is_checkout()
That error comes straight from their plugin (you can see its name there), not from WooCommerce core. An easy way to confirm: deactivate their plugin and leave only WooCommerce core active, and the error goes away.
Their plugin is an extension that adds Stripe features on top of WooCommerce’s core functionality, so it depends on the core to work. If it isn’t compatible with the current version of core, that’s something their developers need to fix on their end. Otherwise every user of that plugin would hit the same error and wouldn’t be able to use it.
I’d go back to them with that and, if you can, ask for a different support rep.
If they still send you back to us (which they shouldn’t), it might be worth looking at a different Stripe plugin instead 🙂
Cheers
Hi @gabrielfuentes
I believe this thread needs some clarification since you’re recommending @beachholiday use a different Stripe plugin.
The communication to @beachholiday was the following:
This looks like an issue on the server where the WooCommerce files were not loaded at some point during a request.
The Payment Plugins team did not communicate that this was a WooCommerce core issue. It’s possible the user’s site has an optimization plugin installed that selectively excludes plugins loading on certain requests where the plugin is deemed to not be needed.
Thanks
