#benign-gorilla_api
steel dragonBOT
đ 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/1342054452332462162
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
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.
- benign-gorilla_api, 2 days ago, 5 messages
west tiger
Do you mean you would like to collect the payment method first, then create the payment intent later?
pulsar ravine
Yes, that is how we currently do it but it is all in the UX
west tiger
If so, I'd recommend using deferred intent flow: https://docs.stripe.com/payments/accept-a-payment-deferred
pulsar ravine
Thanks, this is still binding the elements session to the pi rather than the pi to the elements session, but maybe that is the best way. I was looking to expore if I could do this in fewer stages, e.g. client collects payment info server generates and submits pi : Rather than client collects payment info server generates client binds elements session to pi
steel dragonBOT
lusty dew
hi! I'm taking over this thread. give me a few minutes to catchup