#simonecervini_webhooks
1 messages · Page 1 of 1 (latest)
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1290237551189426197
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- simonecervini_unexpected, 2 days ago, 13 messages
Hi
I want to mention that your endpoint responded with 405, Stripe has no control on it...
I'm aware, but we only respond with 405 if the request isn't using the POST method, which per your documentation should be the only allowed method. Can you confirm all requests are sent as POST?
Also, the same day, we received confirmation of an issue on your end with Apple Pay on iOS 18. The transactions were linked to tests related to that problem: https://discord.com/channels/841573134531821608/1289167914687135774
Also, the same day, we received confirmation of an issue on your end with Apple Pay on iOS 18. The transactions were linked to tests related to that problem: unknown
Yes we are currently, investigating the Apple Pay issue on the iOS 8
But regarding the webhook endpoint, Stripe send only POST request on the webhooks.
If you didn't received a POST request, what was the http method then ? Did you trace it ?
It's very strange and concerning. Unfortunately, we don't have logs for that endpoint due to a short retention period (24h), and these logs were from Friday, so I can’t verify the exact method of the request.
I understand this might seem like a simple mistake, but honestly, I don’t see how it could have happened. Our platform handles donations from tens of thousands of users and multiple partners using Stripe Connect. We've never had issues with webhooks before, and nothing has changed. A 405 error appearing suddenly, especially alongside another confirmed issue, seems highly suspicious.
How do you suggest we proceed? We're trying to replicate the issue for more details, but do you have any further insights on your end? I'd also note that this error hasn't affected production users
How do you suggest we proceed?
I invite you to log the event and share with us what is the method you received and what eventId