#AliJhaver-connect
1 messages · Page 1 of 1 (latest)
Can you clarify - are you saying that your connect account is not seeing any fees being removed from the charge, which you aren't expecting?
So we have a customer under us as a connected account. When they run a transaction, the "fees" are not being deducted from the payment amount. Insead the entire amount if being deposited in their account. Check screenshot pls
Keep in mind, this is a connect account under our main account.
Do you have a charge id?
pm_1Jpcwu2UVNUL5abBOynEr55j
ch_3Jpcwq2UVNUL5abB1Iye3dM3
one of those two i believe
looking!
thank you!
@indigo pecan okay so there are 2 pretty big things here
1/ You are using Direct charges with Custom accounts. This is almost always a mistake and something we usually strongly discourage. Platforms with Custom accounts should use Destination charges: https://stripe.com/docs/connect/destination-charges
It's possible you have multiple good reasons to do this, so up to you, but I want to flag because it's almost always a mistake you regret months later.
2/ Your platform has a special pricing rate where fees are assessed async. This is something you or someone at your company should know about your platform's configuration though! I can't really discuss account specific things on Discord but it points you in the right direction
Yes I am aware of that. So we do have custom pricing. But in our situation, who remove the fees from the customer? Do we do that on the development end or do we set that up in Stripe connect?
does the destination charges allow us to remove that charge and deposit it in our account? I understand Stripe would charge us their fees later, but how do we remove the fees from the actual transaction charge?
i hope that makes sense. is there a number that i can call?
Right now you are creating a charge on a connected account and that's it. So we leave all the money to the connected account. As a platform it's on you to take a cut of the revenue as your own.
there are different ways to do this, and it depends on your integration. If you move to Destination charges, which is the right way, you charge $100 and you explicitly ask us to transfer $90 for example so that you keep $10 as your own revenue/share. And we separately charge you for the fee for that charge later
ah okay that makes a lot more sense. so the problem is we are running these as direct charges instead of desintation. if we ran them as destination, we could clarify how much we want stripe to remove immediately upon the transaction going through
That works with Direct charges too and has been supported for years https://stripe.com/docs/connect/direct-charges#collecting-fees. You'd use an Application Fee in that case
But don't move to Destination charges if you are building a new integration. Way better!
Okay, I will check with our team why we are using direct charges instead of destination charges.
But question for you, can I assess application fee in direct charges as a percentage? Example, 2.9% + $.30 per transaction?
you control the code, you have the amount so you can make the math and pass the final amount in that case!