Deploy

Set Vercel environment variables per environment

Scope live keys to Production, mark secrets sensitive, and redeploy after changing environment variables on Vercel.

Why it matters

Missing variables break production at runtime. Variables shared across all environments put live keys into every preview build.

How to fix it

1. In Project Settings, Environment Variables, add live keys to Production only.
2. Give Preview and Development their own test keys.
3. Mark secrets as Sensitive so their values can't be read back in the dashboard.
4. Redeploy after any change: environment variables apply to new deployments only.

How to verify

• A preview deployment uses test-mode keys.
• Production has every variable listed in your .env.example.

Related checks

• No secret keys in the browser bundle
• Keep Stripe test and live keys apart
• Keep previews away from production data

Tick it off in the full checklist