WooCommerce5 min read· Updated

WooCommerce checkout spinning, returning 500 or declining a payment

A spinning checkout and a declined payment can look identical to a shopper. Follow one test order from the click to the response, then check whether WooCommerce created an order.

Read a failed checkout traceRun a synthetic order failure in your browser. You can try it without a store or a file.
Run the checkout example
On this page

Read a checkout trace

In the worked example, a test shopper presses Place order. The recorded place_order step expects HTTP 200 from /checkout. It receives HTTP 500 after 100 ms. The capture records no order and a failed payment state. That establishes a server error during this attempt. It leaves the responsible extension and the gateway’s own decision unknown.

To check your store, use staging and a payment method in test mode. Use one in-stock item and record the time and time zone, checkout type, shipping choice and expected order state. Check WooCommerce orders and the payment provider’s test dashboard before retrying an uncertain submission.

Choose the observation that matches your test

The checkout keeps spinning
In the browser’s Network panel, find the request started by the click. Classic checkout can use WooCommerce AJAX. The Checkout block uses the Store API. If a request is pending, record the elapsed time. If no request started, look for the first browser error. Neither observation alone tells you whether a payment was declined.
The request returned HTTP 500
Match the time and endpoint to the store’s WooCommerce or PHP error log. Keep the error type and affected component. A request to refresh shipping totals is a different step from submitting the order. Reproduce the same step on staging after one reviewed change.
The gateway declined the test payment
Read the provider’s test result and the order notes. A successful HTTP response can still carry a declined payment. Record the documented decline category and expected order state. Run an approved test payment and a documented decline case separately.

Analyze your own evidence

Open the checkout investigator and choose a supported checkout evidence file or paste its JSON. The evidence guide explains the format. Download the labelled JSON example to see the supported fields. A hand-prepared real report uses the inner WordPress evidence document with its actual collection time and site details. Capture the step, sanitized path, observed and expected HTTP status, duration, and whether an order was created. Leave an unknown value uncollected. Selecting a file leaves it on your device. Select Analyze evidence to read it.

Keep customer details, payment identifiers, cookies, request bodies and raw headers out of the capture. An incomplete trace can support a specific observation while leaving the final order outcome unknown.

Retest and hand the result to support

  1. Repeat the same cart, checkout type, shipping choice and test gateway after one change. Record the new measurement time.
  2. Check the response, order state and provider test result. A disappearing spinner alone cannot confirm an order.
  3. Open the support note in the investigator. Review the expected result, observation, time, limits and next test. Remove private details before copying it.

For checkout-specific request names and log locations, see WooCommerce’s checkout troubleshooting instructions.

Repeat the same check after a reviewed change. Tools that analyze supplied files describe that captured evidence; collect a new snapshot to assess the current site. Review server or DNS changes before applying them to a live site.

Spotted something out of date? Email [email protected].

More guides

Technical SEO5 min read

Crawling versus indexing

Check response directives and discovery, then consult the search engine’s recorded indexing reason.

Email6 min read

Set up email DNS

Separate receiving records from sending authentication and verify every legitimate sender.

Network5 min read

Why a port check says closed

Trace the connection path without disabling the firewall or treating a TCP result as a UDP test.

Redirects7 min read

Fix ERR_TOO_MANY_REDIRECTS

The usual causes are a CDN in Flexible SSL mode, a wrong site address in your CMS or two rules that disagree about www.

Email9 min read

Emails going to spam

Read receiving-server headers, check authentication and alignment, then investigate reputation and recipient signals.

DNS6 min read

DNS change not showing up

Compare authoritative records and resolver caches to investigate a DNS change that has not appeared.

Server config6 min read

Cron job not running

Check paths, environment variables, permissions, logging and time zones in a cron job that is not running.

↑ ↓ moveEnter openEsc close

Expanded view