Vijaykrishnan

[misty canopy]

hi! well in your Stripe account you only have a test and a live mode.
In either mode, you can add multiple webhooks. We just send events to all the webhooks that should receive an event(if you have two testmode webhooks listening to payment_intent.payment_succeeded and that event happens on your account in test mode, we send it to both those webhook at the same time)

[quasi onyx]

are you sure

we dont see that happening

[dusky dirge]

We're using a similar setup. We just add origin to metadata and ignore it if it's not the correct environment

[misty canopy]

I'm quite sure yes, do you have an example of something like a specific event evt_xxx you expect to be sent to certain endpoints that is not being sent, or vice versa?

[misty canopy]

that's an option too, ultimately Stripe does not really have this concept of dev and staging and prod, it's just testmode and livemode. Another option can be using multiple Stripe accounts(one for dev, one for staging) and their test modes separately(but then it's a pain as things like Prices/other saved objects have to be recreated).

[quasi onyx]

no i dont want to do those

my understanding was stripe should call both the url's its like topic publish subscribe i believe not like stack / queue concept.. i have added an url now and triggering a webhook will keep you posted on the event details

[misty canopy]

Stripe should call both the url's its like topic publish subscribe i believe not like stack / queue concept.
yes, that's true, as I said, if you have mutliple webhook endpoints configured to listen to the same events, we send all matching events to all endpoints. If you see differently let me know so I can have a look!