boehmi-dispute-dates | Stripe Developers | Page 1

languid nymph Sep 9, 2021, 2:03 PM

#

languid nymph Sep 9, 2021, 2:23 PM

#

hey there, you can get this by subscribing to the charge.dispute.closed event on your webhook endpoint:
https://stripe.com/docs/api/events/types?lang=curl#event_types-charge.dispute.closed

Occurs when a dispute is closed and the dispute status changes to lost, warning_closed, or won.

Stripe API reference – Types of events – curl

Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.

modest vine Sep 9, 2021, 2:24 PM

#

Ah alright, so besides catching the event there's no way basically? We have a little statistics tool that works with only the data from the API

languid nymph Sep 9, 2021, 2:26 PM

#

no as far as i know that date isn't on the object

#

if you added a webhook endpoint, you could set that date on the dispute object metadata to let your stats tool access that

#

set metadata[closed_event_date]={timestamp of event receipt}

#

then you could get that metadata back from the api

modest vine Sep 9, 2021, 2:29 PM

#

Oh yeah, that sounds like a good idea. That's gonna be all the help I needed, thanks!

languid nymph Sep 9, 2021, 2:33 PM

#

excellent, glad i could help!

hoary halo Sep 20, 2021, 1:52 PM

#

@modest vine depending on what you're really trying to do here, it may be worthwhile to point out that the charge.dispute.closed date is generally when Stripe closes the dispute, and may not reflect anything else concrete about the underlying dispute with the card network

#

This is because of the way disputes work with networks under the hood: a "loss" is when the network claws the funds back. A "win" is when the network returns them ... without eventually clawing them back again.

#boehmi-dispute-dates