#rj1_connect-charges-stripe-fees

1 messages · Page 1 of 1 (latest)

graceful gustBOT
#

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

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

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.

fierce owl
#

With ACSS Debit payments, you can't take an application fee?

craggy cairn
#

we do take the application fee, and it works, but then there is an additional Stripe processing fee on that transaction as well

#

whereas in the case of credit card transactions, this doesn't happen, the platform account gets billed for those, which is what we also want for acss_debit transactions

fierce owl
#

Oh ok. We don't know anything about pricing/fees or how they're calculate in here. So, I recommend writing in to support to find out why that extra fee is charged and how it's calculated. That way you can adjust your calculation for how much application fee to take. https://support.stripe.com/contact

craggy cairn
#

Sorry, let me rephrase, the calculation is ok, but ultimately we just want the platform account to be charged

#

which is why we define application_fee_amount, and this is working for CCs

#

is there anything we can change in our implementation to make sure this doesn't happen for acss_debit?

fierce owl
#

I guess I don't understand the issue then. With direct charges, the connect account is always charged for the stripe fee no matter what. An application fee is a transfer of funds from the connect account to the platform account. I don't understand how you are using this to charge the fees to the platform account for credit cards.

craggy cairn
#

so you mean it shouldn't work the way it is currently working for us for credit cards?

fierce owl
#

We don't really know much about fees in here to be honest

#

So that's why I recommended you write into support

#

But how does collecting an application fee affect stripe fees in any way? That's what I don't understand

#

An application fee is a transfer of funds from the connect account to the platform account

#

But really I recommend you talk to our support team for help on this. They're going to be able to assist better than us for fee/pricing related things

craggy cairn
#

yeah I took a look at that as well, we have connect accounts set to application_custom, which in this case should charge the fees directly to the connect account like you say, but it's very confusing because this isn't what's happening for CCs, only for acss_debit

#

ultimately I am trying to resolve this fee issue without having to switch to destination charges, because our client's clients already have payment methods stored in the connected accounts rather than the platform account, and we don't want to have to delete those payment methods and have them re-add them so that they're in the platform account

#

is there any way that we can change the connected account types from application_custom to application? is that configurable? (on already existing accounts)

graceful gustBOT
calm raptor
#

Hi 👋

I'm stepping in as my colleague needs to go.

craggy cairn
#

hi @calm raptor, thank you!

calm raptor
#

I'm a little confused what you mean about Connected Account types. We have a type property on the Connected Account but that only accepts values "standard", "express", and "custom".

And there is no type attribute of the controller property

So can you clarify what the exact property you want to change is?

craggy cairn
#

yeah, it would be this property here

image.png
calm raptor
#

Ah, you mean the controller.fees property. We document this here. This is assigned when you create an account with type="custom" and is not something you can change.

#

There's a handy table of Stripe fees and which account is charged them in that same doc which might be useful for you

craggy cairn
#

thank you!

is there any other potential configuration on our platform account or the connected accounts that would cause this discrepancy between which account is being charged the fees?

again, the platform account is being charged the stripe fees on credit card transactions, but for bank transactions, it is being charged to the connected account, and we have no idea why this inconsistency is occurring

calm raptor
#

Unfortunately, as my colleague mentioned, we know very little about how and where Stripe fees are assessed. According to that table it appears Stripe payment processing fees are assessed to the Connected Account if controler.fees.payer="application_custom" but some other fees may also be at play here.

My recommendation is to write in to Support and provide example payments for both cases - credit card & ACSS debit and ask about the discrepancy in the way fees are assessed. Provide actual Payment Intent IDs for each payment scenario. Those will allow us to look up the related Stripe fees.

That will make sure the team handling your request has a clear picture of what is going wrong

craggy cairn
#

ok, thanks, I will reach out to them with live payment IDs

calm raptor
#

Happy to help. I hope we can provide some useful information that will help you get consistent behavior in your integration.

misty burrow
#

Helo

graceful gustBOT
#

@misty burrow looks like you're in the wrong place, this thread is for someone else's question.

Note that posting inappropriate messages in other people's threads is against the rules. No worries if this was just an honest mistake, but anyone who violates the rules multiple times will be removed from this server.