#lizabog_api
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1229441824431804466
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello
Hmm good question. One sec
Okay yeah so you would actually use a Webhook here to listen for charge.dispute.closed and the status of the dispute will change in this case to won or lost: https://docs.stripe.com/api/issuing/disputes/object#issuing_dispute_object-status
Right i do use a webhook going forward but i want to take a look at disputes that were already closed in the past
Hmm there isn't really a way to look backward here since disputes that are lost won't have a new balance transaction... those funds were already pulled at the time of the dispute
For disputes that were won you can look at when the second balance transcation was created
So what does balance_transaction.available_on represent on lost disputes
That balance transaction would be the time that the dispute was issued
Not resolution. Since funds are deducted immediately upon a dispute
What would you suggest for lost disputes? is there an average for a dispute resolution?
No, that's completely up to the issuer/card network really.
I don't have a great suggestion here unfortunately.
It is typically within 120 days as we state here: https://docs.stripe.com/disputes/how-disputes-work#timing
okay thanks for the help, If possible to send to your product managers a feature request for this - adding a resolved date for the API - it would be highly appreciate