#ssbb_setupintent-redirect
hardy schoonerBOT
đ 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/1232008599799205920
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
open ferryBOT
plain leaf
Not that I am immediately aware of but I will look and get back to you.
ebon pulsar
Thank you!
ebon pulsar
Checkout docs (https://docs.stripe.com/payments/checkout/custom-redirect-behavior) mentions debit-based methods as a redirect-based method but actually as far as I can tell all intercations happens in Stripe widget and actually it works just fine with if_required redirect
Basically we have a large form and then a payment widget at the end. With the old code we were using Plaid for bank accounts and sources/charges on Stripe side. So previously we always sent tokens with a form and never managed "not paid" state. Payment is succeeded or not (or pending in case of ACH).
So now with new redirects we need to save data in some "draft" state and postpone processing until setup intent succeeded. And then add some handler to remove obsolete drafts, etc. etc.
So just want to see if we can avoid it and keep the old behaviour
plain leaf
Yeah that is strange. I am wondering if that is referring to bank redirects, but it may just be the case that this varies by bank for debits. I've reached outt o my colleagues about this https://docs.stripe.com/payments/payment-methods/integration-options#additional-api-bank-redirects
open ferryBOT
ebon pulsar
Yeah I see. We going to use "ACH Direct Debit" only I think (as an alternative to old Plaid code)
fast mantle
ssbb_setupintent-redirect
plain leaf
ACH specifically should not need a redirect from what we can see. Checkout has a never option for redirects that fully gets rid of redirect-based payment method and ACH is allowed when using that setting https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-redirect_on_completion
ebon pulsar
The page you linked first actually what I was looked for
So it says No for all the Card, Apple Pay, Google Pay and ACH Direct Debit so I think I can ignore it for now
fast mantle
yep that sounds reasonable