#nachofranco14-payment_method

1 messages · Page 1 of 1 (latest)

clear stump
#

it will become unusable after first use, and just floating out there. I don't think it will be deleted

twilit hazel
#

so if I want to keep track of the payment methods I create for certain customer I must attach it to the customer

#

even if it will not be used

#

the problem that I want to address is the update of a payment method (we're using sepa_debit) and it seems like the only way to check whether it's a new or not in comparison to Stripe is to create a new one and check the fingerprints

clear stump
#

It sound inefficient to me that way

#

Maybe you can elaborate more on your integration

twilit hazel
#

sure, but you are confirming that there's no other way to check that, right?

dry jetty
#

the fingerprint property of a PaymentMethod always exists regardless of if it's attached to a customer. But you can't list PaymentMethods if they're not attached to a customer so unless you happen to have stored the pm_xxx on your side to be able to directly retrieve it there's no way to know it

twilit hazel
#

I know that, but is there a way to check that an IBAN I have is the same that is in Stripe WITHOUT creating a new payment method? Can I calculate the fingerprint based on an IBAN and billing_details?

dry jetty
#

no, I'm afraid not