#laser_refund-event
stone joltBOT
đ 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/1278776432071282779
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
gloomy shale
@edgy copper charge.refunded would be sent after you already refunded the Charge (partially or not). See https://dashboard.stripe.com/events/evt_3PaaOiCFwC7hG2OA1nbJhR7s
you do have a lot of WebhookEndpoints, some are listening to no events at all. But you don't seem to listen to that specific Event type
laser_refund-event
edgy copper
Yeah. I was still kind of learning. I was getting some duplicate responses, so I may have killed the wrong one.
We did have 19 refunds get processed. I'll see what event fired, then. Stand by..
I'm going to have to do some reconciliation of those to see what happened.
Just to confirm, one webhook endpoint can handle multiple event types, correct? I thought I read somewhere that it was best to have multiple URLs, but I might be wrong about that.
gloomy shale
yes the best approach is one endpoint/URL for all types you care about
edgy copper
Got it. I'll pick one and handle everything through it, then.
I appreciate the help! api.stripe.com/v1/refunds lists all the refunds that succeeded, right? If it's there, then it went through, correct?
gloomy shale
yes
I mean no
some Refunds can fail see https://docs.stripe.com/refunds#failed-refunds
but it will show all created Refunds yes
edgy copper
Ahh, like the one I asked about. Got it.