#Oren
1 messages · Page 1 of 1 (latest)
Hi, can you clarify what event you're looking to recieve specifically? Do you have another example object id that worked like expected? Are you referring to charge.refund.updated event?
We did send charge.refunded here, https://dashboard.stripe.com/events/evt_1NpDLTAN9UGzw70g8hUyZRcP. In rare events that the refund failed, we send charge.refund.updated : https://stripe.com/docs/refunds#failed-refunds. Otherwise, this looks to be working as expected. Can you confirm what event you're referring to here?
the charge refunded event that was sent has a status of pending in the charge object
sorry refund object
that refund eventually transitioned to success or confirmed some non pending state
but no update event was generated
i would of expected a charge.refund.updated once the status changed from pending
Unless it fails we do not send charge.refund.updated event.
heres a sample charge.refund.updated event where the status is succeeded evt_3JsQ8vAN9UGzw70g2V93mBSU
something like that is what i would expect, if that is not a guarenteed event transmission is the only work around to poll the refund object and wait until the status changes?
Let me further look, when I tested this on my end I do not see charge.refund.updated
Ok, so the event you shared is from 2021. it looks like you manually update the refund here req_x3jB6SPybI5sbf.
So it looks like things are working as expected, and we only send that event in rare events that the refund fails
ok so for refunds that take time to process we need to poll then correct
Unless you get charge.refund.updated event which is sent when refunds fail you can take that as succeeded.
ok thanks