Scular-3DS

[past sonnet]

Hi there!

So if I understand correctly: you use a Checkout Session to save a card, and that requires 3DS. And later when you want to reuse the card, we ask again for 3DS?

[merry bobcat]

yes

[past sonnet]

Are you doing this in test mode or live mode?

[merry bobcat]

both same

[past sonnet]

So basically this is expected. It's the bank that decides wether or not to ask for the 3DS flow. Sometimes the bank might not need it, and sometimes it will ask for it. So your code needs to handle both cases.

In test mode we have cards that always require 3DS (like 4000002760003184), and card that only require it once when you set it up (like 4000002500003155).
You can see all our test cards here: https://stripe.com/docs/testing#authentication-and-setup

[merry bobcat]

Okay I understand. If I pay $1 after the add credit card and user approve 3DS, it will ask 3DS for future payments again?

[past sonnet]

This is completely up to the bank unfortunately. So the customer might get a 3DS flow.

[merry bobcat]

Okay thank you.

[merry bobcat]

so in this case, is there no way to finish the payment process because users are offline they can't confirm 3DS. do you have any advice? Should they add 3DS disabled credit card? (I don't know if there is such a thing)

[past sonnet]

So that's something you need to handle: if an off session payment requires 3DS, then you need to notify your customer to come back to your website/app, and then confirm the PaymentIntent on the frontend using https://stripe.com/docs/js/payment_intents/confirm_card_payment#stripe_confirm_card_payment-attached