Hi @thecottonshoppe,
I understand how frustrating daily payment failures must be for your business. Let me help you systematically troubleshoot this to identify which gateway might be causing issues.
One thing worth flagging right away: WooPayments is built on Stripe under the hood, so running both WooPayments and the Stripe plugin simultaneously can cause conflicts, including unexpected payment failures. If you’re using WooPayments as your primary gateway, it’s generally recommended to deactivate the standalone Stripe plugin to avoid overlap.
That said, here are the best steps to diagnose what’s happening:
- Go to WooCommerce → Status → Logs and look for entries from
stripe or woocommerce-payments. The error messages there will usually point directly to the cause, whether it’s a card decline, an API authentication issue, or something else entirely.
- Log into your Stripe account and review the failed payment events under Payments → All payments. Each failure includes a decline reason (e.g. “insufficient funds”, “do_not_honor”, “card_velocity_exceeded”) which helps separate card issues from gateway issues
- If you have WooPayments and Stripe both active, try temporarily disabling one to see if failures stop. You can also use the Health Check plugin to test in a conflict-free environment without affecting live customers.
To help us dig deeper, could you share your System Status Report? Go to WooCommerce → Status → Get system report, copy it, paste it at pastebin.com, and share the link here. That will show us your plugin versions, active gateways, and any potential conflicts.
Looking forward to your response so we can narrow this down!
Hi
Thank you for your reply. I have created a copy of my system log at https://pastebin.com/qdpkm0SZ. Kindly review and let me know if you find anything! In the meantime, I will deactivate my payment gateway for stripe and monitor if the situation improves.
Just to clarify, under Woocommerce -> Settings -> Payments -> Stripe, there are options for Express Checkouts (Apple Pay / Google Pay & Link by Stripe). Shouild I deactivate all of these as well?
Hi @thecottonshoppe,
Thanks for sharing the system report and for already taking action on the Stripe plugin. That’s a great first step!
On your question about Apple Pay, Google Pay, and Link:
Yes. Since you’re deactivating the standalone Stripe plugin for testing, those Express Checkout options will go away along with it as they’re all part of the Stripe plugin. You don’t need to disable them separately. WooPayments also has its own Apple Pay and Google Pay support, so your customers will still have those options through WooPayments during the test period.
From your system report:
A couple of things worth keeping an eye on while you monitor: you have the Amelia booking plugin active, which has its own payment processing layer. If any of the failed payments are coming through Amelia’s booking flow rather than the standard WooCommerce checkout, that’s a separate area to investigate. Also, CleanTalk (anti-spam) is active. In rare cases this can interfere with checkout form submissions, so if failures continue after the Stripe change, it’s worth temporarily disabling it as part of conflict testing.
Monitor for a day or two with just WooPayments active and let us know if the failures continue or stop, that’ll tell us a lot.
Looking forward to hearing how it goes!
