#blackout_api
frosty cliffBOT
👋 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/1364783346349248624
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
frigid badger
hello! Where are you seeing that it needs more info?
do you have a PaymentIntent or SetupIntent id which you can share so that I can take a closer look?
frigid badger
that SetupIntent was the one used in your screenshot above?
frigid badger
give me a while to look into this
so looks like you're missing the mandate details. If you refer to this guide : https://docs.stripe.com/payments/acss-debit/set-up-payment?payment-ui=elements#web-create-setup-intent. you need to include the mandate details when creating the SetupIntent
hard harness
Oh my goodness
I was stuck on this for like 3/4 days
You're a legend
Thank you so SO much
frigid badger
you're welcome! the error messaging really could have been better in this case, I'll pass on the feedback
hard harness
Appreciate it, thanks again so much!!
Hey sorry Alex, quick question
In the document you shared, they use stripe.confirmAcssDebitSetup in the FE instead of PaymentElements - does PaymentElements support acss_debit as of now?
frigid badger
let me just try it out...
hard harness
Sounds good, because I update setupIntents but still see same screen - i remeber using confirmAcssDebitSetup earlier in my setup but opted for PaymentElements because it seemed newer and capable of taking diff payment options 🤔
frigid badger
it works for me when using the Payment Element and confirmPayment method. It looks like the code might be slightly incorrect though. For the mandate section, you'll probably want to omit currency: 'cad',
maybe try it out and see if you're running into issues still?
hard harness
Hmm interesting, I recieve :
Missing required param: payment_method_options[acss_debit][currency].
frigid badger
🤔
i guess...you should include it then 😆
so even with the mandate details, you're still running into that same error?
hard harness
Believe so, will start a clean instance to try but hmm maybe because Im using a Modal? Will try a few, but you're able to see the entire acss_debit form in PaymentElements on your end?
{ id: 'seti_1RHGa3RvgpatJxiRfIhbvqXl', object: 'setup_intent', application: null, automatic_payment_methods: { allow_redirects: 'always', enabled: true }, cancellation_reason: null, client_secret: 'seti_1RHGa3RvgpatJxiRfIhbvqXl_secret_SBdrc3MLvkUVobAXl19vR64YWGktFty', created: 1745465767, customer: null, description: null, flow_directions: null, last_setup_error: null, latest_attempt: null, livemode: false, mandate: null, metadata: {}, next_action: null, on_behalf_of: null, payment_method: null, payment_method_configuration_details: { id: 'pmc_1R3VnIRvgpatJxiRxrbErj83', parent: null }, payment_method_options: { acss_debit: { currency: 'cad', mandate_options: [Object], verification_method: 'automatic' }, card: { mandate_options: null, network: null, request_three_d_secure: 'automatic' } }, payment_method_types: [ 'card', 'bancontact', 'ideal', 'sepa_debit', 'acss_debit', 'link' ], single_use_mandate: null, status: 'requires_payment_method', usage: 'off_session' }
OHH
Oh
oh
IT WORKS
]
frigid badger
🥳
hard harness
The whole form doesnt show, it creates another modal hahahah
frigid badger
yepyep!
hard harness
But YESSS, thank you SO SO SO MUCH
frigid badger
glad that we managed to get things working!
hard harness
You're an absolute legend Alex, thank you so much!!