#gilles_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/1476116638788223108
📝 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.
- gilles_api, 4 days ago, 28 messages
Hi there, thanks for waiting. Let me take a look
https://dashboard.stripe.com/acct_1NgRcuKHGCD8o7Az/events/evt_1T4bEyKHGCD8o7AzMlLJthjp I found a customer.created event from your account
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
It wasn't delivered to your webhook endpoint successfully because your endpoint returned 403.
That's a very common problem. Hope this doc can help you find out the root cause https://support.stripe.com/questions/webhooks-what-to-do-when-the-http-status-code-starts-with-a-four-(4xx)-or-five-(5xx)
An HTTP status code in the 400-499 or 500-599 range comes from your server, and indicates your system received the request but was unable to process…
Thank you for the clarification. Should be resolved already, had CloudFlare blocking the request.