#pain-dispute-events

1 messages · Page 1 of 1 (latest)

meager elk
#

and you want to look at the Events charge.dispute.*

solar osprey
#

I am currently listening to charge.dispute.created

#

But whenever I use a dispute card it just sends back a charge.succeeded

#

I used the test card 4000000000002685 Not received

#

It does create a dispute but I am not receiving a callback

meager elk
#

not sure what you mean

#

disputes happen async after a successful payment

solar osprey
#

I am not receing a call back from the webhook

#

to state a dispute has been created

meager elk
#

do you have an example I can look at?

solar osprey
#

I will try again just in case I did something wrong

#

I will use the 4000000000001976 card

#

Yeah, the only callback I've received is

#

Hm...

#

It may me a middleware issue on my end, just a moment.

meager elk
#

yeah I don't know what the screenshot means, it's full of SQL

#

you should be able to look at all the Events in your Dashboard in real time

solar osprey
#

Yeah, sorry seems like it's a middleware validation issue on my end.

meager elk
#

all good!

solar osprey
#

charge.dispute.created is working, I understand the picture does not show much; was mainly showing the event types I was receiving

meager elk
#

makes sense and so your middleware was ignoring it?

solar osprey
#

Basically I set some product data in the metadata

#

and I attempt to verify the product data to identify between multiple products for different services

#

disputes don't have this data, I was kind of declaring it for multiple use case, (charge.failed and succeeded) if that makes sense

#

with the dispute I assume I will have to retrieve the disputed charge to get this data instead

meager elk
#

gotcha

#

and yeah though we recommend caching all of this in your own DB really

#

when you get the dispute it tells you it's for Charge ch_123 and your own database should already know what that Charge is about

solar osprey
#

Yeah, I cache the charges in my DB. It's just that the data was required initially (successful/failed charges).

#

Should be good now, was my mistake; thanks for the feedback.