#hume-jacob_api
lost waveBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1338579341553963110
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
mighty fiber
Hello! We have details about how to show saved payment methods in Checkout here: https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=stripe-hosted#save-payment-methods-to-prefill-them-in-checkout
median zealot
So that setting makes it so that if a user creates a payment method in Checkout, then it would get saved, right?
mighty fiber
Yes. The details are in the doc I linked to above.
median zealot
But if I have a payment method that was associated to that user, that had been created via a different, non Checkout method, it'd need to have been saved with the flag enabled (something like this field: https://docs.stripe.com/api/payment_methods/object#payment_method_object-allow_redisplay )?
mighty fiber
Yep.
median zealot
There isn't an easy way to backfill that setting for those payment methods, is there? We'd be talking about getting all my users, getting their payment methods (with this endpoint: https://docs.stripe.com/api/payment_methods/customer), then updating any payment methods using https://docs.stripe.com/api/payment_methods/update, or some similar flow?
mighty fiber
I think you probably meant/want https://docs.stripe.com/api/payment_methods/customer_list instead of that first link in your last message, but yes, that's how you'd do it. Note that you likely need explicit permission from your customers to do this, it's not something you can decide to set for them. The doc I originally linked to mentions that this is goverened by card network rules and data protection regulations.
There's more info here as well: https://support.stripe.com/questions/prefilling-saved-cards-in-checkout
median zealot
Alright, final question: nothing special needs to be done to show payment methods associated with the user for Checkout sessions, assuming that the allow_redisplay flag has been set for that payment method, right? as https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-saved_payment_method_options-allow_redisplay_filters is defaulted to always?
mighty fiber
Yeah, if a customer goes through Checkout and enables the save for reuse option in that UI the saved Payment Method should have allow_redisplay set automatically to the correct value (always) when the Payment Method is created.
median zealot
Alright, thanks for your help.