#binodkafle
mellow loomBOT
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.
- binodkafle, 22 hours ago, 7 messages
earnest mist
hi again!
Not sure I really understand the problem you're facing. If you're integrating that way, you would re-confirm based on the promise from calling handleCardAction on the frontend resolving. You call that, when it returns a result, you call your backend and confirm again.
Payment is processed at the initiation of the call and is confirmed upon successful termination.
overall that doesn't really make sense to me, you shouldn't be extending a single payment over hours like that, it's like you are (ab)using the manual confirmation feature for this. It sounds like a really strange way to use the API.
the correct way to do this is something like fully authorise the payment upfront(create PaymentIntent, confirm+do 3DS, confirm again if needed), and then capture it later at the end of the call.
https://stripe.com/docs/payments/place-a-hold-on-a-payment-method
fathom haven
overall that doesn't really make sense to me, you shouldn't be extending a single payment over hours like that, it's like you are (ab)using the manual confirmation feature for this. It sounds like a really strange way to use the API.
I have implemented this flow as it is necessary to authorize (place a hold) on the payment for the entire 3-hour call duration initially. Subsequently, the actual amount is confirmed based on the call's duration after it concludes.
earnest mist
yeah but what you have built is not authorising the payment. No funds are held or any transactions take place on the customer's bank statement while waiting for 3D Secure to complete, that only happens when the second confirmation API call succeeds.
if you want to the authorise the payment(hold the funds from the customer's card so you can capture them in a guranteed way later), you need to fully confirm the PaymentIntent per the way I suggested above. You need to move the PaymentIntent into the requires_capture state, which means creating the PI, confirming it, fully handling 3D Secure(and doing that includes the extra confirm call if you're using confirmation_method:"manual"), which authorises the payment. If using capture_method:"manual" then after doing those steps you have fully authorised the amount on the customer's card and can capture them later at any time in the next 7 days.