#rast_refund-events
heady mesaBOT
👋 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/1212820957572632596
📝 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!
fleet estuaryBOT
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.
- rast_webhooks, 1 hour ago, 20 messages
- rast_api, 2 days ago, 15 messages
pale smelt
rast_refund-events
@paper glen https://docs.stripe.com/refunds#refund-webhook-events covers this in details
So what part are you not understanding exactly?
paper glen
Is charge.refund.updated triggered once charge is refunded
or do we need to subscribe to charge.refunded also
pale smelt
that page covers it exactly
paper glen
charge.refund.updated Sent when a charge is updated
pale smelt
lol
paper glen
charge.refunded Sent when a charge is refunded,
pale smelt
I'm so sorry
Our docs are completely wrong, that's... wild
This part of the doc is what I was referring to
the table you read is totally wrong, I'll get it fixed.
So charge.refunded -> Charge was refuned
charge.refund.updated -> Refund was updated afterwards. This can be because you added metadata, or because we added info like the "ARN" for the reference number, or because the refund failed
paper glen
Ah right... I see.. charge.refunded is the one
pale smelt
yes sorry for the confusion. I read the sentence but really my eyes glossed over it since I know how this works and I didn't realize the doc was so incorrect 😅
paper glen
np thanks for helping out 🙂
maybe to avoid confusion, the event should be called
refund.updated
to indicate that the refund object has been updated.
pale smelt
yeah it's historical from 10 years ago sadly
Someone on my team was looking to "clean up" and add refund.created and refund.failed and refund.updated cleanly but it's not an easy project
paper glen
no worries, it makes sense once you decipher the first one.