Most store owners assume the Clover sandbox is a safe copy of their live account. It is not. Clover's docs describe it as a separate test environment for developers, with its own dashboard, its own API address and its own credentials. That makes it a good place to try a payment flow. It also means a sandbox key left on a live store can quietly break checkout.
This guide sticks to what docs.clover.com publishes. It says plainly what a sandbox test cannot prove. It ends on the mistake behind many real-world card failures: sandbox keys on a live site. The same rules apply if you connect WooCommerce to Clover POS with CloverWoo.
Table of Contents
- What the Clover Sandbox Is, and Isn't
- How Do You Test Card Payments in the Sandbox?
- Set Up the Sandbox Environment in CloverWoo
- A Short Go-Live Checklist
- Frequently Asked Questions
What the Clover Sandbox Is, and Isn’t
The sandbox is a test copy of the Clover world. It has its own dashboard and its own API address. Your real merchant account, real customers and real money live somewhere else. Check docs.clover.com for the current sandbox URLs instead of trusting an old bookmark.
How to get set up
Clover's developer docs describe this path:
- Create a sandbox developer account.
- Add a test merchant inside that account.
- Take the Ecommerce API credentials made for that test merchant.
Clover's Ecommerce docs say you need a sandbox-specific Ecommerce API token. Do not reuse a production token and hope for the best.
The quick answers
No real cards are charged in the sandbox. A physical Clover Mini or Flex cannot connect to a sandbox account. Clover's developer FAQ says devices need a Dev Kit or an emulator instead. Clover also says there are currently no test gift cards.
What a browser test cannot prove
A website test is card-not-present. It covers the checkout page and the payment response. It says nothing about card-present flows, device screens, NFC or a kitchen printer. Clover notes that some hardware behavior, including NFC and printing, may not be fully supported even in an emulator.
A passed sandbox payment proves your keys and checkout work. It does not prove your kitchen will get a ticket.
How Do You Test Card Payments in the Sandbox?
The flow is short. Work through it in order.
- Enter the sandbox credentials in your checkout or plugin settings.
- Place a test order on your own checkout page.
- Open the sandbox dashboard and find the payment.
- Compare the result with what the checkout showed.
Test cards. This article prints no card numbers. If Clover publishes test cards, they are on docs.clover.com. Copy them from there and do not trust a number from a forum post. If a number is not on the docs site, treat it as unconfirmed.
Run a pass and a fail. An approved card only tells you the happy path works. Also try a declined card, if Clover lists one, or follow the sandbox docs for forcing a failure. Then look at your checkout. Does the customer see a clear error? Does the order stay unpaid instead of showing as paid?
Keep tokens apart. Sandbox and production tokens are separate. A key from one will not work in the other. Most confusing test results come from this one fact.
Write down which environment each key belongs to before you paste it anywhere. A sticky note on the settings page saves an hour of guessing.
Set Up the Sandbox Environment in CloverWoo
CloverWoo has one Environment setting with two choices. Sandbox is for tests with fake money. Production is for real customers.
Here is the rule to remember. Real customer cards only work in Production. If sandbox keys stay on a live store, every real card fails. The checkout looks normal, so the problem can sit unnoticed until orders stop.
You do not need to repeat the fix steps here. If cards are already failing, read what to do when Clover payments fail in WooCommerce. For the setup steps, follow take card payments.
Want to see a checkout before touching your own store? Try the CloverWoo demo store. It is a safe place to look at the plugin in action. Card payments work for US and Canadian merchants only, so merchants elsewhere cannot go live with them.
One more point. If you run more than one location, each location is its own Clover merchant with its own merchant ID. Test each location on its own.
A Short Go-Live Checklist
Sandbox testing ends when you switch environments. Do these steps in this order.
Switch over
- Change Environment from Sandbox to Production.
- Replace every sandbox credential with the production one.
- Clear any saved test keys.
Place one real order
- Use your own card for a small order.
- Check the payment in your Clover dashboard.
- Check the order in WooCommerce.
- Refund it if you do not want to keep it.
Check the whole chain
- One WooCommerce order should make one Clover order. Look for duplicates.
- Stock should drop by the right amount.
- A customer record should exist.
- If you use auto-print, a kitchen ticket should print.
A sandbox test cannot confirm printing on a real device. Only a live order on your own printer can.
Restaurants should add a few extra orders. Try an item with modifiers, an item note, a tip, a discount and a variable product. Try an out-of-stock item. Test taxes with your own state or province rules. Cancel one order and refund another. Afterward, confirm there is no paid order without a Clover order, and no unpaid Clover order with a paid WooCommerce order.
If something fails
Check the Environment setting first. Then check that every value below belongs to that same environment:
- Merchant ID
- Token
- Public and private keys
- Webhook secret, if your plugin shows one
- API base URL
One mismatched field is enough to fail a payment.
Frequently Asked Questions
Is the Clover sandbox free, and does it charge real cards?
Clover's developer docs describe the sandbox as a test environment, so no live card is charged there. Check docs.clover.com for current terms before you rely on it. Money in the sandbox is not real.
Can I connect a physical Clover Mini or Flex to the sandbox?
No. Clover's developer FAQ says devices need a Dev Kit or an emulator for sandbox work. A physical device needs a production account.
Why does my sandbox token fail on a live store?
Sandbox and production credentials are separate. Switch the Environment setting to Production and enter your production keys. Then check that the merchant ID matches.
How do I test a declined card?
Use a declined test card number only if Clover publishes one on docs.clover.com. If it does not, follow the sandbox docs for forcing a decline. Never guess a number.
Can I try CloverWoo before buying?
Yes. Open the demo store and place a test order. CloverWoo is one plugin for Clover payments plus product, stock, order and customer sync with WooCommerce, with free setup help after purchase. When you are ready, see CloverWoo pricing.