thefyrewire_api

[ebon basin]

👋 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/1402652179386470414

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

[storm adder]

Hi there 👋 either works. You don't need to re-confirm the payment client-side, but you can and it should work. Let me know if that doesn't align with what you see in testing though!

[raw thistle]

Thanks! That does line up with what we're seeing, but we just weren't sure if it was good or bad practice to confirm it on the server and then client-side again, and if we should be using next_action instead

Are we correct in thinking that using both confirmPaymentIntent and confirmPayment will both automatically handle all types of payment methods?

[storm adder]

Depending on the payment methods you're using, and what other settings are turned on in your account, yeah.

Like it'll easily handle syncronous flows like 3DS challenges or instant bank verification via Financial Connections, but if you're accepting bank debits and using microdeposit verification, for example, you may want to double check that you have a flow to handle customers coming back to complete the microdeposit verification. Whetther that's using our email features or your own flows.

[raw thistle]

Gotcha, thank you!