#andrea-skuola-paymentmethods
1 messages ยท Page 1 of 1 (latest)
hi! that call does return all the payment methods attached to that customer, and the ordering is most-recently-created first.
yes, if i want to order card ascending?
so the first created is the first in the list
that's not possible unfortunately, all list endpoints in our API use the same ordering of most recent first, and can't be customised
oh ok
you can of course take that list and then reverse how you show it in your own UI and code
but in terms of what's returned by the API directly, the JSON response is a list of payment methods most-recently-created-first
ok thanks
another question: can I create two setupIntents in the same page or they runs in conflict?
Hello ๐
Taking over for karllekko here as they had to step away.
I'm not sure I follow the use-case here.
i have to add a payment method for customer, not in payment flow, just in case user want to change payment method
i give him 2 cases: card or sepa_debit
since i have my graphics can i create 2 setupIntent for generate the 2 forms that makes user add the payment method choosen
?
since i have my graphics can i create 2 setupIntent for generate the 2 forms that makes user add the payment method choosen
are you creating these forms on your own or are you using Stripe elements?
Stripe elements
if i give different ids to forms and elements everything should work, right?
I'm not sure as I haven't tried this flow personally.
I'd suggest you give it a try and see if it gives you any errors. I'd be happy to help you resolve them if any.
i asked this question because before i had only one form with card method and everything works
now i added the form to add the sepa_debit payment method and i run into this error:
the code its the same as card form that works before this
now the 2 forms doesnt work
same error on both
i try to explain it better,
can you share your example code for this?
I'm not sure I've seen something like this before ๐
so this is the code for the second payment element?
now i noticed that even the two payment elements doesn't work so its the same
but they are identical, only variable names change
i copied the snippet in the documentation and changed variable names
i think i solved this alone..
Oh nice! sorry juggling between a few threads at the moment.
What solved it for you?
don't know actually ๐
Ahaha np! As long as you're unblocked ๐
proably I found it: if i comment this the integration will work
when i create 2 setupIntents it give me the error i attached before
did you know why?
I cant say for sure but maybe elements don't like be initialized with two different client-secerts