Try things in test mode

Test mode lets you try programs, partners and payments before real customers see anything. It works like Stripe's test mode. Your company gets a hidden copy that holds only test data. Test orders, rewards, partners and payouts stay there and never mix with your live records.

Switch to test mode

Turn on Test mode at the bottom of the sidebar. On a phone, or with the sidebar collapsed, open the account menu and choose Switch to test mode. A banner stays at the top of every page while you're in test mode. Choose Switch to live mode in the banner to go back.

The first switch creates the test copy. It starts with your company name, currency and languages, and with no programs, partners or orders. Everyone on your team can use test mode, with the same role they have in live mode. The Team and Billing tabs don't show in test mode, so invite teammates and manage your subscription in live mode.

What stays switched off

• Partners get no emails. The email log under Notifications lists each one as skipped, with the reason "test mode, not sent".
• Test orders never count toward your Grizzlee bill.
• No real money moves. You can record manual payouts. Stripe payouts need a Stripe test key, so they only ever reach Stripe's test mode.
• Loyalty passes in Apple Wallet and Google Wallet get no updates.
• Test programs have no public signup page.

Webhooks to your own endpoints still fire, so your developer can check them. Every event has livemode set to false. Live events have livemode set to true.

Keys and connections

Test mode has its own keys under Developers. Server API keys start with grizzlee_test_ and publishable keys start with grizzlee_pub_test_. Test keys reach only test data, and live keys reach only live data.

Connect your payment provider again while in test mode, with its test details:

• Stripe takes a key that starts with sk_test_ or rk_test_, and the signing secret of a webhook you add in Stripe's test mode.
• Paddle takes a sandbox API key, which starts with pdl_sdbx_.
• Chargebee takes your test site, whose name ends in -test.
• Lemon Squeezy takes a webhook you add while your store is in test mode.
• Shopify takes a development store, or a store that only takes test payments.

Live connections refuse test keys, sandbox keys and -test sites. When a live connection receives a test payment, such as a Stripe event with livemode set to false, a Lemon Squeezy order in test mode or a Shopify test order, Grizzlee ignores it and says why under Incoming events. A test connection ignores live Stripe and Lemon Squeezy payments the same way. Each connection has its own webhook address, so Grizzlee never moves an event from one mode to the other.

Shopify doesn't say in its webhooks whether a store is a development store. A Shopify connection in test mode records every order it receives, so connect only a development store or a store that takes test payments.

Try an order

Choose Send a test order on Home. In test mode, Record test order saves the order in test mode right away, with no confirmation. In live mode the same sheet still records a real order and asks you first.

Copy a program to live

When a test program works the way you want, open it and choose Copy to live. Grizzlee creates the same program in live mode, paused, so it rewards nothing until you turn it on there. Only the program's settings are copied. Custom rules for one partner or customer stay behind, because those partners and customers exist only in test mode. The button copies the saved program, so save your changes first.

Delete test data

Owners and admins can choose Delete test data in the banner. After you confirm, Grizzlee deletes every test program, partner, order, reward and payout, and turns off test keys, webhooks and connections. Live data stays as it is. Your next switch to test mode starts with an empty copy and new keys. Webhooks your providers send to the old test connections stop working, so connect your test provider again.

Deleting your company deletes its test mode too.