Environments: Sandbox and Production

Zevio runs in two isolated instances: Sandbox (testing) and Production (live payments). Each has its own app host, database, API keys, webhooks, offers and transactions. Switching environments does not sync data - two separate worlds.

URLs and switcher

  • Sandbox - e.g. app.sandbox.zevio.io
  • Production - e.g. app.zevio.io
  • Header environment switcher opens the same menu path in the other instance.

Operational differences

  • Sandbox - Tpay test mode; no real charges; webhook signature verification may be relaxed.
  • Production - real charges; full webhook verification; active Tpay/Stripe required on the organization.
  • New partner orgs start in Sandbox - Production requires provider onboarding in client context.

What is separated

Per environment: users (accounts may exist in both but sessions are independent), organizations, offers (qrId), customers, payments, subscriptions, API keys, webhook endpoints, developer logs. Sandbox ids do not work in Production - recreate resources or follow your go-live migration procedure.

Maintenance mode

When Production is under maintenance, the panel may show Maintenance with Go to Sandbox - continue test work without live access.

Separate webhooks

Register different webhook URLs and secrets for Sandbox vs Production.

Environments: Sandbox and Production | Zevio