trashboat_api

[grizzled crystal]

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

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

[golden falcon]

Hey there

Unfortunately ACSS Debit is not currently supported in the deferred intent flow. We call this out in our docs here: https://docs.stripe.com/payments/accept-a-payment-deferred?platform=web&type=payment#enable-payment-methods

[frail trail]

thank you @golden falcon, is there any way to accomplish this flow while still confirming the payments on the server?

[golden falcon]

Unfortunately not with Payment Element, no.

You would need to support it as a separate option with your own UI and then create the PaymentMethod on your server via https://docs.stripe.com/api/payment_methods/create#create_payment_method-acss_debit

That would be the only way at the moment without using Stripe Checkout or the standard intent-first Payment Element flow which involves a client-side confirmation.

[frail trail]

thanks again for the help.

if you're interested in updating the documentation, this section in the acss-debit getting started could be clarified with a note detailing this exception https://docs.stripe.com/payments/acss-debit

[golden falcon]

Thanks for the feedback. I'll pass that long internally

[frail trail]

will I have access to this thread in the future?

I see, it will just be moved to read-only

[golden falcon]

Yep -- you can save the link to come back to it if needed.