#nstripe_paymentintent-returnurl
deft summitBOT
š 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/1263605261348638843
š Have more to share? Add more details, code, screenshots, videos, etc. below.
grim python
nstripe_paymentintent-returnurl
@knotty grotto let me have a look. confirmation_method: 'manual' is highly discouraged and really for legacy integrations so my advice would be to move away from this entirely
Otherwise the best approach is for you to explicitly configure the list of payment method you want to support. I see you are explicitly passing payment_method: 'pm_123' and it's a card. If you only use card payments, the simplest approach is to pass payment_method_types: ['card'] instead to disable "dynamic payment methods"
Also: do you have an example request where you tried that allow_redirects? I'm trying right now and it seems to not error for me
ugh I forgot to pass confirmation_method myself š¤¦āāļø
So yeah because confirmation_method: 'manual' is card only, the best approach is really to just force card
knotty grotto
confirmation_method: 'manual' is highly discouraged and really for legacy integrations so my advice would be to move away from this entirely
Yea, we're using this as part of our original integration to finalize payments on the server. Is there a guide you can point me to that still allows for this flow in a different way? Or is finalizing payments on server itself a legecy integration approach?