#suhwanggyu
icy elk
idle sparrow
hello! maybe lets take a step back here, what's your aim here? What are you trying to do at each status? Or why do you need to know of all conditions?
For context, most of the time, you'd only want to be aware that the customer has completed the Checkout Session and whether the PaymentIntent can be captured
modest falcon
In the way I sell products, for customer convenience, I lock product inventory as soon as a session opens. (in my case, step 1)
Our product has the characteristic of being difficult to cancel transmission from the moment it enters the transmission flow.
To transfer locked inventory after payment is captured,
- create check out session (manual capture)
- call capture payment intent
when the response of step 2 is 2xx HTTP Status, I wonder if it is possible for the status to be processing rather than succeed.
Due to other previously linked payments, we are first considering performing the capture method manually before applying the webhook method.
idle sparrow
what does we are first considering performing the capture method manually before applying the webhook method. mean?
to be specific, what webhook method are you applying?
modest falcon
I know the below method to handle checkout.
PLAN A) create session and callback by checkout.session.completed
PLAN B) create session(capture manual) and call capture paymentIntent
We'd like to choose Plan B.
Is there a problem if I don't subscribe checkout.session.completed with Plan B, but simply determine success with 200 status(on capture paymentIntent api)?
Thank you so much for your detailed review.
idle sparrow
i can't remember off the top of my head if there are any payment method types that will move into processing status first, before transitioning into requires_capture. Regardless, if you don't want to listen for checkout.session.completed, you could listen for payment_intent.amount_capturable_updated webhook event instead and then capture the amount for that PaymentIntent
modest falcon
When calling capture payment Intent api for paymentIntent in require_capture state, Is it okay to understand that credit card, Apple pay, and Google pay (non-delayed payment methods) will not be changed to requires_capture -> processing status?
(I expect requires_capture -> succeeded)
idle sparrow
requires_capture will never transition into processing
modest falcon
Oh! I see
idle sparrow
yes, it'll be requires_capture -> succeeded