If you run an online store, there is one failure mode that costs you customers faster than almost anything else: a checkout that charges the customer but tells them the purchase failed. The customer thinks their payment did not go through. They try again. Now they have been charged twice for the same order. They […]
If you run an online store, there is one failure mode that costs you customers faster than almost anything else: a checkout that charges the customer but tells them the purchase failed.
The customer thinks their payment did not go through. They try again. Now they have been charged twice for the same order. They email you confused, frustrated, and wondering if your site can be trusted. You refund them, apologize, and move on, but the damage is already done. And if you do not know what caused it, the same thing will happen to the next customer.
That exact situation is what we recently helped a client resolve. Here is what was happening, how we diagnosed it, and what every business owner should take away from it.
Our client runs a public-facing website that sells tickets to workshops. A customer bought three tickets on her phone and was immediately charged twice on her credit card. She emailed the client asking for a refund, confused and apologetic, as if it were her fault.
When the staff checked the system, both orders had gone through. Two separate charges, two separate order confirmations, twice the cost for the same three tickets. And this was the second time it had happened in recent months. A pattern was forming.
On the surface, it looked like a payment processor bug. Something about the way credit cards were being charged seemed to be going wrong. But payment processors are reliable. Stripe, Square, PayPal, WooPayments — these companies process billions of dollars in transactions and rarely duplicate charges without a reason. Something on the client’s end was causing this.
Our initial thought was that customers on slow mobile connections were tapping the “Place Order” button more than once. The first tap seems unresponsive, they tap again, and the website creates two orders because it could not disable the button fast enough.
That theory fits a lot of real-world duplicate-charge incidents. It was a reasonable starting point. But when we asked the client to walk through a test purchase themselves, something different happened.
The checkout completed. The customer was charged. The ticket was assigned. And then the website showed an error message saying the purchase had failed.
That was the clue that changed everything.
Customers were not tapping twice. The website was telling them their purchases had failed when they had actually succeeded. They were retrying what they thought was a failed transaction. The retry worked cleanly, and now they had been charged twice.
The reason the website was showing false error messages came down to something that happens behind the scenes during every online purchase. When a customer clicks “Place Order,” the website’s checkout system sends a message back to the browser saying “order successful, show the confirmation page.” If anything corrupts that message on its way back, even slightly, the browser cannot understand it and shows a generic error message instead.
In this case, a plugin on the site was throwing small technical warnings during every checkout. Those warnings were getting mixed into the success message and corrupting it. The order itself completed fine on the backend. The charge captured. The ticket was assigned. Only the final “thank you” message to the customer was broken.
This is a subtle enough failure that most site owners would never notice it from their admin dashboard. Every order looks normal in WooCommerce. Payments are successful. Tickets are issued. The only people who see the problem are the customers who received the error message, and many of them assume they did something wrong and quietly give up.
We resolved it in three steps.
First, we installed a small piece of code that prevents those behind-the-scenes warnings from corrupting the customer-facing response. This was the actual fix for the reported symptom.
Second, we deactivated an unused plugin that was the source of one specific warning. The client had installed it for a campaign that never launched and had forgotten about it. An unused plugin was actively breaking checkout.
Third, we added a couple of safety measures as insurance. If anything similar happens in the future, the site now blocks duplicate submissions before they can create duplicate charges.
A follow-up test also surfaced a separate issue: the client’s hosting plan was too small for the volume of work their checkout required, causing a different kind of error. We recommended they upgrade, and once they did, checkouts started completing instantly on the first try.
A few things worth thinking about if you run an online store.
You might have this problem and not know it. The client’s dashboard showed no anomalies. Orders appeared normal. Payments looked successful. The only signal was customer emails, and only the customers frustrated enough to write in actually reported it. For every customer like the one who emailed, there are probably others who just assumed the charge failed and walked away.
Check your customer emails regularly. If you are getting more than one or two “did my payment go through?” messages a year, something may be wrong with how your checkout communicates success to customers. That pattern is worth investigating.
Plugins you forget about can still break things. The plugin causing issues for our client was not being used for anything. It was just installed and forgotten. Every active plugin on a WooCommerce site is code that runs on every page load, including checkout. Auditing your plugin list once a year and removing what you are not using is worth doing.
Hosting matters more than people think. Most small business owners pick a hosting plan based on price and never revisit it, even as their site grows. But the difference between a hosting plan that can handle WooCommerce checkout cleanly and one that cannot is the difference between customers completing their purchase and customers seeing an error page. If your site feels slow, if checkout ever times out, or if you are getting mysterious errors, your hosting is worth reviewing.
Symptoms lie. Root causes tell the truth. The symptom here was duplicate charges. The root cause was a broken confirmation message. A surface-level fix aimed only at blocking duplicate charges would have hidden the problem without solving it, and customers would have still been seeing error messages on successful orders.
We help small businesses figure out what is actually going wrong with their websites, not just what they think is going wrong. If your checkout has been behaving unpredictably, if customers have reported duplicate charges or confusing errors, or if you just want someone to look at your site with fresh eyes, we are happy to take a look.
You must be logged in to post a comment.