#suraj kumar

1 messages · Page 1 of 1 (latest)

dry pondBOT
steep nymph
#

user can have previously added options also.

solar iris
steep nymph
#

but its not card payment it could be google pay or apple pay or card anything which is configured using stripe dashboard

solar iris
#

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

steep nymph
#

lets assume if i don't have type in that case what can be done, i can iterate over customer_list

solar iris
#

I don't understand what you're asking

steep nymph
#

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

solar iris
#

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.

steep nymph
#

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 ?

solar iris
#

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.