#shpatak
1 messages · Page 1 of 1 (latest)
Hi there. What's the issue exactly?
I have to sort all the events by the created date in order to process them in the order they have been created (it's vitally important for our app to process them in the sequence they suppose to be)
It works fine when doing the following actions: payment_intent.succeeded, charge.succeeded, charge.refunded
They shouldn't be created at the same time, because they are mixed and in real world it won't act like that
Got it
So what action did you take to generate the above events in the screenshot?
Were they generated via Stripe CLI commands or what?
Just pay with card: 4000 0000 0000 0259
it should open fraudulent dispute after paying
Dispute is successfully created, in the image you can see that this order is present: payment_intent.succeeded -> charge.dispute.funds_withdrawn -> charge.dispute.created -> charge.succeeded
it should be -> payment_intent.succeeded -> charge.succeeded -> charge.dispute.created -> charge.dispute.funds_withdrawn
Got it
Yeah that's just how our test flow works currently
I can provide this feedback to the team, but no guarantees on when it would be fixed
Yes, please, it would be great to fix, it's vital even for testing, currently we have no idea how to work with this payload
here is the second try:
*nevermind, it is sorted anyway
Ok so this behavior is intermittent?
not quite
the second image is showing wrong sequence as well
it should be -> payment_intent.succeeded -> charge.succeeded -> charge.dispute.created -> charge.dispute.funds_withdrawn
Well order of events received isn't guaranteed
Yeah I'll report it to the team
Thank you so much