vilesa - prevent duplicate payment methods | Stripe Developers | Page 1

vivid kelp May 31, 2022, 2:21 PM

#

Unfortunately there isn't a setting for this. To de-duplicate payments like this, you will probably want to check the fingerprints and make a delete call on one of the PaymentMethods yourself

#

Which could probably be done here in something like the payment_intent.succeeded event

lucid mauve May 31, 2022, 2:34 PM

#

I see

#

do you confirm the event payment method attached is not triggered for these?

vivid kelp May 31, 2022, 2:36 PM

#

That event would still be triggered on the payment because the PM is still getting attached. That event actually may be better to listen to than the payment succeeding event

lucid mauve May 31, 2022, 2:42 PM

#

do you confirm 100% this event is triggered? I had understood it was not (for generated_sepa_debit from bancontact)

vivid kelp May 31, 2022, 2:48 PM

#

If it gets attached to the Customer it should be called at some point but I have not had the chance to test to 100% confirm. If you test this in test mode you will see the same event behavior so you will know what you can react to

lucid mauve May 31, 2022, 3:03 PM

#

I confirm this event is not triggered: payment_method.attached

vivid kelp May 31, 2022, 3:07 PM

#

Good to know, I did not realize that that did not happen with some of our payment methods in this scenario

#

Thanks for reporting back, I will make sure to remember that

lucid mauve May 31, 2022, 3:20 PM

#

np, thanks

#vilesa - prevent duplicate payment methods