#abignalet-pi-dupe-charges
1 messages ยท Page 1 of 1 (latest)
Hello, we have a new behavior on our platform account. 1 payment intent which generates 2 charges, the first one failed and the second one succeeded. Is it a normal behavior?
ch_3JxJavDlpLzq27jH4IKa3lgu
ch_3JxJavDlpLzq27jH4Zi5AP5T
It looks like a retry mecanism of stripe
?
Hello, it's an expected behavior
@sleek cave ๐
๐ค
abignalet-pi-dupe-charges
Let me take a look
Yep, so as stated this is expected behaviour:
ch_3JxJavDlpLzq27jH4IKa3lguis the initial charge attempt of the PI โ where the bank requested authentication. This attempt failed and authentication was requested and handled via Stripe.jsch_3JxJavDlpLzq27jH4Zi5AP5Tthis is the 2nd charge attempt following the customer auth succeeded
Ok so our front end integration re-confirmed the payment and triggered the 3DS ?
Exactly! Stripe.js handled this (likely with confirmCardPayment)
Ok we did not do any custom things like this for the card confirmPayment case. (since it is handle by stripejs)
We did a custom one like this for apple_pay integration (like 2 confirms in some cases). Does it seems correct for you?
We did a custom one like this for apple_pay integration
I'm not sure I understand the question
for the classic card integration, we only do a single confirmPayment call, in this case it fails (bank requires auth). In the background with stripe.js, another confirmPayment is triggered thus generating the succeeded charge.
I was just wondering why isnot it the same with apple pay integration where we have to explicitely make 2 calls to confirmPayment in the case of requires_action
That's different as noted here:
Report to the browser that the confirmation was successful, prompting it to close the browser payment method collection interface.
So the initial confirmCardPayment will close the Apple Pay UI and the 2nd will handle any auth if required
Ok understood ty very much for clarification
Np!