If your WooCommerce payment gateway has stopped working, you're probably watching your cart abandonment rate climb in real time — and that's a horrible feeling. Customers are landing on your site, picking out products, heading to checkout... and then hitting a wall. No payment goes through. Maybe they get a vague error message. Maybe the payment fields just don't show up at all. Either way, they're leaving, and your sales are evaporating.
This isn't just a tech glitch. It's a direct hit to your revenue. Every hour your WooCommerce payment gateway isn't working is another hour of orders that didn't happen. And unlike a broken contact form or a slow-loading page, this one is unmistakable — your store literally cannot do the one thing it exists to do.
The good news is that this kind of problem, while genuinely frustrating, is fixable. Most of the time it comes down to a handful of predictable causes that someone with WooCommerce experience can identify and resolve. Let's break down what's actually happening so you can make sense of it — and figure out what to do next.
What Causes a WooCommerce Payment Gateway Not Working
WooCommerce payment gateway issues almost always trace back to one of a few common culprits. They're rarely mysterious — but they do require someone who knows where to look.
API credentials that are out of date or entered incorrectly. Payment gateways like Stripe, PayPal, Square, and others connect to WooCommerce through API keys — essentially a pair of digital passwords. If those keys have expired, been regenerated on the payment provider's end, or were entered with a typo, transactions will fail. This is one of the most common causes, especially after any account changes on the payment provider's side.
A plugin conflict. WooCommerce runs on WordPress, which means your site is likely running dozens of plugins at once. When one plugin interferes with another — particularly with your payment gateway plugin — things can break without warning. You might have installed a new plugin recently, or a plugin update pushed in the background might have introduced the conflict. If you're curious about how these conflicts play out, WordPress Plugin Conflict: How to Fix It (And What's Really Going On) is worth a read.
An SSL certificate problem. Payment gateways require a secure HTTPS connection to function. If your SSL certificate has expired or is misconfigured, the gateway will refuse to load or process payments as a security measure. Customers may see a browser warning, or the payment fields may simply vanish.
A recent WooCommerce or WordPress update. Updates sometimes introduce compatibility issues between WooCommerce core, your gateway plugin, and your theme. If your payment gateway stopped working right after an update, that's almost certainly why. This is closely related to the broader pattern of things breaking after updates — something covered in detail in Website Broken After Update? Here's What's Going On.
Sandbox/test mode being left on. This one trips up a surprising number of store owners. If your gateway plugin is still set to "test mode," real customer payments will be declined or silently fail. It sounds like a small thing, but it can completely block all transactions.
Firewall or security plugin blocking requests. Some security plugins are aggressive about blocking external connections, and if your firewall is set too tightly, it can prevent the payment gateway from communicating with its servers.
What Fixing a WooCommerce Payment Gateway Actually Involves
Fixing a broken payment gateway isn't usually a single action — it's a process of elimination. Here's a realistic picture of what someone working through this problem is actually doing.
First, they'll check the gateway settings inside WooCommerce — confirming the API keys are current, that test mode is off, and that the gateway is enabled. Then they'll look at recent plugin updates and check for conflicts by temporarily disabling other plugins to see if the gateway starts working. They'll also verify your SSL certificate is valid and that the site is serving over HTTPS consistently.
If those basics don't surface the problem, they'll dig into your site's error logs and the gateway's own transaction logs to find specific error messages. These logs often tell you exactly what went wrong — whether it's a network timeout, an authentication failure, or a code conflict.
From there, the fix might involve regenerating and re-entering API keys, rolling back a plugin update, resolving a plugin conflict, renewing an SSL certificate, or adjusting firewall rules. In some cases, the gateway plugin itself needs to be reinstalled clean.
It's also worth noting that if WooCommerce orders aren't showing up in your admin alongside the payment issue, there may be a deeper backend problem worth investigating at the same time.
Signs This Is Your Issue
Not sure if it's definitely the payment gateway? Here are the telltale signs:
- Customers are reporting that their card gets declined or the payment form doesn't appear at checkout
- You're seeing orders stuck in "Pending Payment" status that never move to "Processing"
- Checkout loads fine but errors out when a customer tries to submit payment
- You received an email from Stripe, PayPal, or your gateway provider about API key changes or account issues
- The problem started right after you updated WooCommerce, WordPress, or a plugin
- Your site recently moved hosts or had its SSL certificate changed
If any of these match your situation, a broken payment gateway is very likely the culprit. You can also check out Payment Not Processing on My Website? Here's What's Going On for a broader look at what goes wrong with online payments.
Should You Try to Fix It Yourself?
This is one of those areas where the risk-to-reward ratio is worth thinking about carefully. Some things — like checking whether test mode is on, or verifying your API keys in the WooCommerce settings — are genuinely simple if you're comfortable poking around your WordPress dashboard.
But anything beyond the basics gets complicated fast. Disabling plugins on a live store can cause other things to break. Touching SSL settings without knowing what you're doing can take your entire site offline. And if you don't have a recent backup, experimenting with gateway settings on a live site is a gamble.
There's also the time cost. If you're spending hours debugging a plugin conflict you've never encountered before, that's hours you're not running your business — and every one of those hours is more lost revenue. If you've already tried the obvious stuff and it's still broken, handing it off is almost always the smarter move.
Common Questions About WooCommerce Payment Gateway Not Working
Why is my WooCommerce payment gateway showing but not processing payments? This usually means the gateway is enabled and loading correctly, but something is breaking the actual transaction — most often an expired or incorrect API key, or a conflict between plugins. Check your gateway's transaction log inside WooCommerce for specific error messages; they often point directly at the cause.
Could a plugin update have broken my payment gateway? Yes, absolutely — this is one of the most common causes. WooCommerce, WordPress core, and gateway plugins all update on their own schedules, and sometimes those updates introduce compatibility issues. If your gateway stopped working right after an update, a plugin conflict or version mismatch is the first thing to investigate.
Why do my WooCommerce payments fail for some customers but not others? This is often a browser or card-specific issue. Some customers may be using outdated browsers that don't support the payment gateway's scripts, or their card issuer may be flagging the transaction. It can also be related to your SSL configuration presenting differently on different devices or networks.
Does test mode affect real customer transactions? Yes — if test mode is enabled in your payment gateway settings, real transactions will not go through. This is a surprisingly common issue, especially for stores that were recently set up or migrated. Head to WooCommerce > Settings > Payments, open your gateway, and confirm test mode is toggled off.
How long does it take to fix a broken WooCommerce payment gateway? In most cases, an experienced developer can diagnose and fix the issue within a few hours. Simple problems like incorrect API keys or test mode being on can be resolved in minutes. More complex issues like plugin conflicts or SSL problems may take a bit longer, but it's rarely an all-day project for someone who knows WooCommerce well.
The Faster Path
If you've read through all of this and the main thing you're thinking is "I just want this fixed without dealing with it myself" — that's a completely reasonable place to land.
Rune is a flat-rate website repair service built for exactly this situation. You describe the problem, we diagnose and fix it — no hourly billing, no retainer, no wondering what the final invoice is going to look like. One flat rate, and your payment gateway gets working again.
For store owners in the middle of a broken checkout situation, speed matters. You can learn more about how the service works at runeintel.com, or if you want to understand what repairs like this typically cost before you commit, How Much Does It Cost to Fix a Website? breaks it down honestly.
The longer your WooCommerce payment gateway sits broken, the more sales quietly slip away. Getting it fixed fast isn't just a convenience — it's the financially smart move.