#wellthen ๐ช๐บ
1 messages ยท Page 1 of 1 (latest)
What product(s) are you using? Checkout? Payment Element? Card Element?
this should be checkout
I don't think you can force 3DS on Checkout, but also: 3DS is always performed when it is required on Checkout.
No, because with Checkout you don't handle the Setup Intent or Payment Intent, unless you're doing that yourself via a different workflow
Can you clarify what you mean by checkout?
I'm integrating Stripe via PHP, and loading Stripe's checkout page.
I'm creating a new session for each client by supplying the parameters.
Hi ๐
I'm stepping in at this point. If you are redirecting your customers to Stripe Checkout you do not need to worry about 3DS. The Stripe Hosted checkout page will take care of that.
Are you using Stripe Checkout?
Yeah, I generate a session via the Stripe PHP API, I fetch the checkout URL and give it to the user.
I assume that's stripe checkout?
Is there not a way to force 3DS even on checkout?
Not when using Checkout.
Gotcha. I assume that's why this dude couldn't get it to work? https://stackoverflow.com/questions/71209098/how-to-force-3ds-in-stripe
Yes. That individual is attempting to use a parameter that does not exist: https://stripe.com/docs/api/checkout/sessions/create#create_checkout_session-payment_method_options-card
How does Stripe determine whether to use 3DS on checkout? Right now when in test mode, I can't simulate a 3DS screen.
Can I make a recommendation to the team to add an option to force 3DS on checkout?
I believe the liability then shifts from merchant to client in cases of fraudulent charges.
I will share that feedback. In the meantime these are the cards you can use to test a 3DS challenge flow: https://stripe.com/docs/testing#regulatory-cards
Thanks. Also, originally I followed a video from a Stripe dev on YT to integrate the checkout, but I was told the redirectToCheckout() JS method is deprecated.
To avoid people from making the same mistake of integration, can it be updated?
I can make that recommendation.