#icecoke-refund-eventbehavior
1 messages · Page 1 of 1 (latest)
Hi there, we notice that we're receiving tons of Refund Update event from Stripe. Most of the events come right after the action where we try to void a pre-auth trxn
we never receive Refund Update events for voiding a pre-auth trxn before. We noticed this abnormal behavior from Stripe starting from last Friday
attaching 2 samples for your investivation
-
ch_3OMRuYCX9m5etkmR0JoV67c6 - after pre-auth trxn was cancelled, 2 identical Refund Update events were sent to us
-
ch_3OIDDTCX9m5etkmR15o0wzBa - a trxn cancelled on 1st Dec. NO Refund Update event.
my qns is that
- why did Stripe start sending Refund Update events for Void requests?
- what exactly does the refund update event update?
give me a few minutes to look into this.
sure can
👋 We're adding a new feature where we surface the Refund's ARN which has been a top ask for a few years. This isn't available synchronously though and is calculated after the refund happens
oic....
I'm looking to confirm it's that give me a few minutes
was this feature deployed last Thursday or Friday?
we started a week ago but it's slowly applying to each account as we monitor feedback like yours
icic
Okay I found the Events, there's definitely something strange here where you get charge.refund.updated twice and both have an empty previous_attributes so I'll flag internally
but overall the updated Event is expected now
since the feature is dedicated to surfacing Refund ARN, i suppose for normal refund we'll also expect to receive refund update as long as ARN is generated right?
yup pls, much appreciated
Overall I think it's because the properties for it are still "gated" (not visible) as we roll it out slowly but the Events are still generated. So I think it's expected, even when releasing an authorization as we would still generate an authorization with their bank to clear the funds and that would have an ARN
I flagged internally but things should be stable by the end of the week as it should be fully available for all accounts!
what's the question?
as for the failure refunds cases, you know how it will be reflected in the refund update event?
the status would change from succeeded to failed
Awesome, glad we could help!