dsaldeno

[heady minnow]

Hi there 👋 a couple things:

1. That is a real scenario that could happen that your flow should be prepared to handle. When you use a Setup Intent to setup a payment method for future usage, we do everything we can to not require 3DS challenges for future payments, but ultimately the issuer decides whether they require authentication for any given transaction. So it's possible your customers will need to complete 3DS twice.

2. If you're using a test card that always requires 3DS (like the 3220 card), then our test flows will always require 3DS to be completed.

[coral gale]

1- Yes correct.
2- Yes, I am using test cards that always requires 3DS (like the 3220 card). Is there a way that the authentication can be done or Stripe recorded as done when the User is adding the card? It seems that when adding the card and doing the 3DS authentication Stripe (at least on the test mode) doesn't record this as done or does anything about it. It's only when placing the order that looks into it.

[heady minnow]

It does record it, but the 3220 card simulates an issuer always requiring the customer to complete an authentication challenge, so it's expected behavior for that card to always trigger a 3DS challenge. I would recommend trying the 3155 test card, which only requires authentication when it hasn't bene previously set up, to test whether setting a payment method up is behaving as expected.

[coral gale]

I see, understood. Thanks for the information.
Two last question.

1- Confirming this card is 4000 0000 0000 3155

2- After implementing the Stripe UI with PaymentIntent when adding the credit card it autocatically takes you to the 3DS page (Stripe seems to do it automatically). However, when placing the order the User is not being re-direct it to the 3DS pop-up for authentication. Is there a guide or steps to follow to make sure the 3DS pop-up appears when placing the order the same way it does when adding a card?

[heady minnow]

Can you elaborate on what you mean by "placing the order"?

[coral gale]

So for example, in this screen the User adds a card (which in case is needed Stripe will automatically prompt a 3DS pop-up for verification) after the card is added the User can press "request to book" (place order). At this time is that the "payment started" and payment process starts however if it requires a 3DS it does not redirect to a pop-up the same way it does when adding a card.

[heady minnow]

What is your request to book button doing there? Is it confirming a Payment Intent, or doing something else?

[coral gale]

I believe is confirming a PaymentIntent. When pressing "request to book" that is when Stripe creates "payment started" and the payment process starts.

[heady minnow]

Hm, usually that means the 3DS challenge was triggered, but wasn't completed. Is the "Request a Book" button something you built, or is it provided a third-party integration that you're leveraging? I'm asking as you sounded a bit unsure of what it did.

Can you copy the Payment Intent ID from the top right of that page, and paste it here so I can take a closer look?

[coral gale]

Request to book button is something we built not using a third party here.

Here is the Payment Intent ID: pi_3NzWjtGIcDWf4swC03lrSjvr

[heady minnow]

Hm, interesting, I'm not seeing evidence that 3DS was started there. The reason for that, is because the request to confirm that Payment Intent was also the request to create it:
https://dashboard.stripe.com/test/logs/req_d6McTmafoXgdY7
that was made from server-side code, which can't automatically present the 3DS challenge because it's not exposed to the customer. That has to be done from client-side code.