Skip to main content
Blink provides a dedicated Test Mode to help you build, experiment, and verify your integration safely before going live. When Test Mode is active, all dashboard metrics, orders, customers, and events are strictly sandboxed.

​
Toggling Test Mode

You can toggle Test Mode globally from your Blink dashboard.
  1. Open the sidebar navigation.
  2. At the bottom, locate the Test Mode toggle right above your active store selector.
  3. Turn the switch ON.
  4. You’ll see a global orange banner appear at the top of the dashboard indicating that you are now viewing and interacting with simulated test data.

​
API Keys in Test Mode

Blink provides two sets of API keys for each store:
  • Live Keys: pk_live_... and sk_live_...
  • Test Keys: pk_test_... and sk_test_...
To perform test operations via the API, simply use your _test_ keys. Test mode API calls will generate test data (like test orders and customers) that are only visible in your dashboard when the global Test Mode toggle is ON.

​
Using the Shopper API in Test Mode

If you’re using the Shopper API or building a custom storefront, ensure that you pass the pk_test_... publishable key to your frontend client. Any checkouts generated using the test key will automatically use Stripe’s test environment, allowing you to use Stripe’s test cards to simulate successful or failed payments.

​
Test Mode Sandboxing Rules

When the dashboard is in Test Mode, the following rules apply:
  • Analytics & Overview: Revenue, MRR, conversion rates, and sales data are recalculated using only test volume.
  • Orders & Transactions: Only test purchases, refunds, and failed checkout attempts are shown.
  • Customers & Subscriptions: Only customers and subscriptions created via test API keys or test checkouts are visible.
  • Discounts: Any coupons you create while Test Mode is ON are flagged as test coupons. They will not be accepted in live checkouts.
  • Payouts: The Payouts dashboard will display a $0 empty state, as payouts are not processed for test transactions.
  • Webhooks: Webhook endpoints are strictly separated by mode. When creating an endpoint, it’s assigned to your current mode. Test webhooks will only receive test events.