#kimberly-clio_code
real sirenBOT
👋 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/1300934865641930763
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
wispy yoke
Hi there
Give me a few minutes to take a look
Just to be clear, is there a specific reason why you're using confirmAcssDebitSetup instead of confirmSetup?
lucid shuttle
i'm following this guide https://docs.stripe.com/payments/acss-debit/set-up-payment?payment-ui=direct-api
"Use stripe.confirmAcssDebitSetup to collect bank account details and verification, confirm the mandate, and complete the setup when the user submits the form. Including the customer’s email address and the account holder’s name in the billing_details property of the payment_method parameter is required to create a PAD payment method."
wispy yoke
I recommend following this: https://docs.stripe.com/payments/save-and-reuse?platform=web&ui=elements
If you want to use the PaymentElement for ACSS only (and not present any other payment method types), just be sure to create the SetupIntent with payment_method_types: ['acss_debit']
Then, when you call confirmSetup, you can pass the Elements instance
lucid shuttle
thanks! i'll give that a shot. i assumed that i had to use confirmAcssDebitSetup for acss!
wispy yoke
Yeah, I see what you mean. Our docs are a little confusing here