#crypt1c-webhooks

1 messages · Page 1 of 1 (latest)

solar raven
#

👋 happy to help

#

is it best practice to create a new account (within my login) for the Test env?
could you please clarify this

cloud olive
#

well the 2 options I've seen are either that or to use Test mode in the same account

#

I want to be able to add a webhook that doesn't get the prod traffic

#

it should only get the Test traffic

solar raven
#

that's possible

#

you should create it here https://dashboard.stripe.com/test/webhooks instead of https://dashboard.stripe.com/webhooks

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

cloud olive
#

what if I have 3 other envs and want 1 webhook for each?

#

should they all be created within /test ?

solar raven
#

yes and you can do something like https://example.com/webhooks?env=...

#

and you'd have to add metadata and set the env on each object you create

cloud olive
#

so creating another account is just overkill for this?

solar raven
#

I guess for the time being that's your best shot

#

or create an account per environment

#

it's not about being an overkill or not

#

but today we don't provide the ability to create multiple sandboxes of test modes

#

so you either have to create accounts/env

#

or try to do some workarounds

#

there is no clean way of achieving this

#

we are aware of this shortcoming and our teams are working for a future improvement on that

cloud olive
#

ok so Test mode is basically 1 sandbox for that account

solar raven
#

yes exactly

distant pivot
#

Hey, taking over here. Let me know if there's any follow-up Qs I can answer!