#Benoît
void cedar
static girder
requires_confirmation is... indeed await for a confirmation call. If you see a confirmation api is called, it shouldn't be in that state
if you want to look closer, please provide the PI id pi_xxx
half olive
Thank you
The ID is "pi_3NNrbVAYYvne95SH22cRBT3t"
Here was my invoice process
The requires_confirmation status was returned by the selected call line in my screenshot : "POST
/v1/payment_intents/pi_3NNrbVAYYvne95SH22cRBT3t"
Maybe with the direct event link it will be easier for you : https://dashboard.stripe.com/test/logs/req_rmdpMyJCXCXYEJ
I can easily reproduce all this steps if you want/need me to
static girder
By the time of req_rmdpMyJCXCXYEJ the PI was just updated with a new Payment Method, so it's expected to be in requires_confirmation status. Only after you call /confirm endpoint, it will be transited into success or fail
https://stripe.com/docs/payments/paymentintents/lifecycle for more explanation, but I think this is expected
static girder
Waiting for user action != waiting for confirmation
Every card needs confirmation. Waiting for user action is about the requires_action status with 3DS
half olive
Ok, but i don't understand why i didn't have any problem until now with this card
So, I have to add a step in my process :
- If
requires_confirmation, then i must callconfirm - If
requires_action, then i use my 3D Secure usual process
static girder
Yes correct. when you say you didn't have any problem, how was it before? Like you didn't call confirm but the PI is still confirmed
Would be easier if you have any previous PI Id to compare
half olive
Unfortunately, i don't have a previous PI ID to compare, because i removed all the Stripe Customer where my previous tests were done
But yes, i never had to confirm a PI with this credit card. Maybe it was done behind the scene
static girder
Yeah believe it was done behind the scene, or if you create the PaymentIntent with confirm: true
half olive
Nope, i just create an invoice, and finalize it, without any options
static girder
Probably you called Pay Invoice? Hard to tell without looking at it
half olive
Yes, i called pay !
And i don't no more, because i now conditionalized pay call
That was the change that made the difference !
Ok, i have a new error because i try to pay a PI that was previously confirmed
static girder
That's also expected. A PI can't be confirmed twice
half olive
Ok