#lliu_test-dispute-close

1 messages ยท Page 1 of 1 (latest)

silk cragBOT
#

๐Ÿ‘‹ 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/1430694755355852862

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

pastel smelt
#

HI ๐Ÿ‘‹

Dashboard links aren't very useful to us. Just the IDs at the end will help us get what we need.

#

Okay looking at the request you shared. I see in the response we didn't return the status you expected.

#

But looking at the Dispute object du_1SL8MBDLqYVHbp3EBtd15wXB, I see the current status is warning_closed

#

This matches the behavior in our docs

When the issuer informs Stripe of its decision, we inform you of the outcome by email, in the charge.dispute.closed event, and by updating the dispute status in the Dashboard and the Dispute API object

silk cragBOT
#

lliu_test-dispute-close

odd notch
#

According to the api doc, should be 'lost'. No?

pastel smelt
#

Unfortunately there is a discrepancy between the docs (there are multiple about this subject). The API reference is what you are looking at. We also have this Integration guide: https://docs.stripe.com/disputes/responding#status where we talk about status won and lost for Disputes.

#

Okay I think I figured this out. It won't become closed because it never became a formal dispute

#

You used this test card: 4000000000001976, which creates an Inquiry

#

That matches the way you created this Dispute