A customer says they paid, but your store shows no order. Another order sits in Pending payment for hours. A third shows Failed, and the customer insists their bank approved it. Failed payments are one of the most stressful problems for a store owner, because money, trust and stock are all involved.
This WooCommerce payment failed orders guide shows how to work out what happened, step by step, without guessing. It covers the order statuses, the most common causes, what to check in your gateway and what to send to a developer when you need help. It uses plain language and works for any gateway, with notes on our own CCAvenue plugin where they apply.
| Status | What it usually means |
|---|---|
| Pending payment | Waiting for a result, so check the gateway before you act |
| Failed | The payment was declined or an error stopped it |
| Cancelled | Cancelled by the customer or the store, including after the hold time |
| Processing | Payment received, so the order is ready to be fulfilled |
What a failed order really is
WooCommerce gives each order a status, as the WooCommerce order documentation explains. A Failed order means the payment was declined or an error stopped it. Pending payment means the order was created and is waiting for a result. Cancelled means the order was cancelled by the customer or by the store, including automatically when unpaid time runs out. Each status comes from a message the payment gateway sent back to your store, or from the lack of one.
That last point matters. A missing message is the most confusing case. The customer may have paid, but your store never heard about it. Treat “Pending payment” as “unknown” until you check the gateway.
Why payments fail
Payments fail for five broad reasons, and it helps to sort every failure into one of them.
- The bank said no. The card was declined, the limit was reached or the bank needed extra approval that the customer did not complete.
- The customer left. They closed the page, switched apps or lost signal.
- The gateway said no. The merchant account was not set up for that payment method, the amount or the currency.
- The message did not arrive. The gateway approved the payment but your site did not receive or process the result.
- Your site had a problem. A script error, a timeout or a conflicting plugin broke the flow.
Baymard’s cart research says 10% of shoppers who left a cart gave a declined card as a reason, which is a reminder that declines are common and not always a store fault. Our cart abandonment guide puts the figure in context.
Step 1: Find the order and read the notes
Open the order in WooCommerce and scroll to the order notes on the right. A good payment plugin writes what the gateway returned, often with a reason. Note the time, the status and any reference number. Do not change the status yet.
Step 2: Check the gateway dashboard
Log in to your payment provider and search for the same amount and time, or the order number. Three outcomes are possible. If the dashboard shows a successful payment, the money moved and your store has not recorded it. If it shows a failed or declined payment, the cause is on the bank or customer side. If it shows nothing, the customer never reached the payment step or the request failed before it left your site.
Step 3: Match the two
If the gateway shows a success and WooCommerce shows Pending payment, the result message did not arrive. Common causes are a security plugin or firewall blocking the gateway’s request, a changed site address, a caching rule that interferes with the return page or a slow server. Our plugin keeps order status in line with the gateway result automatically, and it writes debug logs when you turn them on, which helps you see whether the message reached your site.
Step 4: Check the basics on your site
Go through this short list.
- The site address and HTTPS settings are correct, and the certificate is valid.
- The payment plugin is on its latest version and works with your WooCommerce version.
- No security or caching rule blocks the gateway’s return request.
- Your hosting has not hit PHP time limits or memory limits during checkout.
- The merchant ID, access code and working key are the live ones, not the sandbox ones, if you are live.
Read our website maintenance checklist for a wider routine, and our PHP 8.5 guide if you are planning a server upgrade.
Step 5: Decide what to do with the order
If the payment succeeded at the gateway, update the order to the right status, add a note with the reference and tell the customer. If it failed, leave the order as Failed or Cancelled, and give the customer a clear way to try again. Do not ship goods until you see a confirmed success in the gateway. Keep a simple log of each case, with the cause, so you spot patterns.
Two cases that look alike
Duplicate charge. A customer pays twice, often because the first return page looked broken. Check the dashboard for two successful payments, refund one through the gateway’s own process and keep one order. Paid but cancelled. The store cancelled an unpaid order after the hold time, and then the payment arrived late. Review your hold-stock setting and the timing of your automatic cancel rule.
When the problem is the checkout itself
If many failures cluster on mobile, test the journey on a phone. If failures started after an update, test on a staging copy and compare the plugin versions. If you recently switched to the Blocks checkout, confirm your gateway supports it, as we describe in our checkout block guide. For UAE stores, our AED payments guide lists the settings that most often cause currency and region problems. If customers mention approving payments in a bank app, read our guide to UAE online payment authentication.
What to send to a developer
A developer can help faster when you send a complete report. Include the order number and time, the status shown in WooCommerce, what the gateway dashboard shows for the same payment, the WooCommerce, WordPress and plugin versions, and any error shown to the customer. Add the plugin’s debug log lines for that time, with keys and personal data removed. Never email your working key or other secrets.
Habits that prevent most failures
- Update plugins on a staging copy first and test one live-style order.
- Keep a short list of your gateway’s contacts and support steps.
- Check pending orders every day during a sale.
- Use sandbox mode for every change to payment settings.
- Keep your site fast and your certificates valid.
None of these takes long, and together they remove most of the surprises.
Who can help
If failures keep returning and you cannot find the cause, our website maintenance team can trace a payment from the click to the order note. We will tell you what we find and what belongs with your bank or gateway.
A worked example
A store owner sees five Pending payment orders from one afternoon. She opens each order and reads the notes. Two show no gateway response, so she looks in the gateway dashboard and finds one successful payment and one that never started. For the successful one, she checks the amount and reference, updates the order to Processing with a note and emails the customer.
For the order that never started, she leaves it to cancel after the hold time. The other three orders show declined payments with a reason from the bank, so she sends each customer a polite message with a link to try again or pay another way.
The numbers in this example are invented, but the method is real. Read the note, check the gateway, match the two, then act, and write down the cause so you can see patterns over weeks.
Reading patterns over a month
One failed payment tells you little, and fifty tell you a lot. At the end of each month, count failed, cancelled and pending orders and group them by cause: bank declines, customers who left, results that did not arrive and site problems. Look at the trend, not only the total. A rise in missing results after an update points to the update. A rise in declines on one card type points to the bank.
A rise on mobile points to the checkout. Compare the share of failed orders by payment method, by device and by day of the week. Two or three simple charts in a spreadsheet are enough, and they make your conversation with your gateway or developer far shorter.
What to tell customers
Customers who see a failed payment want three things: to know what happened, to know whether they were charged and to know what to do next. Write a template reply that says the order was not completed, that you can see no confirmed payment yet, that any hold on the card is usually released by the bank and that they can try again or choose another method.
Avoid promising refund dates you do not control, and avoid blaming the customer or the bank. Add your order number format and a contact route so they can reply with details.
WooCommerce payment failed: a quick summary
When a WooCommerce payment failed or an order sits in Pending payment, read the order notes, check the gateway dashboard, match the two and only then act. Sort every WooCommerce payment failed case into one of five causes: the bank, the customer, the gateway, a missing result message or your own site. Keep a log of causes, and patterns will appear within a month.
Key takeaways on woocommerce payment failed
- Do not mark an order paid when a WooCommerce payment failed or stayed pending until the gateway confirms it.
Need a CCAvenue gateway for WooCommerce?
TechBella Payment Gateway Pro connects WooCommerce to your own CCAvenue merchant account, with the UAE region, Blocks checkout and compatibility updates. It is an independent plugin, not an official CCAvenue product.
Frequently Asked Questions
Why is my WooCommerce order stuck in Pending payment?
The store has not received a result from the gateway. The customer may have left the payment page, or the result message may have been blocked. Check the gateway dashboard before taking any action.
Should I mark a pending order as paid?
Only after you see a confirmed successful payment in your gateway dashboard. Add the reference in an order note.
Can a plugin cause failed payments?
Yes. An outdated payment plugin, a conflicting plugin or a security rule that blocks the gateway can all cause failures. Test updates on a staging copy first.
What if a customer was charged but has no order?
Find the payment in the gateway dashboard, match it to the order, update the status after you confirm success and contact the customer. If you see two charges, ask the gateway to refund the duplicate.

