bernard.eugine

[supple jay]

well the web integrations don't retrieve cards at all. So it's just how it works, the ephemeral key is used to access details/payment methods of a specific customer so our mobile SDKs can display/manage them.

[sweet night]

Oh ok. So, how does stored payment methods of returning customers displayed on Web?

get displayed*

[supple jay]

they don't

if you need that functionality it's generally something you build custom in your own site

e.g. you might call https://stripe.com/docs/api/payment_methods/customer_list on your server and render the details in a UI on your web page

[spark yew]

So even (Save your card) consent has to be done in our webpage?

Is there any way to render the masked card details within the sdk?

[supple jay]

not sure what you mean by consent exactly, can you elaborate?

[supple jay]

which SDK? if you mean the web, then no, you'd call https://stripe.com/docs/api/payment_methods/customer_list on your server and render the details in a UI on your web page(the API call returns things like the brand/last4 which you can can use to show some list of saved cards with radio buttons or whatever, and call https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-existing for example when one is picked)

[spark yew]

I meant if I have to take the customer's consent to save their card, do I do that on my app itself?

And if this customer returns later, is there a way to render their masked card details?

[viral vigil]

Hi! I'm taking over this thread.

I meant if I have to take the customer's consent to save their card, do I do that on my app itself?
Ye you can save a customer's card, either while making a payment or without, depending on your needs.