#goodkat24x7-disputes-testing

1 messages · Page 1 of 1 (latest)

late palm
#

Hello 👋
Let me take a look

#

I don't think we have any test parameters that'd supports testing charge_refunded dispute status. Let me ask a colleague.

Looking into 2.

late palm
#

So for 1/ I have some additional information

Some disputes are not full chargebacks, and can be refunded. Look at the dispute in the Dashboard to see if you can refund it. If you successfully refund a charge before the dispute escalates into a full chargeback, the dispute will be closed with status charge_refunded.

#

For 2/ according to https://stripe.com/docs/disputes/responding

warning_closed, the inquiry or retrieval has timed out and didn’t escalate into a full dispute (known as a chargeback)
Can you share the example dispute ID so that we can dig deeper?

Learn how to respond to disputes using best practices.

thick ledge
#

Thanks! It's now a lot clearer about 1.

#

let me find the dispute id for you

#

dp_1KtWeRIdD8JjQJFvSOzwYHSF

late palm
#

Thanks! Looking

#

Ah its the test cards

#

if you use 4000000000000259 , you'd see it as lost

#

with an inquiry (4000000000001976, the one that you used), it is different

thick ledge
#

so can I test bad case with inquiry?

late palm
#

Not sure I follow
can you expand on that?

thick ledge
#

with 4000000000000259 card I can test winning or loosing disputes. Dispute inquiry is something different, but there can also be two results of it: closing with no funds withdrawal and propagating to a real dispute. I need to test the bad case which is propagating to a real dispute

#

can I do that with test cards?

late palm
#

I'm not sure. looking into it

#

I don't think we have any test cards for these unfortunately 😦
I would suggest you reach out to our support team to see if there are any alternatives here
https://support.stripe.com/?contact=true