#Greg-paymentelement
tardy pebble
hi! not right now, no.
that's unfortunately UI you have to build yourself for the most part by calling https://stripe.com/docs/api/payment_methods/customer_list on the backend, and parsing it to a list of card in your frontend
when the user picks one you can call https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-existing for instance, instead of using the PaymentElement
warm orchid
but what about other payment methods, like klarna etc. Would i need to build separate UI for them ?
tardy pebble
Klarna payment methods can't be saved so I don't quite follow
warm orchid
yes, i know. But we are using the Payment element to support multiple payment methods. So if i build custom UI for CC, how would other payment methods work ? Should i build custom UI for CC and use Payment Element for the rest of payment methods ?
calm cargo
Hey, apologies but I missed this thread for a bit. You can use the Payment Element for CC + those other payment mehtods. If you are using the Payment Element, there is no reason to build a seperate CC UI unless you want it to be a completely seperate part of the page
warm orchid
but how can i display(and use) saved CC on the PaymentElement ?
as karllekko said, it's impossbile
calm cargo
Ah, I misunderstood your question. Then yes, you would want a Payment Element as well as your own custom UI that lists saved payment methods that you have for the user
warm orchid
is it planned to support displaying saved CC on the PaymentElement in the future ? i think it could be very useful