jogui_code

[tough oriole]

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1229426298452181083

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[royal verge]

Hi 👋 that is a required field as the Payment Element was designed to support a wide array of payment methods, including those that require redirects.

When creating your intents you should tightly restrict the payment method types that are supported to only ones that won't impact your flow. Then when confirming the intent client-side you'll still need to pass a return_url, but shouldn't need to hit it. You can also set redirect to if_required in that confirmation call to further reduce the likelihood of a redirect happening.

[glass cairn]

Nice, then you can confirm that if i put

        paymentMethodTypes: ["card"],   in the options of the stripe Elements and redirect to if_required in the setup thats it

it wont redirect otuside, only will do 3dsecure inline modals like card element like always

[royal verge]

Yup, that's what you should see in your testing.

[glass cairn]

and how safe is this, will stripe change this behaviour in the future?

I fear someday it starts executing return_url everywhere :/ with cards

[royal verge]

That's an understandable fear. I wouldn't expect it to change anytime soon, but I can't say it never will, or when it would if it does.