#heisend3rp_webhooks
dull vineBOT
đ 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/1351967993667522721
đ 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.
- heisend3rp_webhooks, 5 hours ago, 14 messages
old juniper
Hi, taking a look
You just created the refund, https://dashboard.stripe.com/logs/req_PJ0i5uPm2s6JDM and it's not guaranteed that we send that event right away for all payment method types. You should get this event potentially in a couple of day as we still need to talk to the bank and then we send charge.refund.updated event.
buoyant shell
so the refund has not succeeded yet?
other payments normally sent the refund.updated event a couple of seconds after the charge.refunded
e.g. pi_3QsryQLtk7rShy5b0xsvNhGs
old juniper
That is right. These events could be sent a few days later as we wait for updates back from the network
Some network might send them quicker than others
buoyant shell
ok, thanks