#jason02012023
1 messages · Page 1 of 1 (latest)
- The docs say "When Stripe requests 3D Secure and the attempt is: Unsuccessful-Stripe makes a final attempt to complete the payment without authentication.". Does that mean if the user fails 3DS, the charge would still retry without authentication?
For #1: I can't really comment on that part. I would recomend reaching out to support if you want a better answer https://support.stripe.com/contact/email
For #2: The charge is expected to process without 3DS in this specific case
Find help and support for Stripe. Our support center provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
Thanks @rough anchor. Is there a property e.g. on PaymentIntent or PaymentMethod that tells if 3DS is required?
If 3DS fails, then a card is not successfully authorized, which means that the Payment Intent will fall back to requires_payment_method and you would have to bring your customer back into the payment flow to either (a) present the 3DS authentication modal, or (b) re-enter their card credentials and authenticate via 3DS
Thanks, so before the PI falls back to requires_payment_method, it sounds like Stripe attempts one more time to try to complete the payment but without 3DS, is that correct?
It's a bit more complicated than that, but Stripe will essentially check to see if the card supports 3DS and proceed without it if 3DS is not supported
Why would it attempt 3DS in the first place if 3DS is not supported? In other words, my question is - in what circumstance (if any) does Stripe attempt to complete a payment without 3DS when 3DS was requested?
Why would it attempt 3DS in the first place if 3DS is not supported?
It wouldn't. Stripe confirms the card, then (if 3DS is required) it presents the card issuers auth portal
So what does this mean in the docs exactly?
When Stripe requests 3D Secure and the attempt is: Unsuccessful-Stripe makes a final attempt to complete the payment without authentication.
Hello! I'm taking over and catching up...
That means that if 3D Secure fails we try one last time to process the payment without 3D Secure because sometimes that works.
Ok thanks. Just to clarify, by "3D Secure fails", is that including the user failing 3DS themself? Or is this before the user even is redirected to the issuer's authorization page.
No, in this context it means we tried to start the 3D Secure process and that failed, so the customer wouldn't be asked to authenticate at all.