#mink4501_webhooks
idle eagleBOT
👋 Welcome to your new thread!
⏱️ We automatically close idle threads, which makes them read-only. Make sure you stick around to chat in realtime!
🔗 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/1212791725408387172
📝 Have more to share? You can add more detail below, including code, screenshots, videos, etc.
⏲️ 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. Thank you for your patience!
sleek waveBOT
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.
- mink4501_webhooks, 1 day ago, 5 messages
- mink4501_webhooks, 1 day ago, 9 messages
proud wraith
I received the following email regarding webhooks.
We’ve attempted to send event notifications to this endpoint 3 times since the first failure on February 26, 2024 at 3:27:49 PM UTC. If this endpoint is important to your application, please try and fix the issue. If you do not need this webhook endpoint, you can remove it from your Stripe webhook settings. We will stop sending event notifications to this webhook endpoint by March 6, 2024 at 3:27:49 PM UTC.
I only have two environments in one Stripe Account, live/test. My company has a total of 4 environments called PROD, STAGE, QA, and FEATURE.
Therefore, I need to register 3 webhooks in the test environment of my Stripe Account for the environments of STAGE, QA, and FEATURE. Accordingly, I registered 3 webhooks.
The three webhooks can receive 404 responses because they send webhooks for payments made in each environment.
That's how I ended up receiving the email below.
Question 1. If I receive the email below, are you sure that the webhooks are no longer being sent? Something really terrible can happen when webhooks are forced to stop being sent like this. Considering this is Production, it's really unimaginable what would happen.
Question 2. If it is true that webhooks are no longer being sent, how can I prevent this from happening? Remember that as of right now, we have PROD, STAGE, QA, and FEATURE environments, so we have to register a total of 3 webhooks in our Stripe test environment.
sleek waveBOT
raven temple
You shouldn't 404 then or else we'll retry. in this scenario you should just ignore the event and 200.
Correct we'd disable. You should fix this issue.
See my first response. You should never send a 404. If it's the wrong env, just ignore the event and 200. You need to send a 200 to indicate to us that the event was received successfully by your app
proud wraith
hello.
What about creating new accounts for the Stage and Feature environments, would this be difficult? My company is a contracted customer with Stripe.
raven temple
Creating a new account isn't too difficult
proud wraith
Will it cost more?