#ratta-tha-vermin_api
1 messages ¡ Page 1 of 1 (latest)
đ 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/1339681891363586109
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello! It's difficult for me to say for sure without knowing a lot more, but it's possible you could have the same backend code handle submission for these two scenarios.
any chance you could help me figure out the best path? stripe's docs are very confusing here there's just so many routes you can go.
Have you looked at the Checkout migration guide? Does that screenshot near the top on the left look like what you're using now? https://docs.stripe.com/payments/checkout/migration
yeah i have looked at this. that screenshot is what we're using now.
I recommend starting with that guide and then going from there.
Hello, catching up as my colleauge has to step out soon. Have you decided on Checkout for your new UI as well? Or are you considering each of our UIs that can be embedded on a page? We do have saved card functionality for the Payment Element where you can show saved cards for a customer if they are a returning customer. I forget how that works for Checkout/Embedded checkout currently but am refreshing myself.
We'd like to embed the UI on a page we've built (the 'new subscription confirmation page')
That would be great if we could show saved cards on that page
can we do that using embeddable components instead of embeddable form?
You can do it for either. For the Payment Element, you can create something called a CustomerSession for the existing customer and pass its ID to the frontend (where exactly depends on which payment element integration you are doing)
https://docs.stripe.com/payments/accept-a-payment?platform=web&ui=elements#save-payment-methods
https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=payment#save-payment-methods
For Checkout (which can also be embedded on a page) we have settings for which saved PMs can be displayed. Trying to find if we have a doc that speaks to that in a bit more detail.
https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-saved_payment_method_options-allow_redisplay_filters
amazing!
But basically all PaymentMethods have a property allow_redisplay, and its value determines whether it can be shown when using the CustomerSession + Payment Element or Checkout Session when using the redisplay functionality
https://docs.stripe.com/api/payment_methods/object#payment_method_object-allow_redisplay