Stripe initialization error – express-checkout.js

Hi @tatof,

Thank you for sharing the details. I understand your concern about seeing the “Stripe initialization data is not available” error appearing on all pages except the cart page after the latest update.

To help us investigate this further, could you please share the following information?

• Your System Status Report from WooCommerce → Status → Get system report.
• Any Stripe-related error logs from WooCommerce → Status → Logs.

You can paste the information into https://pastebin.com/ or https://gist.github.com/ and share the link with us.

Could you also include your site URL in system status report so we can take a closer look at the behavior from our end?

In the meantime, please try the following:

• Clear your site cache and browser cache.
• If you are using any caching or optimization plugins, temporarily disable them and check whether the issue still occurs.

Once we have the requested details, we’ll be able to investigate further and determine whether this is related to the Stripe initialization process or a conflict with another component on the site.

Hi @tatof!

Thank you for providing more information about the issue.

I have reviewed the System Status Report, and everything appears to be fine. I also checked the error log you shared, but it does not seem to be related to the issue you’re experiencing.

Additionally, I tested the no-cache URL and was able to reproduce the issue on my end. Even adding ?nowprocket did not resolve it.

For testing purposes, could you please temporarily deactivate the wprocket plugin, clear any server-side cache, and then check whether the issue still occurs?

I’m suggesting this because another user experienced a similar issue and was able to resolve it by excluding the Shop, Cart, and Checkout pages from caching. For reference, you can review this discussion:
https://wordpress.org/support/topic/express-checkout-error-after-plugin-upgrade/#post-18327750

If that does not help, please create a staging site and perform a conflict test by deactivating all plugins except WooCommerce and WooCommerce Stripe Gateway, and activating a default theme such as Storefront or Twenty Twenty-Five. Then check whether the issue persists.

I’m recommending these steps because we have not been able to reproduce the issue under normal conditions on our end, which suggests there may be a plugin, theme, or caching conflict specific to your site’s environment.