akdj16

[onyx beacon]

It'll likely always be sepa_debit as that is the recurring type of a Bancontact payment method:

After your customer authenticates the payment, Stripe refunds the payment and store your customer’s IBAN in a SEPA Direct Debit payment method. You can then use the SEPA Direct Debit PaymentMethod to accept payments or set up a subscription.
https://stripe.com/docs/payments/bancontact/set-up-payment#:~:text=After your customer,a subscription.

Bancontact PMs are single use and can't be saved to your customers

[south bay]

yes, I know that, but how to find out that the sepa pm attached is caused by a boncontact ?

[onyx beacon]

I'm not sure you can unfortunately. Maybe you can check for some details in the sepa_debit hash on the PM: https://stripe.com/docs/api/payment_methods/object#payment_method_object-sepa_debit

Otherwise you may need to make a manually link between the 2, perhaps using metadata: https://stripe.com/docs/api/payment_methods/object#payment_method_object-metadata

[south bay]

can we retrieve the setupIntent using the paymentMethod?

[south bay]

that what I prefer to avoid 🥲

[onyx beacon]

Yep, via: https://stripe.com/docs/api/payment_methods/object#payment_method_object-sepa_debit-generated_from-setup_attempt

[south bay]

ok, let me try

the test looks good for me, I can find the bancontact type inside the generated setup attempt

thanks!