#adam-williams_api
mortal glacierBOT
👋 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/1339558611579310176
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
sage cipher
it's the actual claim made by the card issuer attached to a dispute which gives the reasoning for it being raised (an actual explanation in English, beyond the network reason code)
In Dashboard it's displayed in a modal with title "Evidence from the cardholder’s bank"
chargeback_issuer_evidence is the field name Stripe appears to use for this, but I can't see how to retrieve it from the API
surreal seal
chargeback_issuer_evidence is the field name Stripe appears to use for this,
where do you see this? I can't find this field in the API reference
sage cipher
it's not in the API reference
Dashboard makes request to https://dashboard.stripe.com/v1/disputes/internal/issuer_evidence?include_only[]=chargeback_issuer_evidence.id
sage cipher
it's not in the API reference
(that's why I'm asking where it is 🙂 )
surreal seal
got it! then it just means this is a Dashboard-only feature. so this information cannot be accessed in the API.
sage cipher
Okay, follow-up question:
What's the point of having an API to allow you to update and respond to a dispute programmatically if you can't build an integration that actually .. lets you view the claim made by the card issuer first? You can't respond to a dispute if you've not even read the claim made by the card issuer, surely?
If responding to a disupute is effectively dashboard-only, fair enough - but I wish the docs would be clear about that.
(is there a more appropriate venue for me to have a moan about this than here?)
surreal seal
I agree this is not ideal
but you can see all fields in the API ref here: https://docs.stripe.com/api/issuing/disputes/object
if you have feedback about this, feel free to raise it on https://support.stripe.com/contact
sage cipher
I'll drop our account manager an email, thanks.
mortal glacierBOT
terse egret
would you mind me closing the thread then?
sage cipher
go for it, I got nothing else