#matt_connect-uasettings-error
mortal turtleBOT
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- matt-k_api, 37 minutes ago, 12 messages
tawny fieldBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1252295786356801658
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
gusty panther
This is the configuration we're trying to create our accounts with, and the documention implies this is valid.
drifting oracle
Hi 👋
What error are you receiveing?
gusty panther
InvalidRequestError: Request req_D53NWN7pXyZlnJ: fees[payer]=application is not supported when creating an account with the full dashboard.
drifting oracle
Unfortunately I do suspect the docs are incorrect, as the error message is pretty explicit and our internal logs show a pretty standard error. I can raise this internally.
gusty panther
Is it possible that there is an account configuration that could change this?
drifting oracle
From my read of the docs as well as our internal code, you should be able to create an account if you change the Dashboard access to Express or None\
gusty panther
The big feature that we want that the express dashboard lacks, is the ability for our connected accounts to be able to handle refunds, is it possible for that to be enabled in the express dashboards? Or would we need to build this out ourselves?
drifting oracle
Actually, just thinking through the logic here, I think the issue is Direct charges occur on the connected account so it is difficult to have both loss liability and stripe fees come from the Platform
gusty panther
Yeah but it is still possible for us to assume liabilities and fees, so long as we build out the dashboard (as far as we can tell) we just would prefer to not have to reimplement the stripe dashboard to do this, and it's not clear to us why we have to?
drifting oracle
It isn't entirely clear to me either but that is the code path I can see
gusty panther
👍
drifting oracle
I get your frustration. It's a current limitation that I can flag internally and raise as a feature request
gusty panther
Do you think our rep would be able to be helpful here? Are there possibly acocunt settings that can be enabled/disables to change this?
drifting oracle
At the very least, we should be able to provide more explanation of why certain configurations are not possible
Are there possibly acocunt settings that can be enabled/disables to change this?
Not that I know of.
With respect to your rep, that might be the most effective way to raise this as a feature request
gusty panther
Ok, thanks for looking into this! We super appreciate how quickly the developer support is able to answer our questions!
(our rep is quite slow in comparison)
drifting oracle
Okay I can also raise this as a feature request if you'd prefer that
gusty panther
That would be great! Thank you!
drifting oracle
Sure thing! Feedback filed. You can reach out to your rep who should be able to find the internal ticket and keep an eye on it for you.
gusty panther
Thank you!
drifting oracle
Sure thing, happy to help 🙂