#james_api
sweet matrixBOT
👋 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/1390433672997634170
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
solemn flicker
Hi there
If you already have a payment method and can therefore check its type (which you always would following this kind of flow), you can follow the advice in the error message and just pass payment_method_types
Does that make sense?
vague mist
Hi, I'll try that, thanks. I'm confused by the error message, though - why not just state that the parameters are incompatible? Seems like there's some nuance I'm not understanding.
solemn flicker
I think we want to guide you toward passing the correct parameter to get this to work if you get to this point - you can use errror_on_requires_action, you just can't use it on a PaymentIntent with dynamic payment methods. To which point - I get that this is a little confusing because we don't document this properly in our API reference. I'll flag that to our docs team
vague mist
Thanks @solemn flicker , managed a successful request 🙂
If I did want to allow dynamic payment methods, would automatic_payment_methods[allow_redirects] = "Never"
simply prevent any method of type card from working, since they may or may not require auth?
solemn flicker
no, that parameter is for payment methods that require redirecting to another page as part of their payment flow
but if you're creating/confirming a paymentintent on the backend in a single API call, automatic payment methods aren't really relevant, right?
vague mist
Ahh, I guess I was conflating the secondary auth portion of 3DS as a "redirect"
Some forms of card SCA auth DO redirect though, don't they?
solemn flicker
I'm not too sure about that - generally its a pop-up/modal
vague mist
Alright, thanks again for the help, It's been tough to wrap my brain around Intents and try to fit them into legacy design patterns