#junger

1 messages · Page 1 of 1 (latest)

opal lynxBOT
karmic ravine
#

Hm this shouldn't be because of multiple stripe accounts. If a payment is made on a particular account, that account's webhook endpoint should get the event. Having multiple accounts shouldn't matter

#

Can you send an event id of an event that had trouble reaching one of your endpoints?

#

Want to see what kind of errors are happening

lusty lotus
#

Oh jeez. I think I just figured it out. The webhook was only enabled on 2 of the accounts; and disabled on the other 2. I assume that would cause the issue 😅

karmic ravine
#

Well if we have trouble reaching a webhook endpoint, the endpoint is disabled automatically after a certain period of time so that could be what happened

#

Would need to see an event id or webhook endpoint id to investigate though

lusty lotus
#

Ah OK. Here's a webhook event ID:
we_1MFVMzK1k2iVVIhHWSLAebnV

#

*sorry, webhook ID

karmic ravine
#

Ok looking

#

Ok so this is the error on your server that caused all the event processing to fail:
Invalid request. Webhook could not be processed. No signatures found matching the expected signature for payload

#

I recommend checking your server logs to narrow down the issue. You might be using the wrong webhook endpoint secret

lusty lotus
#

What type of error would we see in our server logs?

karmic ravine
#

Well you should see the above

#

You can also go in your accounts dashboard in the developer section and click the webhook endpoint

#

It will show a list of attempted deliveries for events

#

But on your server what you see depends on your existing logging in your code

#

So I would check that the signing secret you're using on that particular endpoint matches the signing secret of that endpoint on the dashboard

lusty lotus
#

OK, got it. I checked the logs and unfortunately it happened too long ago that they've already been rotated. But I assume that I could reactivate the endpoints and make sure that the signing secret is correct with the form submitting to it, right?

karmic ravine
#

Yeah

#

The above error could have numerous causes, but since you have multiple endpoints, the most likely cause is you're just using the wrong signing secret