cbennett91

Yes as @agilbert84 said the option to exclude apple pay wasn’t available.

However, it seems to be working as it should again now

I’ll need a bit of clarification to better understand your setup. If your Card, Klarna, and Apple Pay payments aren’t running through the Stripe payment plugin, could you confirm which payment methods are actually enabled under Stripe? THEY ARE RUNNING THROUGH STRIPE. THE ONLY OTHER DIFFERENCE WAS WHEN WE HAD JUST PAYPAL (CARD WAS RUNNING THROUGH PAYPAL BUT NOT ANY MORE)

Also, could you let me know which hosting platform you’re using? I’ve seen a very similar case recently, and I’d like to determine whether this could be related to the server environment, since that other issue also couldn’t be reproduced on staging despite having the same setup. WERE HOSTED THROUGH KINSTA

For reference, I tried replicating the issue on my own test site here: https://moses-testing.mystagingwebsite.com/checkout/, but I wasn’t able to reproduce it, even with multiple gateways active. One difference I did notice is that both of you have PayPal enabled, which I don’t use on my test setup.

As a next step, could you try disabling the PayPal payment plugin, then keep only Stripe active along with an offline option like BACS (so customers still have a choice of payment method), and let me know if the issue continues? I WAS ABLE TO CLICK THE DIFFERENT PAYMENT METHODS AND ENTER DETAILS A LOT LONGER UP UNTIL AROUND 1 MINUTE MARK ON THE VIDEO THEN THE ISSUE STARTED https://www.loom.com/share/c7431749f80e4d3c9783e519e7da70b8?sid=9f371edf-a627-4885-b76f-709ee00b3697

When you respond, please also share your system status report by going to WooCommerce > Status > Get system report > Copy for support so we can review it in more detail. https://gist.github.com/ChrisDSS/a7a2e37d6ea4813df6cce4cf1ee6edcc

Paypal taken off and stripe on – desktop – even worse, card option shows up and i can enter the details fine but unable at all to put customer details in and the klarna option isnt showing. mobile – works fine

have a test your end

• fatal – none
• error
• exception – none
• timeout – none
• stripe
• link
• checkout – the only instance of checkout is the below:
• 2025-09-18T13:24:09+00:00 DEBUG
• ====Stripe Version: 9.9.1====
• ====Stripe Plugin API Version: 2024-06-20====
• ====Start Log====
• Stripe Express Checkout buttons display on product pages is disabled.
• ====End Log====
• and: “is_legacy_checkout_enabled”:”no”,
• ajax – none
• console – none

I’ve pasted the bits ive found on the available searches here: https://gist.github.com/ChrisDSS/8b003bfc91874fe871ee4359d3b56e04

Sorry its probably not much help

the smaller one: https://gist.github.com/ChrisDSS/8f1c52ed23e77b18dde23f1df5765d03

I cant do the big one for some reason it keeps throwing a 500 error on github, is there any other way I can send it to you?

• This reply was modified 8 months, 3 weeks ago by cbennett91.

Theres a big 5mb log https://snipboard.io/EHhkrP.jpg and also a 2mb one from yesterday when i was testing it

Do you want me download them for you to look at?

Hi

Please find answers below

First, test in a different browser and an incognito/private window to rule out browser extensions and local cache, you mentioned you cleared cache but this confirms a client-side factor. Tested in chrome, edge and firefox – all the same issue. Safari on mobile didn’t actually fully crash and could use it but just has a 1/1.5 second delay when changing payment method or entering customer details

Second, check host and CDN caching, object cache and any server-level optimisations, temporarily purge/disable them on the live site and retry. All caches cleared – no difference

Third, confirm only one Stripe integration is active, WooPayments and WooCommerce Stripe can conflict if both are connected, disable WooPayments entirely on the live site while testing. WooPayments fully removed and tested – no different. We only added woo payments after the issue started to try and use that instead but it actually caused the same issue we’re having with Stripe gateway

Fourth, disable Apple Pay / Google Pay and the Link payment option in the Stripe plugin settings since you noted Link caused issues before, and then retest. Apple/Google pay removed – no difference *edit – since removing them and following the next requests, as mentioned below, we’re now able to select the payment methods longer before crashing (also noted on the first console image https://snipboard.io/UauQoD.jpg it stated: unable to download payment manifest which looked like it was to do with google pay (not sure if relevant but thought i’d ask)

Fifth, reproduce the problem and capture the browser console errors and a short Loom video if possible, the earlier screenshot helped a lot so another console capture after disabling the above will be useful. screenshots and video attached (we’re actually able to click the payment methods longer now before the issue starts)

video: https://www.loom.com/share/57bacc01fb3d4b65b7b6e68e8f4dc781?sid=1587c5a1-5f43-448b-b92d-7c42dbc2e5c9

console image: https://snipboard.io/pkclAs.jpg

If the issue continues, please check server error logs and recent changes at the host around the time the problem started, and share the System Status report copy again if you can.

system status: https://gist.github.com/ChrisDSS/00dd25701cc1803ee9fd37fca7a0f788

when in discussion with our server host Kinsta, they asked to see the console so I sent them the original one (https://snipboard.io/UauQoD.jpg) and they asked:

there’s multiple script failures there, indicating an inability to download a payment manifest – if that’s something the rest of the payment transaction relies on, that could definitely be an issue.

Do you know if your Stripe integration requires having our external IP address allow-listed in that particular system of theirs? 🤔

Thanks

That’s strange!

video link: https://www.loom.com/share/7370ff1722b74ad88b056c76d9dd5603