#jorge_55073
cobalt wharf
Hello
crude falcon
hi
cobalt wharf
Sounds like your live endpoint might be listening for more Event types than just invoice.payment_failed?
crude falcon
no, I can confirm it is only listening for the one event
cobalt wharf
Can you provide an example Event ID that is not an invoice.payment_failed that you are seeing sent to the endpoint?
Sorry that is not one of our Event IDs. They look like evt_xxxx
crude falcon
"evt_1NknS1IDuy4oijCtUoJfo2Tl"
ocean coyoteBOT
crude falcon
I am confused
the issue is that that was a successful payment, yet a invoice.payment_failed event was triggered
cobalt wharf
Ah
Okay that is a different question
I misunderstood and thought you meant you were receiving different Events
Not that the Event was occurring for successful payments
crude falcon
ohh, no
cobalt wharf
Looking
Give me a moment
Okay @crude falcon so what happened here is that a CAPTCHA challenge was presented to the customer.
So the initial attempt was actually "unsuccessful" and the "invoice payment failed". This is the same thing that happens when 3DS is required.
crude falcon
how do we resolve this so we get only true uncessfull payments sent ?
ashen rain
hi there taking over here
You'd need to implement filtering on your webhook handler
We'll send all events of that type, so it's up to you to filter them in your code
crude falcon
Thanks, is there a way to know from the event that is sent that it is not a "real" failed payment?
ashen rain
You could retrieve the underlying payment_intent: https://stripe.com/docs/api/invoices/object#invoice_object-payment_intent
And look at its status: https://stripe.com/docs/api/payment_intents/object#payment_intent_object-status
requires_action would be the scenario where either 3ds or captcha challenge is required
crude falcon
Okay, thanks