#_api
void vaporBOT
đź‘‹ 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/1273671038890410037
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
glacial stratusBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- _api, 35 minutes ago, 30 messages
- _customer-portal, 2 days ago, 7 messages
lament cave
the _api is the previous discussion i was having with a stripe cs person. the thread was closed before my issue got resolved
wispy plume
Hello! Can you explain exactly what you question is about? You say "don't persist" but what does "don't persist" mean?
lament cave
I fill payment details in checkout session A, when i create checkout session B the payment details I filled out in A are not there
wispy plume
That's expected behaviour, we don't really prefill the card details anymore unless you actively pass allow_redisplay. You should read https://support.stripe.com/questions/prefilling-saved-cards-in-checkout carefully first
But my advice is to give up on that part of the feature, it is brittle and not really helpful. If you want pre-filled card details, use Link instead https://stripe.com/payments/link
lament cave
in the previous thread, the customer service agent said it was possible
You just need to pass the customer id to prefill the payment method
ID of an existing Customer, if one exists. In payment mode, the customer’s most recently saved card payment method will be used to prefill the email, name, card details, and billing address on the Checkout page. In subscription mode, the customer’s default payment method will be used if it’s a card, otherwise the most recently saved card will be used. A valid billing address, billing name and billing email are required on the payment method for Checkout to prefill the customer’s card details.
wispy plume
Correct it is, if you read carefully that exact support article it explains it
But again, I'm an expert at our products and APIs and I am advising you to not bother doing this. It is brittle, end user can opt out, and it is really just a waste of your time. Use Link instead
lament cave
Link really doesn't solve our use case, so we were hoping to do it with checkout sessions
wispy plume
Link solves your use-case. Link is a simple way for the end customer to save their card details with Stripe for quick checkout in the future. When they come back to a Checkout Session later, they will have a cookie identifying them and their card details prefilled. It is the right way to do this.
lament cave
There is something checkout session allows us to do that Link would note