#linups_webhooks
lyric laurelBOT
👋 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/1467881610572726304
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tacit sinew
👋 Hi there! Let me take a look
It looks like you got two events because you requested a refund twice via the Dashboard:
dark breach
how i can request refund twice for the same transaction?
tacit sinew
Yes, that does seem unexpected that the second request should have succeeded. Taking a look…
dark breach
thanks
lyric laurelBOT
tropic crystal
Hi taking over
Not sure why you were able to create 2 via the dashboard for the same transaction. We're not very familiar with dashboard behavior in here unfortunately. However, I see only 1 of the refunds went through. The other was canceled. So the customer should only have received 1 of those.
Ah I see what happened actually
The first refund was also cancelled via the dashboard before the second was created
So you can create a second refund if you cancel the first
Here's the request for the cancellation: https://dashboard.stripe.com/acct_102pHV2WxmpWlx1M/logs/req_21rMycN1m3Wk0K
dark breach
then before parsing refund webhook i have to check if it is unique one?
until now, we were not checking that and i noticed mulple refunds for same transaction.
tropic crystal
I don't know what your code does so hard to say
dark breach
as both comes as: "type:charge.refunded"
right now, we parse webhooks "charge.refunded" and save in database.
tropic crystal
Yeah up to you really. Not sure your application's requirements. I also recommend listening to refund.failed so you can keep track of which refunds actually are refunded successfully
dark breach
so "charge.refunded" is not equal as successfull refund?
tropic crystal
Correct
That's sent when the refund is initiated
You'd need to listen to refund.failed
They can fail due to a number of reasons
Including if you initiate one and then cancel it shortly thereafter (as in the above example)
dark breach
got it. thanks for tips.