#001101011-test-disputes
junior abyss
thx ! i searched but could not find it on https://stripe.com/docs/testing
there is almost what i need with SEPA, but the dispute is immediately lost, i want it to stay open (this is where some edge cases appear that i want to test)
chilly yew
Is there a reason you need the 3 minute gap in time? With the dispute test cards like 4000000000000259 the PI would originally succeed, and THEN the dispute would be created, which should be enough for most tests
junior abyss
i need the delay to test this scenario :
charge is created, then refunded, and then a dispute occur
i have no way to be sure our integration work in this case.
In that specific case i want to "void" the refund in our system and replace it with the dispute, which not totally trivial and definitely needs to be tested.
Any idea on that ?
chilly yew
What do you mean by "void" the refund?
junior abyss
just hide it internally
is there any way to generate a dispute, even manually on test dashboard, after a succesfull charge ?
chilly yew
Unfortunately no - I believe the test cards are the only way to generate a dispute
I could've sworn that we did have a test card that does what you want, but I'm not seeing anything that'll fit what you need
junior abyss
im pretty sure there was one at some point
any recommandation on how to handle this situation ?
any documentation on what should happen could be enough, especially what would happen on the refund object on stripe
i saw an example (in production) where the refund transitionned to failed status
not sure exactly what is the lifecycle and all possible cases though..
chilly yew
Support (https://support.stripe.com/contact) knows more about the specifics of disputes, but to my knowledge we (Stripe) wouldn't do anything to modify the original refund if it was created before the dispute was created. If the refund ultimately fails, that's up to the issuer/card network