#tobewisebeforeiamold_code
ivory galeBOT
đ 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/1483537878611918983
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
craggy ore
Is there some way to see debug output in the console to give me a hint as to why the PaymentElement shows the tab, but there are no inputs shown when I click on that tab?
void fiber
Hello, good question. I'm not sure the best way for you to check that for a checkout session. Looking in to this.
And are you seeing ACSS with the same setup in payment mode?
craggy ore
I haven't gotten to payment mode yet. I'm starting with adding the method via what we call the "wallet". So just starting with setup_intent as opposed to payment_intent.
Here's what the setup_intent looks like that I created in order to open that PaymentElement{ "object": { "id": "seti_***", "object": "setup_intent", "application": null, "automatic_payment_methods": null, "cancellation_reason": null, "client_secret": "seti_***", "created": 1773772015, "customer": "cus_***", "customer_account": null, "description": null, "excluded_payment_method_types": null, "flow_directions": null, "last_setup_error": null, "latest_attempt": null, "livemode": false, "mandate": null, "next_action": null, "on_behalf_of": null, "payment_method": null, "payment_method_configuration_details": null, "payment_method_options": { "acss_debit": { "currency": "cad", "mandate_options": { "interval_description": null, "payment_schedule": "sporadic", "transaction_type": "personal" }, "verification_method": "instant" }, "card": { "mandate_options": null, "network": null, "request_three_d_secure": "automatic" }, "us_bank_account": { "financial_connections": { "permissions": [ "payment_method" ], "prefetch": [] }, "mandate_options": {}, "verification_method": "automatic" } }, "payment_method_types": [ "card", "us_bank_account", "acss_debit" ], "single_use_mandate": null, "status": "requires_payment_method", "usage": "off_session" }, "previous_attributes": null }
I don't need to spoof my IP as being in Canada to get that to show up, do I?
void fiber
No immediate idea from that. Can you send the actual ID of the setup intent that was returned? It is considered safe to share those because someone would need your secret key to be able to do more with it.
I have something I can check on my side. Looking into if there is a good general tool for you on your side. rWe do have this dashboard tool that lets you see reasons why certain PMs did or did not show up for a specific payment, but it doesn't have an option for setup intents.
Oh sorry I see that acss is in that payment method type list. I don't think you need a CA IP for this, looking in to why else it might not show up
craggy ore
Here's the ID for that setup_intent creation: seti_1TC2aKDYgrK1cJzVKgY4Agsf
We do have this dashboard too
Neat! Looks like that's geared towards payment_intent, which is why you probably asked about that. Maybe I'll stub out some code so I can use that, if you can't see anything obviously wrong with my setup_intent, and then use that information to get the setup_intent working.
In case visuals are helpful
void fiber
Ah there we go. So I just tested with your same code and and am seeing the same thing.
The twist is that this is expected behavior and the PAD panel is actually the ACSS panel here.
craggy ore
The twist is that this is expected behavior and the PAD panel is actually the ACSS panel here.
Sorry, I think you lost me
void fiber
Basically PAD and ACSS are both parts of Canada's system for sending payments by bank debit
PAD = Pre-authorized Debit
craggy ore
Gotcha - but that's what I'm trying to enable: PADS. Am I using acss_debit in the back-end when I should be using a different value, or maybe an additional value?
void fiber
You are already passing the right thing. I think I may have misunderstood your original question. When you say:
How can I get inputs to appear within the "Pre-authorized debit" tab of my PaymentElement?
What inputs aren't showing up that you are expecting?
craggy ore
I was working off of this doc: https://docs.stripe.com/payments/acss-debit/set-up-payment?payment-ui=checkout
What inputs aren't showing up that you are expecting?
I guess I am not sure. For card and ACH you have to enter some data so Stripe knows what payment method you're referring to. But since I get no inputs within the setup_intent Pre-authorized debit tab I am assuming something is not working correctly. How does Stripe know what bank to draw upon, or what account at that bank? If you and I both lived in Canada and tried to pay via PADS we'd have to enter something into the PaymentElement so Stripe knows to draw upon my account and not yours?
void fiber
Ah gotcha, so you need to submit the form to see the rest. The Payment Element only shows a name and email field but submitting it brings up a popup where the user would log into their bank or enter their details
It is like how ACH works but I guess for some reason we don't show the bank icons and such up front
craggy ore
OK, so when I call stripe.confirmSetup that'll launch something! OK, thank you! I didn't even try that because I assumed it was broken. Thank you!
Confirmed - the issue here was my unwarranted apprehension. Solved, thanks! Have a great day!
void fiber
No worries, glad we could fix that!