Switching environments

Switch Sandbox ↔ Production from the panel header (button with current environment name). Click opens the same menu path in the other instance - e.g. Offers list in Sandbox becomes Offers list in Production (different data).

What happens after switch

  • Full app reload on another host.
  • Different organization list (same user emails may have orgs in both, but separate records).
  • Different API keys, webhooks, qrId, sessionId - not migrated automatically.

Sandbox → Production checklist

  • Complete organization onboarding in Production (Tpay, Stripe, company data).
  • Recreate offers or migrate via API/internal scripts.
  • Generate new API keys and update webhook URLs in external systems.
  • Test one small live payment before full traffic.
  • Update embedLink and CSP domains for checkout in Production.

Partner and client portfolio

In Partner view the Environment column shows Sandbox vs Production per client. Header switcher works the same in client organization context.

Not migrated automatically

  • qrId, API keys, webhooks, Tpay/Stripe merchant IDs.
  • Offers, customers, payment history.
  • Separate cookies per host.
  • qrId, API keys, webhooks, Tpay/Stripe merchant IDs.
  • Offers, customers, payment history.
  • Separate cookies per host.
Switching environments | Zevio