#Fab-full-ToS
1 messages · Page 1 of 1 (latest)
Hey!
The transfers capability is the default and will be on every account. If you aren't going to use it, that's fine and you can ignore it.
That said, let's back up a second. What type of Connected Accounts are you using and which fund flow?
I’m using Custom Accounts + destination_charge + on_behalf_of. The flow of funds is designed to set the connected account as the MOR (merchant of record/settlement merchant) while we, the platform, collect a platform fee
Yep great.
So technically with that flow you are using both the card_payments and the transfers capability
So you would need both. But that fund flow is good and mostly you just want to request both capabilities alongside the full ToS when you create the accounts
Ok got it. I was wondering, if the “transfers” capability results to be active, are we going to be debited for Payouts to Connected Accounts? This cost is only applied if a Custom Account results as Active, I was wondering if the “transfers” capability is involved in that
No I believe that is based on actual processing happening with the account. However I'm not an expert in fees as I focus on the API so you may want to double check with our Support team (https://support.stripe.com/contact/login) on that
Ok thanks a lot! Btw, what if we set a 100% platform fee? So the Custom Account actually doesn’t receive any money, while still being the MOR? Are here still involved both capabilities?
Yeah I wouldn't get too caught up on which capability is used for which piece. Different flows need different capabilities to function as a whole
And yes, the Custom Account would still be the MoR here.
Great, really appreciated!