boylepeter | Stripe Developers | Page 1

round steppeBOT Nov 9, 2022, 5:07 PM

#

serene pivot Nov 9, 2022, 5:10 PM

#

I don't think the Payment Intent can be overridden. Are you just trying to test the firing of the charge.dispute.create event?

onyx gazelle Nov 9, 2022, 5:21 PM

#

No, we're trying to test end to end. So we would receive the dispute (which given the opportunity, would have a payment intent which is also present in our client's db) and then send that payment intent to them for receipt reversal (our application is playing middleman between Stripe and Oracle).

#

We have receipt of the webhook, but the follow on call passing the Stripe data to Oracle is the ask. We of course understand that there has to be some level of "gaming the system" here, but they are asking for functional end to end testing meaning we pass data that matches what is in their system, meaning that Stripe would have to pass that same data. If there were a way to trigger a dispute on a specific payment intent via the dash that would also work? Not sure of the support for that via the dash though.

serene pivot Nov 9, 2022, 5:26 PM

#

It has to be for a specific Payment Intent?

onyx gazelle Nov 9, 2022, 5:27 PM

#

Well it has to be for one that exists in test mode. It can't be an auto generated payment intent ID because that wouldn't exist in Oracle...

#

So for instance the way we have tested "payment_intent.payment_failed" is by using an ACH payment method that fails after processing as successful. That way it makes it past verification in payment element, but then fails.

serene pivot Nov 9, 2022, 5:30 PM

#

I see

#

I don't know if you can test Disputes for alternative payment methods. We have all the test tokens/cards for simulating Disputes, but I think those are always cards: https://stripe.com/docs/testing?testing-method=tokens#disputes

Testing

Simulate payments to test your integration.

#boylepeter