#kikkm2022-environments

1 messages · Page 1 of 1 (latest)

tiny furnace
#

Hi there! This is really up to you... we don't have a lot of recommendations here. If you want to differentiate them, one way to do so would be to use the + email trick. So like test+123@gmail.com will still have emails sent to test@gmail.com but that can differentiate it.

placid scroll
#

and i assume we can create different products for each environment

#

like if I'm doing a refund

tiny furnace
#

Yes it should

placid scroll
#

ok, interesting

#

i think i remember that from years ago!

#

do you have companies that set up multiple Stripe accounts for this reason?

tiny furnace
#

Yes it is common to set up multiple accounts for dev/staging/prod

#

It is a little tricky to ensure they are all configured the same

placid scroll
#

ok, got it

tiny furnace
#

But it is the best way currently

placid scroll
#

i see

#

so you gain data separation but the cost is that you have to keep the config the same

tiny furnace
#

Yep

placid scroll
#

is there any other way that people differentiate the users?

#

other than the +123

#

?

#

Is there some metadata that could be set on the user record

#

and filtered

tiny furnace
#

What do you mean by user record exactly?

#

Like metadata at the Account level?

placid scroll
#

Sorry, I should have said "customer" record

#

is there a field we could use to differentiate dev and staging customers

tiny furnace
#

Depends a bit on what your integration is doing, but on almost all objects you could set metadata that you could use to differentiate if you wanted to go that route.

placid scroll
#

ok

#

got it

#

i guess we'll have to discuss the pros cons of the config vs. data separation issue.

tiny furnace
#

Yeah that is essentially the tradeoff

placid scroll
#

Ok, appreciate the help!