#ignasidedieu_refund-webhook-events
drowsy oarBOT
👋 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/1326950778375503933
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
finite nexus
Hello 🙂
nimble ospreyBOT
drowsy oarBOT
small knot
Hello, there are things in our system that send out multiple events at once or close together and we don't guaruntee the order that you will receive them in. So we do recommend that your system should be able to handle that. Looking in to these specific events, I am not sure if they are redundant here or not.
https://docs.stripe.com/webhooks#event-ordering
finite nexus
How ofter could we receive a refund.failed event paired with refund.updated? I believe you don't have an answer on this
small knot
Trying to figure that out as well, for refunds the failure would be the terminal state so I think your system can ignore the updated events after
finite nexus
Okay thank you
small knot
As far as I can see, that is right. The updated event will have more info on the refund, but failure is terminal. A refund won't fail and then be recovered.