Skip to main content
web60

Web60 Features

Payment Test Mode Left On: The Staging Push That Took No Money

Graeme Conkie··14 min read
Two teal rounded panels outlined in navy sitting side by side on a shelf line, the right one carrying a small toggle switch, against off-white and warm grey shapes

The gift sets went up on a Saturday morning in late November. Twelve of them, photographed on the studio's own workbench, priced, described and announced with an Instagram post at nine o'clock. By lunchtime the owner had a phone full of likes, three messages saying the card would not go through, and a WooCommerce dashboard showing a handful of orders marked as processing. She packed those first. None of them had been paid for.

This is a composite rather than one shop's story. The business is a small pottery studio in Longford, and every part of what went wrong happens on WordPress shops each winter, on every kind of hosting. Nobody was hacked. No plugin crashed. The owner did the responsible thing, which was to rebuild her Christmas checkout on a staging copy instead of the production site, and then she pushed that copy back with the payment plugin still in test mode.

I want to walk through that weekend properly, because the lesson is not that staging is dangerous. Staging is the right habit. The lesson is that a copy of your shop is still your shop, wired to your real payment account and your real customers, and the switches that make testing safe travel with the copy in both directions.

Why a Copy of Your Shop Is Still Your Shop

A staging environment is a private duplicate of your website. Same theme, same plugins, same products and, crucially, the same database. That database holds far more than pages. Every customer account, every past order, every setting in every plugin and the connection details your payment plugin uses to talk to Stripe or PayPal all live in it.

So the copy arrives fully wired. In the studio's case, the first thing the new staging site could do was take real money from a real card, because the live payment connection came across with everything else. That is why the owner switched the payment plugin into test mode before trying out the new checkout. Sensible. It is exactly what the plugin documentation tells you to do.

Stripe draws the line clearly. Its guide to API keys says that in a sandbox "card networks and payment providers don't process payments" and you cannot accept real payment methods, while live mode is the one that "processes real payments". Test keys and live keys are separate sets, and objects created in one mode are not accessible in the other. The street-level consequence is blunt: whichever mode your production checkout is in decides whether the money from a Saturday launch lands in your bank account or disappears into a simulation.

Where the Test Switch Actually Lives

Most owners imagine test mode as something attached to the staging site itself, like a sign hung on the door. It is not. For most payment plugins it is a setting stored in the database alongside everything else, and the database is precisely what a full push from staging to production carries back.

WooCommerce's documentation for its Stripe extension makes this concrete. Connecting a test account "will automatically put the Stripe plugin into test mode at the end", and getting out again is a matter of "unchecking the test mode box and saving". One box. Ticked on the copy, carried back to production, and nothing on the shop front tells a customer.

Four things travel with a copy of a shop, and each one hurts in a different direction:

What travelsWhere it livesRisk on the staging copyRisk after pushing back
Live payment connectionPayment plugin settingsReal cards can be charged while testingLow, if test mode was never switched on
The test mode switchPayment plugin settingsNone, it is what protects youProduction quietly stops taking money
Scheduled emails and tasksThe database's task queueReal customers get messages from the copyDuplicate or stale messages
The staging labelSite configurationProtects you where plugins respect itProduction behaves like a test site

Each row deserves a closer look.

The Live Connection on a Fresh Copy

Before anyone touches the test switch, a fresh staging copy is a working shop with a different address. Place a quick test order with your own card and it may well be charged for real. Stripe's testing documentation is also plain that its services agreement prohibits testing in live mode with real payment details. A refunded test order is a nuisance. Miss the refund in the month-end reconciliation and it becomes a small accounting mess in January.

The Test Switch Back on Production

This is the Longford weekend. Test mode protected the copy perfectly. Then the full push laid that setting on top of production.

What customers saw depended on how they paid. People typing in card numbers hit errors, because a test-mode checkout cannot accept real cards. A few of them sent messages. Most, as is always the way, simply left and bought a gift somewhere else.

Phone wallets produced something stranger. WooCommerce's Stripe testing guide notes that with Apple Pay in test mode you "simply use your real card information", and that this "will not actually place a charge on your card". So, with that extension at least, the checkout can complete. The customer sees a confirmation, the order sits in WooCommerce looking like any other, and the money never existed. Lost sales hurt. Parcels dispatched for orders nobody paid for hurt twice, because now you are writing awkward emails to customers who believe, quite reasonably, that they already paid you.

The Staging Label

WordPress has had a built-in way to label a copy since version 5.5. The core team's announcement of wp_get_environment_type lists four values (production, local, development and staging), with production as the default, so that plugins can behave differently on a copy.

Some payment plugins honour it. WooPayments documentation says that when a site is marked as development or staging, "payments stay in test mode, even if a real WooPayments account is connected", and it warns owners never to switch that protection off on a copy. Good design. It has a mirror image, though. If that label ends up on production by mistake, the same plugin tells you the store is in development mode and payments are simulated, and you arrive at the Longford weekend by a different road.

Nobody needs to memorise which plugin reads which setting. The point is that this protection depends on the plugin, on the label and on how the copy was made, so none of it can be assumed. Where your hosting panel or plugin supports a staging label, use it. Then verify anyway.

Two overlapping envelope shapes, one solid teal and one off-white with a teal outline, between sweeping teal bands edged in navy
A copy of your database carries its queue of scheduled emails with it, so the copy can write to your customers too.

The Emails Nobody Meant to Send

The payment switch is the expensive mistake. Emails are the embarrassing one.

Your database holds a queue of scheduled jobs: review requests due a few days after delivery, abandoned basket reminders, subscription renewals, the nudge that a gift voucher is about to expire. Copy the database and you copy the queue. The staging site then notices those jobs are due and runs them, from the copy, to your real customers.

In the studio's version of events this happened on the Thursday before launch, while the owner was still building. A batch of review requests went out twice, once from production and once from staging, and the second set linked to the staging address. One regular customer replied to ask whether the site had been hacked. Fair question.

One Careful Plugin Is Not a Quiet Copy

The best-documented guard against this comes from WooCommerce Subscriptions. According to its staging site documentation, it records the site's address when first activated and treats any new address as a staging site. On the copy, renewals switch to manual so no automatic payments are taken, and the plugin "will not send any subscription-related emails".

Read the next line, though: "Any emails sent or managed by WordPress, WooCommerce, or another plugin may still be sent from your staging site." The same page warns that after a migration, "your old site will continue to process real recurring payments" unless you deal with it. One plugin behaving well does not make the whole copy safe. A copy left running is a copy that keeps acting on your behalf.

What a Safe Checkout Test Actually Looks Like

Strip away the plugin names and a safe test of a shop change has five properties. Any setup that meets them, on any host, will do the job:

  1. The copy cannot take real money. Test keys or a sandbox on staging, and never your own card against the live connection.
  2. The copy cannot reach real customers. Outgoing email and scheduled jobs are switched off or captured on staging before you start building.
  3. The copy is labelled as a copy. Where your host or plugin supports a staging label, it is set on the copy and nowhere else.
  4. Only the change goes back. You deploy the pages, products or settings you changed, not a whole database that also carries test settings and a stale order list.
  5. Production is verified after every deploy. Not assumed. Verified.

Point five is the one that would have saved the studio's weekend, and it takes about five minutes.

The Five-Minute Verification After Any Push

  • Open the payment settings on production. Confirm test mode is unticked and the live connection is the one showing.
  • Read the notices. Look on the WooCommerce payments and status screens for anything mentioning test, sandbox or development mode.
  • Match the first real order. When it arrives, find it in your live payment dashboard, not just in WooCommerce. An order in WooCommerce proves someone checked out. Only the live dashboard proves someone paid.
  • Silence the copy. Once you have finished, pause the staging site's scheduled emails or remove the copy entirely, so it stops writing to people.

None of this needs a developer. It needs the habit of treating a push to production as a deployment that gets verified, rather than a save button that gets trusted.

Where Web60 Fits, and Where It Does Not

Consider the alternative first. Without any staging copy at all, the same owner builds the new gift-set checkout directly on production during the week, and the first person to find the half-finished page is a customer trying to buy from it. Staging is still the better habit by a distance, which is why I get irritated by hosts that sell "managed WordPress" and then charge extra for a staging environment, or bury it in a higher tier.

What the Platform Handles

On Web60, one-click staging environments are part of the platform, so the copy lives on the server beside your production site rather than on a laptop or in a forgotten second account. Automatic nightly backups with one-click restore, plus manual on-demand backups, mean you can take a backup immediately before you push and roll back if the push carries across something it should not. That backup layer is the backbone of any WordPress security and backup routine, and it matters most on the day a deployment goes wrong.

Pre-update safety snapshots are taken automatically. If a conflict appears that you cannot untangle, there is an Irish-based support team of real people to look at it, not a ticket queue on another continent.

You also have full WordPress, the same software that runs roughly 38 to 39 percent of all websites according to W3Techs' figures this week, so every payment setting in this article is one you can open and verify yourself. No agency change request at €75 to €150 an hour to find out whether a box is ticked. Staging, backups, SSL and security all sit inside Web60's €60 a year, with no add-on fee for staging, on Irish infrastructure where the data stays in Ireland. If you are starting from nothing, the AI builder will produce a full WordPress site from your own description of the business in under a minute, and you build from there.

What Staging Cannot Do, Ours Included

No staging tool keeps up with production while you test. Orders that arrive on Tuesday exist only on production. Push a whole database from a copy made on Monday and Tuesday's orders, customer accounts and stock levels can be overwritten by Monday's version. That is the deal with any snapshot. Move the change rather than the whole copy, take a manual backup first, and save the big pushes for a quiet hour rather than the morning of a launch.

When a Different Setup Genuinely Suits Better

Fairness matters here. If your shop runs several payment gateways across multiple currencies, with a developer team shipping changes every week, the right answer is a proper deployment pipeline where live keys are supplied per environment and never sit in a database copy at all. Stripe's own key guidance recommends keeping keys in a secrets vault rather than in code or configuration files. Premium managed WordPress providers built around developer workflows genuinely suit that kind of operation better. That is not a pottery studio, and it is not most of the shops I talk to.

A teal rounded square with a thick navy arrow looping around it and pointing back to its centre, on an off-white background
Every push to production ends with one step: verify the shop can take real money.

What to Take Into Your Next Launch

Testing on a copy was the right call in Longford, and it is the right call for any shop changing its checkout before Christmas. The copy simply needs to be treated as what it is: a full working version of your business, with its own line to your customers and your payment account.

The habit to add is a small one. After every push, open the payment settings, read the notices, and match the first real order against your live payment dashboard. Do that, and the nine o'clock launch post is selling something you will actually be paid for.

Frequently Asked Questions

How do I know if my WooCommerce shop is in test mode?

Open WooCommerce, then Settings, then Payments, and open each payment method you use. With the WooCommerce Stripe extension, look for the Enable test mode option and confirm it is unticked. With WooPayments, look for test account indicators on the payments screens and for a notice saying the store is in development mode and payments are simulated. The most reliable check is the first real order: if it appears in WooCommerce but not in your live payment dashboard, stop and investigate before you dispatch it.

Can I test my checkout on a staging site without charging real cards?

Yes. Put the payment plugin on the staging copy into test or sandbox mode and use the test card numbers your payment provider publishes. In a Stripe sandbox, card networks do not process payments, so nothing is charged. Do not test with your own real card against the live connection, because Stripe's terms prohibit testing in live mode with real payment details. Just remember to verify that production is back in live mode after any push.

Why are customers getting emails from my staging site?

A staging copy includes your database, and the database holds the queue of scheduled jobs such as review requests, abandoned basket reminders and renewal notices. When the copy runs, it can work through that queue and email real customers. Some plugins, such as WooCommerce Subscriptions, detect a staging copy and stop their own emails, but other plugins may still send. Switch off or capture outgoing email on the copy before you start, and remove the copy when you are finished.

Should I push my whole staging site to production?

Usually not for a shop. A full push replaces production's database with the copy's, which can carry test mode settings back and overwrite any orders, customer accounts or stock changes made on production while you were testing. Move only what you changed where you can, take a manual backup immediately beforehand so you can roll back, and verify the payment settings straight after the push.

Sources

Graeme Conkie
Graeme ConkieFounder & Managing Director, Web60

Graeme Conkie founded SmartHost in 2020 and has spent years building hosting infrastructure for Irish businesses. He created Web60 after seeing the same problem repeatedly — Irish SMEs paying too much for hosting that underdelivers. He writes about WordPress infrastructure, server security, developer workflows, managed hosting strategy, and the real cost of hosting decisions for Irish business owners.

More by Graeme Conkie →

Ready to get your business online?

Describe your business. AI builds your website in 60 seconds.

Build My Website Free →
Buy NowTry Free
Payment Test Mode Left On After a Staging Push | Web60