Reid-dispute-event | Stripe Developers | Page 1

willow marten Aug 3, 2022, 6:03 PM

#

Happy to help. Do you have a dispute ID?

cunning hazel Aug 3, 2022, 6:04 PM

#

I do! I also have the event id.

disputeID:pdp_1Kz8miFXc3zoUgUupwS818ff

eventID: evt_1Kz8mkFXc3zoUgUu6n4izjwT

#

I think that first one is the dispute id anyway. I also have the paymentID that the dispute started from if that is helpful.

willow marten Aug 3, 2022, 6:06 PM

#

It doesn't look like there were any webhook attempts. Let me dig a bit deeper. Just a second

#

Have you received events for charge.dispute.closed since May 13th when this dispute closed?

#

Ahhh, okay I figured it out. The charge that was disputed was created on behalf of a connect account, so you need to make sure your connect webhooks are configured to listen for other events: https://dashboard.stripe.com/webhooks/we_1H7tI1FXc3zoUgUuJQM2ZJvI

Stripe Login | Sign in to the Stripe Dashboard

Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.

#

Right now it only listens for account.updated and payout.failed

cunning hazel Aug 3, 2022, 6:14 PM

#

oooooh, so we are listening for that on the wrong endpoint. We are listening for that on the Account webhook

#

Would this event ever go to an account webhook? like if the dispute was won instead? Or would that only be related to a dispute on a subscription payment or somesuch?

willow marten Aug 3, 2022, 6:19 PM

#

Would this event ever go to an account webhook?
I don't believe so, because it's a charge.dispute.<something> event, which means it lives on the charge object, so the event should always be on the connect account for charges made using the transfer_data field

cunning hazel Aug 3, 2022, 6:20 PM

#

Great. Thanks for clearing that up!

willow marten Aug 3, 2022, 6:22 PM

#

Sure thing!

#Reid-dispute-event