I am having a critical issue where my production deployment is being injected with an incorrect environment variable value. My frontend code is reading process.env.NEXT_PUBLIC_STRIPE_PUBLISHABLE_KEY, but it is receiving the value of a completely different secret variable. I have already redeployed without cache and confirmed the key is not hardcoded in my source code. This appears to be a platform bug.
Hi @mychapterpay, welcome to the Vercel Community!
I’m sorry that you are facing this issue. Can you confirm if you’ve set the environment variable correctly for the Vercel environment? For example, if you are accessing the production deployment, the variable must also be set in production.
For testing purposes, can you try adding a dummy public variable and accessing it on the frontend to see if that works?