#todordvv_docs
1 messages ¡ Page 1 of 1 (latest)
đ 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/1290318400522027084
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
What is not working like you expect?
Well we're expecting to be able to set the application fee globally and then create standard accounts that can utilize that.
Since we need franchises to be able to login in a dashboard but we don't want to have to create said dashboard.
I just can't fantom why standard accounts can't have the platform manage fee collection.
if we're moving to fluid accounts and away from types
why can't both:
controller.stripe_dashboard.type = full
controller.fees.payer = application
be set?
Where are you seeing that combination is blocked? Are you trying to create accounts and encountering errors for that configuration?
yes, in the docs it clearly states that combination is invalid:
under unsupported configurations
so both UI methods (using dashboard, creating connect accounts using the standard stripe dashboard interface) and API have a limitation
you can't use the BETA platform pricing tools with standard accounts (since the fee payer is not the platform)
and there's no platform pricing overrides in the standard connected account settings
and nether does the API approach work
Oh, i misread. I see.
to create an account that has a dashboard access (set to full) but also has the platform handle the processing fees
which would enable the platform pricing tools to be working on that account
I can't really speak to why configurations are not supported by default. I would recommend you write in to support with a clear explanation of your model and some example customer/payment flows that you'd use, and support can provide guidance on whether this is possible.
https://support.stripe.com/contact
Find help and support for Stripe. Our support site provides answers on all types of situations, including account information, charges and refunds, and subscriptions information. Get your questions answered and find international support for Stripe.
so we either have to chose to have platform pricing tools and handle invoice creation through API, in which case WE DON'T REALLY NEED the platform pricing tools since if we create an invoice via API we can just set the application fee amount right?
or we have to use standard accounts but we can't set application fees for any invoice the franchises (connected accounts) create via their dashboard
we did but we're trying to figure out the API aspect of this...
we even tried using the webhooks to modify payments to add application fees to every payment but the payment is processed before the webhook even arrives
so that's a no-go
we did but we're trying to figure out the API aspect of this...
You did what?
we're trying to figure out if we can resolve this via API - i.e. have standard accounts automatically apply an application fee to each transaction
without the standard connect accounts having control over this, i.e. removing it
No, you would specify that via the application fee params
we have contracts with these franchises (which get a connect account) where we should charge a % of each transaction
but we want to use the stripe dashboard
and so if they create an invoice via their connect dashboard (for standard accounts) there's no way to specify application fee parameter right?
and with these beta tools now, the platform pricing tools don't work for standard connect accounts - only express and custom
and express and custom don't have full dashboard access
Correct
These pricing schemes apply to activity on your connected accounts where your platform is responsible for the Stripe fees.
THat's at the top of the platform pricing tools doc
exactly, so to sum it up - there's no way to setup AUTOMATIC GLOBAL APPLICATION FEE for a "standard connect account" i.e. one that has full dashboard access
if they just create an invoice via the dashboard there's no way to modify the invoice to include a fee on a global level
neither via the UI of the dashboard for the platform, nor from the connect account dashboard, nor from the API functions
That seems to an an accurate assessment of the currently defined behaviour, yes
If you have a use case that falls outside of that, please talk to support about whether that can be used
we will, just wanted to make sure I understand the API and platform capabilities
and honestly it's very strange because as I said, and bear with me for a sec here
if we're using express or custom accounts - we have to use API to create invoices and subscriptions
so we have a way to set a fee amount on those as the invoice is being created via the API, so we don't need a global option
the only reason we might need a global option is for standard accounts which can use the full dashboard to create their own invoices and subscriptions
yet the global options in PLATFORM PRICING TOOLS (beta) specifically don't work with standard accounts
it's literally an oxymoron
it should be the other way around
wouldn't you agree?
I can see what you're trying to do, and I imagine there must be a reason why this is not allowed by default via the API. It's possible there are exceptions to this rule depending on use case, but I don't know about those. That's why I am suggesting you write in.
Already did but we're honestly frustrated. Support just said they'll investigate and I am not sure they understood - they said they'll forward to someone.
This is the main reason we went with stripe and we were assured we'd be able to collect fees automatically and very easy
but it turns out we can't not unless we create our own dashboard and just do everything through API
Understandable, but this feature is still in development so may not support all use cases just yet.