#Atef
1 messages · Page 1 of 1 (latest)
hi! hard to say, are there server logs you can investigate into why your website code might be crashing?
Nope. but when i switched back to the old api keys it worked
I just want to link a different stripe account to the website, is there anything i should do apart from updating the api keys in the environmental variables?
really depends on your own code and what it does
I'm using stripe checkout on nextjs app
could be anything causing this, maybe you have a database that stores e.g. the IDs of Stripe Customer/Product objects, and your code crashes trying to access them since they exist on a different account now
you really need to start debugging it (check the browser devtools in the frontend for errors, look at the server logs in the backend) to see what might be happening and get a lead.
ok. will do. but for now, if i want to link a different stripe account to the website, is there anything i should do apart from updating the api keys in the environmental variables?
again, it depends on your code. There's a bunch of things that could go wrong
maybe your code assumes the use of certain API versions(like it looks for certain fields in the Stripe API response that might not exist in older/newer versions) so will break on accounts using different ones, or it relies on a beta/private Stripe feature your existing account has but the new one doesn't
there's a bunch of things possible here, I can't give you a generic answer. The first step is to find a stack trace of an error somewhere and we can dig into that.
ok. will check the server logs maybe it shows something