#ryanw
1 messages · Page 1 of 1 (latest)
I think payment_method.attached would work for both here. Can you try listening to that and then confirm one of each?
As far as I know, that event should indicate that your customer now has a new valid payment method. I forget if the payment intent confirmation will automatically attach the PM though. If you test that will clear up whether this will work
Yes, I see that payment_method.attached is also fired when a payment intent is confirmed. I think this event will work for us then!
But just to confirm - Are you aware of any other cases the event might fire? Is it even possible to attach a non-new method? Or should this event only ever fire when a new method is added to a customer?
Just want to ensure we don't pick up false alarms from some other case where this might fire for whatever reason
That event shouldn't fire multiple times for the same method. You can only attach a method once. Once it is detached it can't be used or attached again.
So yeah I can't think of a time that would be an issue here
Okay, great. This sounds like we should be perfectly good with the attached event then. Thank you for the help!