#evelin-3ds-questions
1 messages · Page 1 of 1 (latest)
evelin-3ds-questions
For #1 The best approach for this is to use payment_method_options[card][request_three_d_secure]: 'any' as a parameter to require 3DS but it would still bypass it if the card doesn't support 3DS. So you should also use manual capture so that after the successful payment you can look at the resulting Charge's details. Specifically you want to look at the payment_method_details[card][three_d_secure] property which contains details about the 3DS authentication. If it succeeded, capture the payment, if it didn't, refund it and explain why.
Overall though it's going to hurt your conversions a lot in that case
For #2 you want to read https://stripe.com/docs/payments/3d-secure#disputed-payments
For #3 yes I think so
Those questions are better directed to our support team though: https://support.stripe.com/contact
if the card doesn't support 3DS, would we still be "protected" (liability shift) or are we consuming the risk