hoongry_api

[gritty karma]

👋 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/1427621814913208362

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[blissful egret]

hi there!

[civic verge]

Hi

[blissful egret]

type and controller are mutually exclusive. so you need to chose between the two.

if a normal "standard" account doesn't work for you, then you probabbly want to use the controller property which gives you more control.

and you can learn more about the different controller configuration here: https://docs.stripe.com/connect/design-an-integration

[civic verge]

ok, but how can I create a standard account with stripe fees on behalf of the platform?

[blissful egret]

is there an issue with the configuration you shared in your screenshot?

[civic verge]

The screenshot is what I need

[blissful egret]

so have you tried this? what's the issue?

[civic verge]

If I create a standard account with the api, as you said, I can only set type or controller so I cannot set type: standard and controller with fees.payer to 'application'. On the stripe dashboard if I click on create in the connected account section and select standard, I cannot set who pays the fees.

[blissful egret]

I already explained this. don't create a "standard" account. instead use the controller property to have more control over the connected account.

and in the controller property, set everything as in the screenshot you shared:

here are the parameters you can set: https://docs.stripe.com/api/accounts/create#create_account-controller

• using type (standard, express, custom) is the old way of creating connected account
• using controller is the new way of creating connected account, which gives you a lot more flexibility. that's what you want to use.

[civic verge]

Give me a second, I will try it

ok, so I tried to create an account with this controller:

controller: {
fees: { payer: "application" },
losses: { payments: "stripe" },
stripe_dashboard: { type: "full" },
requirement_collection: "stripe"
}

It should be the same as the configuration utility, right?

This is the error that I get :
fees[payer]=application` is not supported when creating an account with the full dashboard.

[blissful egret]

can you share the request ID (req_xxx)? you can find it here https://dashboard.stripe.com/test/logs

but not all combinaison of the controller object are valid. so you'll need to figure out a configuration that is valid and works for you.

[civic verge]

This is the requestId: req_eoYk6wJC7ehQbR

[blissful egret]

thanks! yes it looks like this specific configuration is not supported by Stripe. so you would need to change one of the controller property (either stripe_dashboard or fee.payer) for this to work.

[civic verge]

So is the documentation not correct? I cannot create an account with full dashboard with 'application' as payer?

[blissful egret]

I can raise that feedback to the team working on the documentation.

but what is you end goal eactly? for the platform to pay the Stripe fees?

if you create Destination Charges or Separate Charges & Transfers, then the platform would be paying the Stripe fees.

you can learn more about this here: https://docs.stripe.com/connect/charges

[civic verge]

The main goal is to create a payment to a standard connect account and have the platform pay the stripe fees

[blissful egret]

got it. then have you tried what I suggested just above?

[civic verge]

to change stripe_dashboard ?

[blissful egret]

no, to use Destination Charges or Separate Charges & Transfers

and simply create a Standard account.

[civic verge]

I already use destination charges, the stripe fee is paid by the standard account

no, sorry I'm using direct

[blissful egret]

got it. with Direct Charge it's indeed the connected account that will pay the Stripe fees.

the only option would be to use Destination Charges or Separate Charges & Transfers. but note that this change would impact other things, like who is the merchant of record and who handle disputes/refunds.

[civic verge]

I think that at a fiscal level, direct charge is the correct configuration. Last week I tried to create a connect account with fee.payer set to 'application' and was able to create it with stripe_dashboard set to express. I tested it with a direct charge and it worked. So is this the correct alternative if I cannot use standard account and destination charges?

[blissful egret]

doing a Direct Charge on an Express account is technically possible, but a really bad idea.
the main reasons is: it would be up to the Express account to handle Refunds and Disputes, but the Express dashboard doesn't allow to do this.

I think the simplest option is to keep Standard account with Direct Charge, but change your application fee to take into account the Stripe fee.

[civic verge]

But in that case the stripe fee is paid by the connected account not the platform

[blissful egret]

correct, that's why you could reduce your application fee to take this into account.

that's not a perfect solution, but what you are trying to do (Direct Charge where the platform pays the Stripe fee) is just not supported.

[civic verge]

ok, got it

thank you for the help. I currently have this structure, so I will change the application fee accordingly

[blissful egret]

happy to help 🙂

[civic verge]

But is it this thread public?

[blissful egret]

yes, why?

[civic verge]

just asking, because I can see every other support thread

[blissful egret]

yes support on Discord is public.

if you want private support, you would need to reach out to https://support.stripe.com/contact