#tikitikitero88
slim depotBOT
Hello! We'll be with you shortly. 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.
- tiki-paymentintent-capture, 1 hour ago, 40 messages
keen atlas
Hi there 👋 can you summarize the current state of your question/concern here?
frozen wadi
I need to reopen the thread #1194387743355183154 message because I have extra questions
keen atlas
What are those questions?
Let's discuss them here. Reviewing the entire previous thread will take me some time, it's typically faster if you can summarize your questions in the new thread we start.
frozen wadi
Will this https://stripe.com/docs/payments/place-a-hold-on-a-payment-method work also in this scenario:
1 - Creating the Payment Intent first with confirm=false when placing the order.
2 - Then updating to confirm=true when the order is approved by a Manager (it can happen a few days after the order is created).
3 - And then capturing the funds when the order is shipped
In the scenario from the documentation you don't mention the confirm parameter. That is the reason of my question. Besides that, I want to confirm that the expiration time for the authorization will start when setting the payment intent to confirm=true (in 2) and not in 1 (with confirm=false)
keen atlas
Gotcha, you won't update the Payment Intent and set the confirm parameter (that parameter is only available when creating a Payment Intent). Instead you make a request to confirm it.
If you're confirming from your server, you can use this:
https://stripe.com/docs/api/payment_intents/confirm
For client-side confirmation, that would be done from stripe.js
Yes, the authorization is granted when you confirm the intent (not necessarily setting the confirm parameter), and the validity period for it begins immediately.
frozen wadi
Ahh ok
So it will be
1 - Create the Payment Intent first with confirm=false when placing the order. That will happen DAY 1 for example
2 - Then confirm the intent when the order is approved by a Manager using the https://stripe.com/docs/api/payment_intents/confirm API. it can happen a few days after the order is created. Let’s say DAY 5.
3 - And then capturing the funds when the order is shipped. Let’s say 5 days after the order as approved by the manager. So, in DAY 10.
In that scenario as the counter for authorization expiration will start when we confirm the intent and not once we created it, we will not have an error when doing the capture
Are we on the same page?
slim depotBOT
frozen wadi
Currently as we are setting the confirm to true on DAY 1 we are getting an error on DAY 10 when doing the capture
keen atlas
Yup, that sounds right, assuming you're working with a Payment Method type where the authorizations are likely valid for a certain amount of time. There are some like Klarna where that isn't how they work, that you may need to take into account. We talk about them more here:
https://stripe.com/docs/payments/place-a-hold-on-a-payment-method#auth-capture-limitations
frozen wadi
We are already using the auth and capture mechanism today. We just need to update when we start the counter for the authorization. After order gets approved not when order is created. So that is why we wanted to check that we can fix that situation using the confirm option.
So when we confirm the payment intent the authorization counter for expiration start and also that is that is the time when the money is hold for the customer. Right?