#Wakeuphate - Disputes
gentle axle
Hey 🙂
tropic bluff
Do you have some concrete examples you are curious about?
gentle axle
So what we're trying to do really is derive status for an invoice that's been disputed and alert the user
My problem is that to derive that I'll need to reach through the payment intent or the charge - Payment Intents I am pulling down to our DB but Charges I am not yet
tropic bluff
Okay, that makes sense.
gentle axle
I'm really asking to find out if I need to also ingest Charges too as a possible way to reach the Dispute
tropic bluff
In some cases (I'm looking at a test dispute in my own account now), the associated charge record will have an associated_payment_intent set (if the charge was generated from a Payment Intent).
In either case you would want to expand the transaction property to get a view into what the transaction is that is being disputed.
gentle axle
hmm I dont see that listed anywhere in the docs, is it metadata? (the charge, that is)
tropic bluff
Which docs are you referring to? It'll help if we're on the same page
gentle axle
Ah yes, sorry - I keep making this mistake too, it's not the Dispute at the Issuing level - https://stripe.com/docs/api/disputes
I think it might be looking like the path back to an invoice is dispute -> charge -> invoice
tropic bluff
Yes I think there are some discrepancies in our docs and the current Dispute object. Can you share a Dispute ID so we can talk about a specific record?
gentle axle
Unfortunately not at the moment, i'm currently just testing for the most part - we have a lot of live customers but i've not yet pulled any disputes in
I'm not even sure there are any yet