#.abishek
sinful kindleBOT
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
daring vigil
Well there's a created field on the Dispute object which covers first Q
Otherwise, no. You'd track the win/loss via the related events and use the timestamps from those events. Those timestamps aren't stored on the Dispute object
drowsy heart
what about the due date?
drowsy heart
Otherwise, no. You'd track the win/loss via the related events and use the times...
you said related events, are those events part of the dispute object?
daring vigil
Well the event contains a snapshot of the Dispute object at the time of the event, yes
drowsy heart
sorry, can't seem to find the event property on the dispute object. not sure if I am missing something
daring vigil
There is no event property. Are you using webhooks today? See: https://stripe.com/docs/disputes/responding
drowsy heart
not yet, but is that the way to go about ?
daring vigil
For example, charge.dispute.closed will fire when it's closed. And then you can check status field in that event to determine whether won/lost
And the timestamp of that event will denote when it was won/lost
drowsy heart
ok
daring vigil
It's a better integration than polling the API for updates yes
drowsy heart
i understand and that works for new/current disputes, but API is the only way to get info on past disputes
daring vigil
True. But unfortunately for those it'd be impossible to determine when they were closed without the events
drowsy heart
ok