#xxxxx-events

1 messages · Page 1 of 1 (latest)

warped kestrel
#

hi! what do you mean by "update the keys"? and what are "ongoing events"?

magic geyser
#

means the secret and publishable keys

#

ongoing events- payouts and all.

warped kestrel
#

not sure what "payouts and all" means. And I don't know what you mean by "updating" those keys.

magic geyser
#

changing the keys.

warped kestrel
#

can you be more explicit? How do you change the key exactly?

#

like do you mean rolling the key through the dashboard? https://stripe.com/docs/keys#rolling-keys It really would help if you explained in a little more detail and longer sentences about what specifically you are thinking about.

magic geyser
#

As i have two environements created one dev and the other is staging. So for the dev environment i am using the keys of another account, so i have to also change the secret and publishable keys as well.

#

I just want to ask will that create any problem?

warped kestrel
#

it could! Hard for me to say since it's your environment. If you change the API keys then you're operating on an entirely different Stripe account. Maybe you have a database full of IDs of Stripe objects from the other account and your code starts breaking because it gets 404s from the API accessing them. Maybe the accounts are on different default API versions (and you don't force on your requests(https://stripe.com/docs/api/versioning) ) and that could lead to bugs in your code.

magic geyser
#

Is their any solution for this, as my two environements were having the same keys and different database so it was also creating problems, Is their any way how will i solve this one.

warped kestrel
#

I can't suggest a solution when I don't know what the problem is.

magic geyser
#

Sorry, I have two env. my webhook were failing because the event was created on the dev env. and we have webhook created in the staging env. so it was giving error because that payout id was not found in my staging database because it was created on dev.

#

So now i want that for both the env. i should have different keys.

warped kestrel
#

makes sense!

#

I 'm not sure what I can suggest here. You need to not use the the same database for two different accounts, or add some logic like a row in the tables so you know what account it's meant for.

magic geyser
#

What if i create a new account in my stripe account , and mark it as dev and another for staging .

warped kestrel
#

not sure what that means. Stripe doesn't know what a dev or staging account is.

#

they're just different accounts entirely.

magic geyser
#

in the .env file in nodejs we store the same API keys ,

warped kestrel
#

the fix here is on your side, not Stripe's. You need to properly set up your databases and code to work for multiple Stripe accounts if you are using multiple accounts. That's code you have to work on.

magic geyser
#

will the key will be different for different accounts?