#suraj kumar
1 messages · Page 1 of 1 (latest)
user can have previously added options also.
hi! you can call this API https://stripe.com/docs/api/payment_methods/customer_list and parse the result and render details of the PaymentMethods(like brand, last4 digits, etc: https://stripe.com/docs/api/payment_methods/object#payment_method_object-card ) in custom code in your frontend.
but its not card payment it could be google pay or apple pay or card anything which is configured using stripe dashboard
well Google/Apple Pay would still be saved as type:card so the same thing applies
but yes, as part of your custom code you need to check the type of the PaymentMethod object and adjust accordingly to look at the fields relevant to it
lets assume if i don't have type in that case what can be done, i can iterate over customer_list
I don't understand what you're asking
in my case i just add eda payment method using paymentIntent API and later on i will create a subscription on it
now after adding that method, i would like to display added method details
like selected payment method and all
what is a "eda payment method"?
now after adding that method, i would like to display added method details
sounds good! my first reply in the thread describes how to do that.
okay
one more question
Currently we are in migration phase ,
Till the time we were creating a token using stripe.createToken and then we accept payment but now would like to move on payment method. Can you please highlight me what kind of issues we have to handle for backward compatibility ?
it's hard to say, but there aren't any specific concerns since the APIs that accept PaymentMethods generally all accept old saved Card objects too.