#nitin_api
dire tundraBOT
👋 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/1327151709897752636
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
rocky steeple
This is the API throwing 400
URL - https://api.stripe.com/v1/elements/sessions
Error - {"error": {"message": "You do not have the capabilities required for payment method sepa_debit","request_log_url": "https://dashboard.stripe.com/acct_1PyGC2EWpHr2XKZj/logs/req_7sVQq6lmmCCpDu?t=1736486892","type": "invalid_request_error",},}
Log - https://dashboard.stripe.com/acct_1PyGC2EWpHr2XKZj/workbench/logs?object=req_7sVQq6lmmCCpDu&filtered=true
grim blaze
Hello! Taking a look, gimme a while
this connected account doesn't have SEPA Debit enabled as a PaymentMethod, i think try asking your connected account to enable SEPA in their payment method settings and see if it works for them : https://dashboard.stripe.com/settings/payment_methods
rocky steeple
Thanks @grim blaze , will inform the same with the client. But in this case no payment elements are being loaded. Atleast the card payment should be visible right? Instead the payment element just does not display anything but throws the above error only for sepa debit. Ideally not enabling sepa debit should not block other payment methods right?
grim blaze
onesec, looking into whether card will show
hrm, because the session itself is failing, that's why I don't think the payment element will load. I think like what you said, disabling sepa debit should allow it to work, but you will need to test it out to make sure it works
rocky steeple
@grim blaze Another thing that I noticed is the session API only failes when the deferred_intent[mode] is subscription. If it is payment it loads the above screen as expected
grim blaze
can you paste the relevant session request id for the above screenshot scenario (mode="payment") here, then write in via the link I'm going to share, and we'll look into it.
I'm assuming that you expected that if sepa debit is not an enabled capability on the account, we should just omit it and display the other available payment methods instead.
dire tundraBOT
Hello @rocky steeple, we have sent you a direct message, please check it at https://discord.com/channels/@me/1327172731124453376
- 🔗The message has instructions on how to open a direct support case with our Developer Support team, in order to help you more effectively.
rocky steeple
@grim blaze By session request id you mean stripe_js_id from the payload? Because I'm unable to any other Ids from the request
I'm assuming that you expected that if sepa debit is not an enabled capability on the account, we should just omit it and display the other available payment methods instead.
Yeah
grim blaze
are you able to see this request https://api.stripe.com/v1/elements/sessions from the frontend network requests for the mode=payment screenshot that you shared?
rocky steeple
Yeah, I'm able to see it. What should I be sharing exactly from that/
Should I share any ID from that params or the entire request itself?
grim blaze
just paste that request id here, that's sufficient
rocky steeple
These are the request ids for both payments and subscription
req_xaHmVdjKmexrwZ - payment [working]
req_SQaSa40M16ChMZ - subscription [not working]
grim blaze
alright, once you submit the support ticket, we'll look into it further and get back to you via the ticket!
rocky steeple
Thanks, I have raised a support ticket with the request IDs