#jack_checkout-savedpms
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/1282770496668041227
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
jack_checkout-savedpms
@lilac frost It is possible but it is really complex and brittle because you have to have asked for permissions upfront, stored it on individual PaymentMethod objects (or you might break important legal/compliance rules), etc. There are also strict criterias such as having a full billing address stored on it, etc.
It also only shows one and only cards.
Overall, my advice is to move on and not try to make it work. Instead, focus on supporting Link which is our own wallet/payment method which works way better: https://stripe.com/payments/link
But the cards are visible in the payment methods of the customer portal, how can it break compliance to surface them at the checkout for my logged in users? This feels like it should be a solved usecase
the CustomerPortal works completely differently and is built differently. What I am saying is that you shared an example code where you passed saved_payment_method_options: { allow_redisplay_filters: ["always"], } which can break some rules and it's best to steer clear from it
So basically this isn't possible with Checkout?
correct you can't do the same thing as the CustomerPortal
So what does payment_method_save do then? I can use that, but I still can't see the payment method as an option on checkout
Looking in to this. Having trouble finding exactly where that allows a PM to be displayed again
payment_method_save does save a PM that can be saved properly to potentially be the one card that is redisplayed on a later session. I think the point earlier is that it is possible but at the moment there are a lot of restrictions that can make it very difficult to work with.