Ying

[umbral cedar]

This issue occurred when our user tried to add a payment method (based in Europe)

[molten fable]

If this is a general issue, you may be missing a the return url for your iOS app. If this is a single customer, they may need to contact their bank to ask about the 3DS flow and why the authentication was failed.

I'd suggest contacting our support team with the payment intent ID for any help investigating when you have more info from your customer: https://support.stripe.com/contact

[umbral cedar]

Thanks for the suggestion - it's not a general issue, but only happens to some users. I will send the email

[umbral cedar]

(I sent an email with the transaction id for investigation) can I follow up with a more generic question: when adding payment methods, we would use setup_intent. Currently in Europe, setup_intent would always trigger the 3DS auth UI because of SCA. Does setup_intent have an option to not trigger the 3DS auth UI when adding the payment ? I am curious.

[molten fable]

Requiring 3DS or not is at the discretion of the issuer, you cannot control that no

You can opt-in to request it more often, but this is still up to the bank to require or not

[umbral cedar]

I see. The reason I asked was because, I tested adding the same card on several apps. Most of the apps prompted the 3DS auth UI, and one or two apps didn't. Which made me wonder if the latter was doing something different

[normal path]

Gotcha. So yes, some of the apps may have been doing something different to request that the bank do 3DS more often, and some of that may have been luck of the draw based on the bank's decisionmaking.

[umbral cedar]

I see.