#Aamir
1 messages · Page 1 of 1 (latest)
Hi there
Hi
sure, one sec
function confirmStripe(client_secret,url){
stripe.confirmCardPayment(
client_secret,
{
return_url: url
},
// Disable the default next action handling.
{handleActions: false}
).then(function(result) {
alert(result);
if(result.paymentIntent.status === 'requires_source_action'){
$('#3did').attr('src',result.paymentIntent.next_action.redirect_to_url.url)
$('#3dconfirm').show();
}
});
}
client_secret and url can be seen in browser debug
Okay and are you testing 3DS here?
yes
Can you provide a PaymentIntent ID that you are testing with
Okay so that PI never was confirmed at all client-side
Ah the first one was
But not the second
Looking at the first, one sec
ok
Okay so that first one successfully went through 3DS
So your promise did resolve
And it went through your code: if(result.paymentIntent.status === 'requires_source_action'){ $('#3did').attr('src',result.paymentIntent.next_action.redirect_to_url.url) $('#3dconfirm').show(); } }); }
So looks to be working fine
you think it should work
I mean you don't see any issue in payment intent?
Not for pi_3MZbQUHmasT8jH4F1ESaBeP3. You can look in your Dashboard and see it is succeeded: https://dashboard.stripe.com/test/payments/pi_3MZbQUHmasT8jH4F1ESaBeP3
Ahh okay I see the confusion here
This went through an "attempt acknowledged" 3DS
So it never actually needed to manually complete 3DS
But yeah it still went through the whole process fine
The reason it did that is because you have request_three_d_secure: "any", set on your PI creation
I think we need to give other credit card where it is needed to confirm