#Wav3
frosty orbit
ripe lotus
hi! well like, we send the event to the URL you specify on the Stripe account you create the webhook
if you have two different shops generally you have two different Stripe accounts and different domains, and the code running on your server knows what shop+Stripe account it's for, so it treats incoming events as being for that account.
ripe lotus
then if an event happens on your Stripe account and any webhook endpoint you have configured to listen for that type of event happens, we'll send it to each of those endpoints
odd edge
that's what I thought it will happen
but, somehow, the notification came only on one of the webhooks
on the wrong one
the events are identical
ripe lotus
what's an event ID evt_xxx where this happened?
odd edge
these are the webhooks
I made a payment on www.wall... and received webhook on www.posters
only on posters. nothing received on wall
event id received on posters: evt_3MHSkYLpt8lgWCBP0qI90T4u
ripe lotus
looks to me like it was sent to both
we couldn't connect to wall.. though since there's a TLS/SSL security error with that site
odd edge
hmm
so you didn't get a 200
then this must be the problem. i'll check that
another thing please
is there any way to check which events were sent to an webhook?
ripe lotus
you can check on https://www.ssllabs.com/ssltest/
odd edge
and see the server's response?
ripe lotus
probably the certificate chain is incomplete(browsers don't care usually but we check this)
ripe lotus
is there any way to check which events were sent to an webhook?
yes it's all logged on https://dashboard.stripe.com/webhooks/we_1MH5b4Lpt8lgWCBPuovoKMqj
ripe lotus
but yeah per https://www.ssllabs.com/ssltest/analyze.html?d=www.wall*****ie&hideResults=on it is a chain issue.
You can see that the report indicates that your certificate chain appears to be incomplete. To resolve this, I recommend visiting the issuer you bought the certificate from and re-installing your SSL certificate, including any 'bundle' file that comes with it. If you're having trouble with this, or have questions, I'd suggest sharing your SSL Labs results with your issuer, they can guide you in locating any intermediary certificates and resolving this.