#Maxime Beaudry

1 messages · Page 1 of 1 (latest)

dim trailBOT
crisp wigeon
#

It looks like there were three attempts to confirm that payment intent from the payment page. The first two required 3DS but 3DS auth failed to no charges were made. The last one did not require 3DS so the charge was attempted and failed otherwise

#

So it looks like the data in that event was accurate to one of those 3DS failures

half lichen
#

But why don't we have a charge attached to the payment intent for 3DS? If I look at another payment_intent.payment_failed event (evt_3LuZaYGNN1T4yZi61SZiOu7S), this time the payment intent has a charge attached. Why is there a difference in behavior? Note that in that second case, the charge status is failed.

crisp wigeon
#

That event is for a decline

#

Basically failed charges only get added to the payment intent's list on a decline. With 3DS failures the process doesn't get as far as a decline so there isn't a failed charge to add to the list here

#

In the first case the charge was added because of a decline as well. 3DS failed on the first two payment attempts, then the last attempt didn't require 3DS but was otherwise declined

half lichen
#

Thank you. That's good to know.