#niteeshvparticipant
1 messages ยท Page 1 of 1 (latest)
handleActions: false is to handle 3DS manually in your system. It doesn't stop 3DS from happening
I'm afraid it's not possible to stop 3DS as card issuing bank may request it
is there anyother ways ?
As mentioned earlier, 3DS is requested by the card issuing bank (not Stripe). It's not possible to prevent 3DS
but handleActions: false is working on 4000000000003220 this card
Can you share the example Setup Intent ID (seti_xxx) made with 4000000000003220?
yes
const payload = await stripe.confirmCardSetup(clientSecret, payment_method, { handleActions: false });
if (payload.error) {
} else {
if (payload?.setupIntent?.status === "requires_action" && payload?.setupIntent?.next_action?.use_stripe_sdk?.three_d_secure_2_source) {
this.setState({
paymentMethod: null,
errorMessage: "Card with 3D Secure Authorization cannot be used. Please use a different card.",
});
}
else {
this.setState({
paymentMethod: payload.setupIntent.payment_method,
errorMessage: null,
});
}
}
}
};
I'll need Setup Intent ID (seti_xxx) with 4000000000003220 to check why 3DS didn't happen
Ideally, 4000000000003220 should trigger 3DS
In any case, it's not possible to stop 3DS from happening
Thanks for waiting! Discord is busy now
ok ๐
but when I use 3DS2 test cards , I am not getting the 3ds popup
sry
ut when I use 3DS test cards , I am not getting the popup like when I use 3DS2
Can you share the Setup Intent ID (seti_xxx) that you used 3DS test card, so that I can check why 3DS wasn't shown?
ok
{
"id": "seti_1Nt3VfojEYdp",
"object": "setup_intent",
"automatic_payment_methods": null,
"cancellation_reason": null,
"client_secret": "set5QV",
"created": 1633458,
"description": null,
"last_setup_error": null,
"livemode": false,
"next_action": null,
"payment_method": "pm_1Nt3T7Lt7oSplF8Ji7mOcCXK",
"payment_method_configuration_details": null,
"payment_method_types": [
"card"
],
"status": "succeeded",
"usage": "off_session"
}
is it a one
you are asking
Thanks for sharing. As per checking 4000000000003220 can be acting weird sometimes in test mode.
To test 3DS authentication, this set of 3DS test cards should be used instead: https://stripe.com/docs/testing#regulatory-cards
Back to your original question, your integration should support handling 3DS as it's not possible to disable 3DS
ok thanks
No problem! Happy to help ๐