#brandon_webhooks
jovial irisBOT
👋 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/1287771103992746075
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
gleaming depotBOT
deft coral
Hi there 👋 are you creating your refunds by making requsets to our API? If so, the ID of the Refund object that is created is included in the response to that request and you may not need to listen for the Event you reference.
charge.refund.updated includes the Refund object though, if you need to listen for Events related to refunds that may take time to process.
magic atlas
Hi Toby!
Yes, I'm creating the refunds via API requests, and I do store the ID from the response. If the refund succeeds immediately, I perform all of our business logic right away.
I'm more concerned with refunds that take time to complete, as you mentioned. The refunds documentation implies to me that charge.refund.updated event only covers failures, metadata changes, etc. Are you saying that I'll receive this event for completed refunds as well?
