#notaduck-test
1 messages ยท Page 1 of 1 (latest)
hi there! you can use the test API keys for testing and setup a separate endpoint in test mode
you can use the Stripe CLI to forward events to your localhost : https://stripe.com/docs/cli/listen#listen-forward-to
or you can use ngrok to expose your local endpoint publicly
The case is that I have our new API hosted on a development server that is already public, I am just afraid that it will get the events from the webhook from the "old" website so I don't send a policy out by accident to a customer.
if that makes sense?
Oh, so what you are saying is that once I create a webhook when the "Test mode" is on, the webhook wil only respond to development events. right?
yep that's right
Thanks!
or an alternative is if you're really worried. Create an entirely separate Stripe account for testing only
the troublesome thing about that is maintaining the same settings on both accounts
that makes sense, but I can also see that the url https://dashboard.stripe.com/test/webhooks/create indicated that it is a test webhook.
So i am not so worried anymore, thank you so much!
Sry for being a little slow here, I still need that first or third cop of coffee.
np ๐
One last question.
Creating the webhook throug the vs code plugin, would that be a test as well or in the live enviroment?
I really like your docs but something like this is not exactly clear.
it would create it based on the secret API key that you've defined
so if you're using your test key, it would create it in test env
if you're using your production key, it would create it in prod env
Ahhh, so I should not have logged in with the account, but with the api key instead.
honestly, i haven't used this before. So i'm not all that certain about how this plugin works
Fair enough ๐