WooCommerce & Online Payments

WooCommerce Payment Pending: What Staff Should Check First

Review pending orders against the gateway's verified transaction state before delivering work or manually changing payment status.

Man looking at iPhone
Illustrative photograph, not a client or team claim. Photo: NeONBRAND neonbrand via Wikimedia Commons · CC0. Resized and cropped.
In this guide
  1. Understand the recorded state
  2. Look for a missing update
  3. Use a controlled example
  4. Escalate with useful evidence

An order exists, but its status does not show the payment outcome the team expected. The safest first step is reconciliation, not clicking “completed” to make the dashboard look tidy.

Understand the recorded state

Review the order notes, gateway method and safe transaction reference. Check the provider's authorised record for the actual payment state. Approval, authorisation and capture can represent different stages depending on the integration.

Look for a missing update

A customer may have cancelled, the provider may still be processing, or the store may not have received the expected update. Check the supported gateway logs and webhook arrangement without exposing sensitive details. Do not assume a return to the website proves payment was completed.

  • Confirm product, amount, currency and merchant.
  • Distinguish unpaid, authorised and captured states.
  • Review failed delivery of provider notifications.
  • Avoid sending duplicate payment requests prematurely.
  • Keep fulfilment tied to the verified business rules.

Use a controlled example

In a test setup, follow a cancelled checkout and a completed checkout. Compare the resulting order states and notes. This helps staff recognise the supported behaviour of their actual gateway rather than relying on a generic screenshot from another store.

Escalate with useful evidence

Provide the order reference, time and safe error identifiers to the integration maintainer. Never share complete payment credentials in a public enquiry. Resolve the cause before manually forcing statuses across many orders. Order administration should reflect what happened, not substitute for verifying it.

Need help putting this into practice?

Tell Nithu what your website needs and which systems are involved. The next step is a review of the requirements and an agreed scope, with any paid tools or ongoing costs explained before work.

Discuss your WooCommerce project

Further reading from the official documentation