{"id":542,"date":"2026-11-01T07:15:00","date_gmt":"2026-11-01T07:15:00","guid":{"rendered":"https:\/\/paymentsetu.com\/blog\/?p=542"},"modified":"2026-11-01T07:15:00","modified_gmt":"2026-11-01T07:15:00","slug":"woocommerce-orders-stuck-pending-payment","status":"publish","type":"post","link":"https:\/\/paymentsetu.com\/blog\/woocommerce-orders-stuck-pending-payment\/","title":{"rendered":"WooCommerce Pending Payment: Causes and Fixes"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">A woocommerce pending payment order means WooCommerce received the order but has not confirmed payment yet. If the customer says they paid and the order still has not changed, the problem is usually in the payment notification path, plugin configuration, caching, firewall rules or a site conflict.<\/p>\n\n\n\n<aside class=\"ap-card\" aria-label=\"PaymentSetu WooCommerce Plugin\">\n<span class=\"ap-card__badge\">Recommended for WooCommerce<\/span>\n<div class=\"ap-card__body\"><p class=\"ap-card__name\">PaymentSetu WooCommerce Plugin<\/p><p class=\"ap-card__best\">Best for wooCommerce stores that want UPI checkout into their own merchant account without gateway fees<\/p><ul class=\"ap-card__features\"><li>Upload paymentsetu-gateway.zip, enable under WooCommerce &gt; Payments<\/li><li>Customer pays by UPI straight into your merchant account<\/li><li>Webhook marks the order paid after verification<\/li><li>No separate PaymentSetu KYC<\/li><li>No custom API work needed<\/li><\/ul><\/div>\n<div class=\"ap-card__side\"><p class=\"ap-card__price\">Free download <small>Free plugin \u00b7 plans from \u20b9399 \/ 30 days<\/small><\/p><a class=\"ap-card__btn\" href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">Get the WooCommerce plugin \u2192<\/a><\/div>\n<\/aside>\n\n\n\n<p class=\"wp-block-paragraph\">This guide helps you separate an unpaid order from a paid order whose confirmation did not reach your store, then test the full flow safely.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Before you start<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Collect these details before changing settings:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>The order number, current status and time the customer attempted payment.<\/li>\n\n\n<li>The payment method selected at checkout and the exact order total.<\/li>\n\n\n<li>The UPI transaction reference (UTR), amount and timestamp from your own merchant account, if the customer claims payment was successful.<\/li>\n\n\n<li>Access to the WordPress admin area, including WooCommerce logs and the payment plugin settings.<\/li>\n\n\n<li>A staging site or a low-value test product for repeatable testing.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Do not mark an order as paid only because a customer sends a screenshot. Confirm the credit in your own merchant account and match the amount and reference before fulfilling it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What \u201cPending payment\u201d means in WooCommerce<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">WooCommerce uses <strong>Pending payment<\/strong> when an order has been received but payment has not been confirmed. That can be completely normal while a customer is still scanning a QR code, entering payment details or deciding whether to complete checkout. The <a href=\"https:\/\/woocommerce.com\/document\/managing-orders\/order-statuses\/\" target=\"_blank\" rel=\"noopener\">WooCommerce order status documentation<\/a> describes the normal path from Pending payment to Processing after payment is received.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The important distinction is whether money actually reached the merchant account:<\/p>\n\n\n\n<figure class=\"wp-block-table ap-table\"><table><thead><tr><th>What you see<\/th><th>What it usually means<\/th><th>What to check next<\/th><\/tr><\/thead><tbody><tr><td>Pending payment, no matching credit<\/td><td>The order is unpaid, abandoned or the payment was not completed<\/td><td>Ask the customer to use the order\u2019s payment link or try again<\/td><\/tr><tr><td>Pending payment, matching credit exists<\/td><td>Payment confirmation did not complete the notification or verification path<\/td><td>Check order notes, plugin settings, webhook delivery and logs<\/td><\/tr><tr><td>On hold after a payment<\/td><td>The method is waiting for confirmation or manual verification<\/td><td>Follow the method\u2019s confirmation process and review order notes<\/td><\/tr><tr><td>Processing<\/td><td>WooCommerce has recorded payment and the order is ready for fulfilment<\/td><td>Pack or deliver the order; do not wait for Completed automatically<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">For physical products, <strong>Processing<\/strong> generally means paid and awaiting fulfilment. <strong>Completed<\/strong> is a later fulfilment status, so a paid order does not need to jump straight to Completed.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 1: Check the order notes and payment evidence<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why:<\/strong> The order record tells you whether checkout stopped before payment or whether the payment notification stopped after payment.<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Go to <strong>WooCommerce &gt; Orders<\/strong> and open one affected order.<\/li>\n\n\n<li>Note the status, payment method, order total and order time.<\/li>\n\n\n<li>Read the <strong>Order notes<\/strong> panel from the newest entry backwards. Look for a transaction reference, payment initiation message, error, timeout or status change.<\/li>\n\n\n<li>If the customer says they paid, check your own Paytm Business or PhonePe Business merchant account for the matching amount and UTR. Do not rely on the customer\u2019s screenshot as proof.<\/li>\n\n\n<li>Compare the paid amount with the order total. A mismatch should be investigated rather than treated as a successful payment.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If there is no matching credit, the order is probably waiting for customer action. Send the order payment link or ask the customer to retry from the original checkout. If the credit exists but the order has no payment-related note, continue with the notification checks below. WooCommerce also recommends using order notes and logs when a payment does not complete automatically; see its <a href=\"https:\/\/woocommerce.com\/document\/troubleshooting-payment-errors\/\" target=\"_blank\" rel=\"noopener\">payment troubleshooting guide<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 2: Verify the WooCommerce plugin and webhook settings<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why:<\/strong> A correct payment can remain pending when the plugin has the wrong API key, an old webhook URL or a staging URL instead of the live store URL.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For the PaymentSetu WooCommerce plugin:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Download <code>paymentsetu-gateway.zip<\/code> from the <a href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">PaymentSetu WooCommerce plugin page<\/a>.<\/li>\n\n\n<li>In WordPress, open <strong>Plugins &gt; Add New &gt; Upload Plugin<\/strong>, upload the ZIP and activate it.<\/li>\n\n\n<li>Open <strong>WooCommerce &gt; Settings &gt; Payments<\/strong> and enable PaymentSetu.<\/li>\n\n\n<li>Copy the webhook URL shown in the plugin settings. Treat it as an exact value; do not retype or shorten it.<\/li>\n\n\n<li>Create a PaymentSetu API key, add the copied WooCommerce webhook URL, then paste the API key back into the plugin settings.<\/li>\n\n\n<li>Save the settings and confirm that the live site URL, API key and webhook URL belong to the same store. Keep the API key private.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The customer pays by UPI directly into your own merchant account. PaymentSetu verifies the transaction against the order and sends the webhook that lets the plugin update the status. It is a payment verification service, not a payment gateway, and it does not hold the money.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/paymentsetu.com\/blog\/wp-content\/uploads\/2026\/10\/woocommerce-orders-stuck-pending-payment-1.webp\" alt=\"PaymentSetu\u2019s WooCommerce plugin page, where you download the plugin and follow the setup flow.\"\/><figcaption class=\"wp-element-caption\">PaymentSetu\u2019s WooCommerce plugin page, where you download the plugin and follow the setup flow.<\/figcaption><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">After saving, place a controlled test order. A successful test should produce a payment-related order note and move the order out of Pending payment after the payment has been verified.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 3: Remove cache, firewall and endpoint blockers<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why:<\/strong> A webhook is an incoming server request. A page cache, login wall, security challenge or firewall rule can prevent that request from reaching the plugin even when checkout itself loads normally.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Check the following with your host or security administrator:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Exclude the PaymentSetu webhook URL from full-page caching. Do not cache or rewrite its POST requests.<\/li>\n\n\n<li>Allow HTTPS POST requests to the webhook endpoint. Review WAF, CDN and hosting security logs for blocked requests at the time of the test.<\/li>\n\n\n<li>Confirm the live WordPress site is not behind maintenance mode, HTTP Basic Authentication or an IP allowlist that the notification service cannot pass.<\/li>\n\n\n<li>Check that the endpoint is not redirected from HTTPS to HTTP, from the live domain to a staging domain, or through a login page.<\/li>\n\n\n<li>Temporarily relax only the relevant security rule on staging or during a controlled test. Restore the protection after identifying the matching rule.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Success looks like an incoming request reaching WordPress, a verification result appearing in the order notes and the order status changing. A normal homepage response does not prove that the webhook endpoint is reachable, because caching and firewall rules often treat POST requests differently.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 4: Check WordPress cron and queued actions<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why:<\/strong> Some follow-up tasks, cleanup jobs and retry mechanisms use scheduled WordPress or WooCommerce actions. If scheduling is broken, a payment flow can appear incomplete even though the original checkout request worked.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress explains that WP-Cron is triggered by page loads rather than running continuously like a system cron. Check <strong>Tools &gt; Site Health<\/strong> for loopback or scheduled-event warnings, then review <strong>WooCommerce &gt; Status &gt; Scheduled Actions<\/strong> if that screen is available.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Look for actions that are pending for an unusually long time or marked failed around the affected order. Open the action details before retrying it, and record the error rather than repeatedly running every failed action.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If you have WP-CLI access, run this from the WordPress installation directory:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>wp cron test<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Use the result to ask your host to correct loopback requests or configure a server cron if WP-Cron is disabled. The <a href=\"https:\/\/developer.wordpress.org\/plugins\/cron\/\" target=\"_blank\" rel=\"noopener\">WordPress Cron documentation<\/a> explains why low-traffic sites can leave scheduled work waiting until the next page load.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This check complements the webhook check; a direct webhook request should still be allowed to reach the site. Do not assume that repairing WP-Cron will fix an endpoint blocked by a firewall.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 5: Test for a plugin or theme conflict<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why:<\/strong> Checkout customisations, caching extensions, security plugins and themes can alter payment fields, redirects or API responses. WooCommerce lists plugin and theme conflicts as a common source of payment errors.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Run the test on staging where possible:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Update WordPress, WooCommerce, the PaymentSetu plugin and the active theme to compatible versions.<\/li>\n\n\n<li>Keep WooCommerce and PaymentSetu active, then temporarily disable other plugins.<\/li>\n\n\n<li>Use a default WordPress theme for the test so checkout markup and scripts are not customised.<\/li>\n\n\n<li>Place a controlled order, pay the exact amount and watch the order notes.<\/li>\n\n\n<li>If the test works, re-enable plugins one at a time and repeat the test until the conflict returns.<\/li>\n\n\n<li>Restore the working configuration and replace or reconfigure the conflicting extension.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If you cannot use staging, schedule a short maintenance window and notify anyone who could place a real order. Avoid changing production payment settings while customers are actively checking out.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Step 6: Run one complete UPI test from checkout to order status<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Why:<\/strong> Testing each part separately can miss a mismatch between the order amount, dynamic QR, merchant account and webhook payload.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Use this sequence:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>Create or select a low-value test product and confirm the final checkout total.<\/li>\n\n\n<li>Select the PaymentSetu payment method and generate the order\u2019s payment details.<\/li>\n\n\n<li>Pay the exact amount to the connected merchant account from a separate UPI account or device.<\/li>\n\n\n<li>Confirm the credit in your own merchant account and note its UTR.<\/li>\n\n\n<li>Return to <strong>WooCommerce &gt; Orders<\/strong> and review the order notes, plugin logs and status.<\/li>\n\n\n<li>Confirm the order moves to the paid state used by your store, normally <strong>Processing<\/strong> for a physical product.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">If the money is visible in the merchant account but the order remains Pending payment, save the order number, UTR, amount, timestamp, webhook URL and relevant log entries. Those details let you isolate a mapping or delivery problem without asking the customer to pay again.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Do not fulfil an order simply because the browser returned to a thank-you page. The reliable check is a verified credit in your merchant account matched to the intended order.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Stop recurring pending orders with webhook verification<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Manual UPI instructions leave you checking bank notifications and changing order statuses by hand. A webhook-based flow gives WooCommerce a machine-readable payment event instead:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n\n<li>The store creates an order and a dynamic payment request.<\/li>\n\n\n<li>The customer pays directly into the merchant\u2019s own Paytm Business or PhonePe Business account.<\/li>\n\n\n<li>PaymentSetu matches the received UTR and amount to the order.<\/li>\n\n\n<li>PaymentSetu sends a webhook to the WooCommerce plugin after successful verification.<\/li>\n\n\n<li>The plugin records the result and WooCommerce can move the order into its paid workflow.<\/li>\n\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">The <a href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">PaymentSetu WooCommerce plugin<\/a> handles the connection without custom API work. The plugin download is free and works with a PaymentSetu plan; the Starter plan is \u20b9399 per 30 days for 100 verified payments, while Pro is \u20b9999 per 30 days for 1,000 verified payments. PaymentSetu charges 0% commission on the payments; the money goes directly to your own merchant account.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For a store owner, the practical prevention checklist is short: keep the webhook URL exact, keep the API key private, exclude the endpoint from caching and security challenges, review order notes after a test order, and periodically test the complete flow on staging.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">When the flow is ready, <a href=\"https:\/\/paymentsetu.com\/auth\/register\">create a PaymentSetu account<\/a> and connect the merchant account you use for your store.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">What to do with existing stuck orders<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Work through old Pending payment orders one at a time rather than bulk-marking them as paid.<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n\n<li>No matching merchant-account credit: leave the order unpaid, send a payment link or ask the customer to retry.<\/li>\n\n\n<li>Matching credit and a working webhook after the fix: document the UTR and order number, then use the plugin\u2019s supported verification or reconciliation process. If no such action is available in your version, confirm the credit before making any manual WooCommerce status change.<\/li>\n\n\n<li>Unclear or duplicate credit: pause fulfilment and reconcile the amount, UTR, order total and customer details first.<\/li>\n\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">After resolving one order, run a new controlled test. A single corrected status does not prove that the endpoint, caching rules and plugin settings will work for the next checkout.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">FAQ<\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">Why is my WooCommerce order still pending after UPI payment?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">First confirm that the exact amount reached your own merchant account. If it did, inspect the order notes, PaymentSetu API key and webhook URL, then check whether caching, a firewall or a plugin conflict blocked the notification.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">How do I change a WooCommerce order from pending payment to processing?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">Change it only after confirming the payment in your merchant account and matching it to the order. For future orders, fix the notification path so verified payments update the status automatically instead of relying on manual changes.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Can WP-Cron cause WooCommerce payments to stay pending?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">It can delay scheduled follow-up actions or retries, especially on a low-traffic site. Check Site Health and Scheduled Actions, but also test the webhook endpoint separately because a blocked incoming request is a different problem.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Does a customer\u2019s UPI screenshot prove that the WooCommerce order is paid?<\/h3>\n\n\n\n<p class=\"wp-block-paragraph\">No. A screenshot is not confirmation that money reached your merchant account or that the amount matches the order. Verify the credit and UTR, then rely on the payment verification result before fulfilment.<\/p>\n\n\n\n<aside class=\"ap-cta\" aria-label=\"Stop chasing pending orders\"><div class=\"ap-cta__content\"><p class=\"ap-cta__eyebrow\">WooCommerce UPI setup<\/p><p class=\"ap-cta__title\">Stop chasing pending orders<\/p><p class=\"ap-cta__text\">Connect your WooCommerce checkout to direct UPI payment verification with the PaymentSetu plugin.<\/p><\/div><a class=\"ap-cta__btn\" href=\"https:\/\/paymentsetu.com\/woocommerce-plugin\">Get the WooCommerce plugin<\/a><\/aside>\n\n\n\n<p class=\"wp-block-paragraph\">DONE woocommerce-orders-stuck-pending-payment words=2166<\/p>\n\n\n\n<script type=\"application\/ld+json\">{\"@context\": \"https:\/\/schema.org\", \"@type\": \"FAQPage\", \"mainEntity\": [{\"@type\": \"Question\", \"name\": \"Why is my WooCommerce order still pending after UPI payment?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"First confirm that the exact amount reached your own merchant account. If it did, inspect the order notes, PaymentSetu API key and webhook URL, then check whether caching, a firewall or a plugin conflict blocked the notification.\"}}, {\"@type\": \"Question\", \"name\": \"How do I change a WooCommerce order from pending payment to processing?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"Change it only after confirming the payment in your merchant account and matching it to the order. For future orders, fix the notification path so verified payments update the status automatically instead of relying on manual changes.\"}}, {\"@type\": \"Question\", \"name\": \"Can WP-Cron cause WooCommerce payments to stay pending?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"It can delay scheduled follow-up actions or retries, especially on a low-traffic site. Check Site Health and Scheduled Actions, but also test the webhook endpoint separately because a blocked incoming request is a different problem.\"}}, {\"@type\": \"Question\", \"name\": \"Does a customer\u2019s UPI screenshot prove that the WooCommerce order is paid?\", \"acceptedAnswer\": {\"@type\": \"Answer\", \"text\": \"No. A screenshot is not confirmation that money reached your merchant account or that the amount matches the order. Verify the credit and UTR, then rely on the payment verification result before fulfilment. DONE woocommerce-orders-stuck-pending-payment words=2166\"}}]}<\/script>\n\n","protected":false},"excerpt":{"rendered":"Fix a woocommerce pending payment status with a practical checklist for order notes, webhooks, caching, cron, plugin conflicts and UPI verification.","protected":false},"author":1,"featured_media":541,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_singular_sidebar":"","csco_page_header_type":"","csco_page_load_nextpost":"","footnotes":""},"categories":[19],"tags":[113,112,17,28,61],"class_list":["post-542","post","type-post","status-publish","format-standard","has-post-thumbnail","category-woocommerce","tag-payment-troubleshooting","tag-pending-payment","tag-upi-payments","tag-webhooks","tag-woocommerce","cs-entry"],"_links":{"self":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/542","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/comments?post=542"}],"version-history":[{"count":1,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/542\/revisions"}],"predecessor-version":[{"id":737,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/posts\/542\/revisions\/737"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media\/541"}],"wp:attachment":[{"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/media?parent=542"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/categories?post=542"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/paymentsetu.com\/blog\/wp-json\/wp\/v2\/tags?post=542"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}