How to run a test order through your checkout

Checkout is the one page on your store that earns money, and it’s also the page owners look at least — you don’t buy from yourself, so weeks can pass before anyone notices it’s broken. A checkout can fail quietly, from an expired gateway key or a conflicting plugin update, while the rest of the site looks perfectly healthy; it’s usually the first thing to break on a neglected store. The fix is cheap: buy something from yourself once a month. Here’s the full loop. You’ll need a customer-facing browser, your store admin, and your payment gateway’s dashboard login.

Get your gateway’s test mode and test cards

Every major gateway has a test mode with fake card numbers. Stripe’s classic is 4242 4242 4242 4242 with any future expiry and any CVC; PayPal uses sandbox accounts; Square and Braintree publish their own lists. One big caution: test mode is usually store-wide — flip it on a live store and real customers can’t pay. So use test mode on a staging copy, and on the live store do it the honest way instead: create a 99-cent test product (or a 100%-off coupon on a real one) and pay with your own card. You’ll refund it in a few minutes anyway.

Place the order like a stranger would

Open a private/incognito window so you’re not logged in, not cached, and not carrying an admin’s permissions. Better yet, do it from your phone — that’s where most of your customers are. Find the product through the menu or search, not a bookmarked URL. Add to cart, type a real shipping address by hand, pick a shipping method, pay. Note anything that made you hesitate: a slow page, a confusing field, an error flash. You’re testing the road, not just the destination.

Check the confirmation email arrived

Wait two minutes, then check the inbox you ordered with — and the spam folder. No confirmation email means customers are already wondering if you charged them for nothing, and it usually means all your store’s mail is failing: shipping notices, password resets, the works. If it didn’t arrive or landed in spam, that’s its own fix — make your emails deliver — and it’s a bigger deal than it feels like right now.

Verify the order landed everywhere it should

An order isn’t one record, it’s several, and they can disagree. Check each: the order appears in your store admin with the right total and status; the payment shows in your gateway’s dashboard for the same amount; inventory decremented if you track it; and any downstream system (fulfillment, accounting, email list) picked it up. A store where the gateway got paid but the admin shows nothing has a broken webhook, and that’s worth finding on a 99-cent order instead of a customer’s.

Refund the test and check that too

Refund from your store admin, not the gateway, so you test the integration in both directions. Then confirm the gateway shows the refund, the order status updated, and inventory bounced back. Refunds break in the same quiet ways checkouts do, and the day you need one to work, a customer is already unhappy.

Put it on the calendar

A recurring monthly reminder — first Monday, coffee in hand, ten minutes. Same loop every time: order, email, records, refund. You’ll know it’s working the same way you verify today: a completed order in the admin, a matching payment and refund in the gateway, and a confirmation email in your inbox. Pair it with uptime monitoring and your store has two watchmen: one that checks the site is up, and one that checks it can actually take money — which was the point all along.