#parkermurray_code
vital flameBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1224787337108525056
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
rigid dragonBOT
steel bone
Hello! It differs based on use case, but some people have many different Stripe accounts for testing. Others mock API responses instead of actually interacting with Stripe.
See https://github.com/stripe/stripe-mock for example.
mortal linden
I see, those are the two options I have been looking into. Do you know if we can add a seperate testing env under our current stripe account?
steel bone
No, you would need to create another Stripe account, but you don't need to ever activate it.
Test mode fully works immediately when you finish creating a new account.
If you click on your account name in the top left of the Dashboard there should be an option there to create a new account.
You can then click on the name again to quickly switch between accounts.
mortal linden
okay so to test locally test against the "test mode" api we just should create a new account and not worry about making it go live.
steel bone
Yep!
mortal linden
Okay So I will likely need to just have the admin user create one, I assume they will likely have their own api keys and such?
steel bone
Yep, each account has their own API keys.
mortal linden
great okay thanks!
steel bone
Happy to help!