cris-moshtix_webhooks

[rustic crown]

👋 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/1361703144563675369

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[willow carbon]

refund.updated is only sent in cases where the refund is update, for example getting the refund reference number in the example you shared

WHat exactly are you trying to do that is not working like you expect?

[storm palm]

I need to listen to webhooks for refund completions. I got told by your senior manager that "refund.updated" would suffice. I can also tell you that some webhook currently firing "refund.updated" are correctly doing what I'd expect and completing the refund on my end. It's the first time I hear this event is for a refund updated, like its details, not its completion status.

[willow carbon]

Do you have an example that is not sending this?

It might be that it is pending for longer than you expect, and the update comes later

or it might not require any updates and is considered successful immediately

[storm palm]

Actually, looking better at one of the refunds, I got first a charge.refunded, then the refund.updated twice. So I think I'm always getting a charge.refunded event. Are u suggesting all I need to listen to is charge.refunded event only? All I care is the refund completion event.

[willow carbon]

There should always be charge.refunded and refund.created -- whether there is refund.updated depends on whether there are updates required, as i explained

You likely need to listen to two event types, refund.updated plus one of the others to be able to track refund success

since it might be on creation or might be later

Not all refunds work the same way

[storm palm]

Ok, I have a few questions then:

1. "refund.updated depends on whether there are updates required". What do you mean? Am I supposed to provide any kind of info when receiving this event?
2. Are you saying sometime refund.created is all I'm going to get? No other events? If yes, how do I know this event is all I'm going to get?

[harsh panther]

Hi taking over here as synthrider has to step away

1. Recommend reading https://docs.stripe.com/refunds#refund-events there's more info there. You don't provide any info. I'm not sure what you mean by that.
2. There will be other events like charge.refunded. My colleague was just explaining that refund.updated isn't always sent

[storm palm]

1. Clear
2. I've read the doc you linked. I see also refund.failed. Is this sent instead of charge.refunded in case of a refund being declined?

[harsh panther]

Yes that's correct

[storm palm]

Ok, thanks for your help