How to Test WooCommerce Checkout Without Real Payments

For a WooCommerce store, the most important page isn’t the homepage — it’s the one where someone pays. After an update, “the shop loads” is nowhere near enough. The question is whether a customer can still get from a product to a completed order.

Testing that properly has one obvious problem: you don’t want to charge real cards, send real confirmation emails or reduce real stock. Here is how to check the journey safely.

Why checkout deserves its own check

A checkout depends on WooCommerce, the theme, the payment gateway, shipping and tax rules, and often a handful of extensions. Any of them can change in an update. Some failures are loud, like an error on the checkout page. Others are quiet: a shipping method disappears for one country, a coupon stops applying, or the order confirmation email never sends.

Start with a staging copy

The safest place to test is a staging copy of the store — a private duplicate where orders, emails and stock changes don’t affect real customers. Before using it for tests, it needs a little preparation:

• Outgoing email captured or disabled, so customers never receive test messages.
• Connections to live services — fulfilment, accounting, CRM — paused or pointed at test accounts.
• Payment gateways switched to test mode.

Use the gateway’s test mode

Most payment providers offer a test mode with test keys and published test card numbers. Stripe, for example, documents test cards such as 4242 4242 4242 4242 that behave like real payments without moving money. PayPal offers a sandbox environment for the same purpose.

WooCommerce test card numbers

With the Stripe gateway or WooPayments (which runs on Stripe) in test mode, the same published test cards work. Use any future expiry date and any three-digit CVC:

• 4242 4242 4242 4242 — Visa, the payment succeeds.
• 5555 5555 5555 4444 — Mastercard, the payment succeeds.
• 4000 0000 0000 0002 — the card is declined.
• 4000 0000 0000 9995 — declined for insufficient funds.
• 4000 0027 6000 3184 — always asks for 3D Secure authentication.

Test the failures as well as the happy path. A customer whose card is declined should see a clear message and be able to try again, and the order must not be marked as paid. The 3D Secure card shows whether the authentication step opens and returns to the store correctly, which is where many checkout problems hide.

These numbers only work while the gateway is in test mode; on a live store they are simply declined. PayPal works differently: you pay with sandbox buyer accounts created in the PayPal Developer dashboard. Other gateways publish their own test details in their documentation. And if you only want to test the order flow itself — shipping, tax, coupons and emails — you can enable a manual method such as Cash on delivery on staging and skip the gateway entirely.

What to walk through

1. Find a product and add it to the basket, including a variation if the store uses them.
2. Change the quantity and apply a coupon.
3. Check shipping options and tax for the main countries you sell to.
4. Pay with a test card and reach the order confirmation page.
5. Confirm the order appears in the admin with the right status, and the emails were generated.

After a WooCommerce update it is also worth opening WooCommerce → Status, which lists theme template files that are out of date compared with the new version — a common source of subtle checkout issues. We explain how to handle them in WooCommerce outdated templates.

# List active plugins and whether updates are waiting
$ wp plugin list --status=active --fields=name,version,update

When there is no staging

Not every store has a staging environment. In that case we don’t create recurring real-money orders by default. Instead we agree a safer alternative with the store owner — typically a regular manual walk-through that stops before payment, plus a staging setup as a recommended next step.

For the full update process around these checks, see how to update WooCommerce without breaking checkout.

How often, and how deep

In our WooCommerce maintenance service, a weekly automated purchase-flow check is possible once a safe test environment exists. The exact scope and frequency depend on the store: how many payment methods it uses, how complex shipping is, and which integrations sit behind the order. We agree that during the store review, before care begins — and we are clear that live payments, fraud checks and third-party services remain outside what any test can guarantee.

Frequently asked questions