#bananasop_unexpected
harsh socketBOT
👋 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/1242418134401552464
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
earnest kelp
Can you share an example?
exotic wyvern
Yes, this is the instance I've encountered: pi_2PHlJeYcNkb4llAk1Y84h6CB
earnest kelp
Where do you see status: 'processing'? In a webhook event? API response?
exotic wyvern
In API response. After the customer gets redirected back to our website once they complete or fail the 3DS check, I retrieve the Payment Intent from the API and check the status to know how to proceed. Is here that I got processing.
earnest kelp
Can you share the req_xxx ID and JSON?
exotic wyvern
I don't have a request id for the call to retrieve the Payment Intent, but since it was in an invalid state, the system immediately tried to cancel it. The request id for it is req_h08znlftecXwhS and the JSON response is
earnest kelp
Yeah, processing is an intermittent status for card specific to capture_method: 'manual' that you're using:
If you’re separately authorising and capturing funds, your PaymentIntent can instead move to requires_capture. In that case, attempting to capture the funds moves it to processing.
https://docs.stripe.com/payments/paymentintents/lifecycle#intent-statuses
exotic wyvern
Ah, I see. Thanks!