jokamax

[slow fjord]

Yes it's normal. You don't need to handle the 3DK by suing the URL, you should just call stripe.confirmCardPayment and let Stripe.js to handle for you.

[lapis tide]

So I can't use in production, the way which work in development ? (to be sure)

Because in developpement we have : "next_action": {
"type": "use_stripe_sdk",
"use_stripe_sdk": {
"type": "three_d_secure_redirect",
"stripe_js": "https://hooks.stripe.com/redirect/authenticate/src_1NuscsHagJ8u1cfkMf1DAwiv?client_secret=src_client_secret_ZvXTN2JQjNxXMQh8SWFQcHre&source_redirect_slug=test_YWNjdF8xTUNpVVJIYWdKOHUxY2ZrLF9PaUpGbmprU0t2MzFUSzZLeWk3MThiNG5QSmlEUHR10100qfLU0xoX",
"source": "src_1NuscsHagJ8u1cfkMf1DAwiv"
}
},

this work well in dev. Not possible to have the same thing in production ? (we saw that we never have this "stripe_js" field with url, maybe a problem in production ???)

[slow fjord]

It really depends on the next_action.type (https://stripe.com/docs/api/payment_intents/object#payment_intent_object-next_action-type) . If the type is redirect_to_url, then yes you can manually redirect your customer to the URL. But the recommendation is to use stripe.confirmCardPayment so that it can handle both redirect_to_url and use_stripe_sdk

If you want to experience next_action / use_stripe_sdk / stripe_js it in test mode, set use_stripe_sdk to true when creating a PaymentIntent

[lapis tide]

Ok thanks

If I set "If you want to experience next_action / use_stripe_sdk / stripe_js it in test mode, set use_stripe_sdk to true when creating a PaymentIntent" in PRODUCTION : it'll work and fix (temporary) my problem ?

[slow fjord]

I believe using stripe.confirmCardPayment will solve the problem