#johan_docs
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/1403022965854961686
đ 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.
- johan_unexpected, 6 days ago, 27 messages
Hi, that flow you shared, https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=payment would work in this case. After you collect the payment method details, you can look how much inventory you have in your system to then determine if you want to create the PaymentIntent or not.
the problem with this is that we might have inventory but what if two customers purchase at the exact same time? there could be a customer that is currently purchasing tha last booking using an SCA card and that would delay the order fulfilment. then in that time where there's another customer looking to book the same class out inventory still says that there's one spot available even though our SCA customer that came before is still trying to complete the SCA authentication
should the paymentIntent be created with a confirmation_method set to manual, then run our validations and then capture the paymentIntent if the validations passed?
I would not jump into that conclusion as there are some payment methods that are not supported with that flow: https://docs.stripe.com/payments/place-a-hold-on-a-payment-method#auth-capture-limitations. Stripe does not have have an inventory management system like you imagined.
You can instead check inventory before you render the checkout page. When someone else clicks on the checkout page, you can show they can be added to a 'waitlist' or something like that so in case the payment fails with that customer, you can still present the option to the customer who is on the waitlst.