#intel_paymentintent-manual
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/1263180890582945873
đ 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.
- intelagent_api, 19 hours ago, 19 messages
- intelagent_checkoutsession-custompayment, 2 days ago, 9 messages
@tall bough honestly, we highly highly recommend never doing that. This is brittle and you're going to end up with various edge-cases over time and regret it completely.
But if you really have to you should use confirmation_method: 'manual' which always requires an extra confirmation server-side and it will work even after 3DS. See https://docs.stripe.com/api/payment_intents/create#create_payment_intent-confirmation_method
But it is mostly only compatible with card payments
intel_paymentintent-manual
Hey sorry I'm here just thinking about this.
I'd rather not do that, especially if it isn't recommended. But I'm not sure of alternate approaches?
When you say highly recommend never doing that what exactly are you referring to? The manual confirmation I assume but want to be clear
Yes. We recommend never trying to get to a state where money movement only happens after an explicit server-side operation. That's discouraged and that prevents you from using almost any payment method other than card
Ok interesting, that's helpful to understand. If I hold inventory while a payment is processing, I need to somehow release the hold on that inventory when a payment doesn't go through for whatever reason. I guess the payment intent webhooks can be used for that.
yes and you can have also a "max time" where after the time passes you can for example cancel the underlying PaymentIntent so that even if they finish 3DS after, the confirmation will fail and we'd show an error