#k3davis
woeful quartz
Hello! Are you currently relying on the payment intent events to be sent to your webhook endpoint in order?
junior coyoteBOT
dawn wharf
no, not at all, the issue is in the other direction; the submit logic of our form indicates the payment should succeed first and once complete the receiving api (on our end) amends the payment intent to add the transaction id as metadata. We were puzzling over how it was possible for the transaction id to be added to the payment intent before the payment intent even succeeded. For example in this view, the middle event is the transaction id being added, and the success is above it.
but in the actual event log, the events don't happen in that order. the payment intent timeline view seems to be misrepresenting it, maybe due to lack of precision on the timestamp
woeful quartz
Ah I see what you mean - youre confused why the dashboard is representing the update request as occurring before the event that would have triggered the update in the first place
woeful quartz
No worries - you actually did a pretty good job of phrasing it the first time
Yeah I suspect it's because of what you mentioned (lack of precision with the timestamp)
I can flag it as feedback, but realistically I don't think it's something that can be fixed easily
dawn wharf
perhaps i'm misreading but the log page seems to show the "actual" order, even though the precision is still not shown. the two pages disagree about the order of events
novel plinth
Is this leading to a technical problem in your integration, or is the issue limited to a confusing visual representation?
dawn wharf
the latter, now that i've come to realize it as such; it looked like the integration was inherently flawed and we were spending a lot of time trying to figure out how it was possible