nate-event-invoice

[last sage]

@bright granite yes that can happen something unfortunately. It's common with India payments for example

nate-event-invoice

We don't really have the kind of reference you're asking sorry

[bright granite]

@last sage Thanks. To clarify, it happens sometimes but not always? For context, I'm trying to collect data on payment method types associated with payment failures. I thought I could bundle it in with our existing invoice.payment_failed processing and look at invoice.payment_intent.last_payment_error.payment_method.type. Would it work to put this logic in the payment_intent.payment_failed handler instead? Would that ever be emitted without a last_payment_error on the PI?

[last sage]

yeah it depends on cases, it will happen often for India flows where 3DS is required, it's a bit weird unfortunately and you'll have to work around it, for example when you get invoice.requires_action put it in a queue and wait to see if you get invoice.payment_failed soon after

[bright granite]

All right, I'll work around it. Thanks for the info.