#xaositect_best-practices
warm zephyrBOT
đ 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/1384224395492458588
đ 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.
- xaositect_docs, 3 days ago, 26 messages
placid idol
Hi there!
round swift
We meet again, with more questions about checkout
placid idol
Indeed!
I'd imagine in your existing flow, if you're doing multiple PaymentIntents per "session" on the client, you are probably doing something like collecting payment details and confirming Payment Method, saving it for future usage, and then creating/confirming n PaymentIntents on the backend with the understanding that your customer knows what they're paying for
round swift
Yeah, that's about the size of it. We do setup intents for user gestures for 'scheduled' payments, but otherwise as you describe
placid idol
So conceptually, SetupIntents are for collecting Payment Method details without collecting a payment at the same time. PaymentIntents can also optimize a Payment Method for future usage with the setup_future_usage parameter. So you would use that parameter with the Checkout Session you create, and then you can create/confirm PaymentIntents on the backend same as before
round swift
So like:
... create the session with the setup_future_usage param, capture the session, and then when the session comes back in completion url, create payment intents and capture them as previously.
Okay, that seems reasonable. I was thinking this https://docs.stripe.com/payments/multicapture but it seems to only work for cards.
Thank you!
I'll report back to our team. Oh writing tickets, my favorite job.
placid idol
Yeah, I think one of the classic use cases for multicapture as a concept in online card payments is really big retailers that take orders (REI, Dick's Sporting Goods, Target, what have you) and then authorize the total amount and then see what they can capture out of that authorization (ie how much product they have to fulfill the order with and where the product is)
round swift
That makes sense, and isn't really what we're trying to do, since we are just the middle man and not responsible for fulfillment.