#scott_best-practices
lethal galleonBOT
👋 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/1501468797356212319
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
azure crater
Stripe doesn't support grandparent / grandchildren relationship, i.e. a platform (child) connects to another platform (grandparent), and process the payments on the connected accounts of the child platform.
This relationship is not supported by Stripe: Your platform (grandparent platform) > Shop owner's platform (child platform) > connected accounts (grandchildren accounts)
Direct charge only supports one terminal reader to one connected account currently
coarse osprey
so there’s no solution for one card reader shared by different connect accounts - even by not going down the direct charges route?
azure crater
The only possible way is to perform destination charges with reader owned by your platform. However, the platform will be the one managing the location, refund... etc. The connected account holder will not have access to the management of the reader as well.
If you would like two connected accounts to manage the same reader, this is not supported
coarse osprey
Okay. My platform would be charged for the Stripe Transaction fees in that setup too right ?
The only alternative I could think of would be be to stick with direct charges and then make a transfer to the intended destination afterwards.
I’d have to work out a way of reimbursing the stripe transaction fee from the card reader owner to the charge destination though right?
azure crater
If Destination Charge is used, platform will be charged for the Stripe fee.
The only alternative I could think of would be be to stick with direct charges and then make a transfer to the intended destination afterwards.
This is not supported unfortunately. Stripe doesn't support fund movement directly between two connected accounts. Moving funds between two connected account should always go through the platform, i.e. accept payment on connected account A > transfer the fund to platform > the transfer fund to the connected account B. In addition, the merchant record of the payments will be connected account A in this case.
Alternatively, you can use Separate Charges and Transfers (https://docs.stripe.com/connect/separate-charges-and-transfers) which the platform can transfer the final amount after deduction of the Stripe fee. For example, the payment will be processed on the platform (with optional on_behalf_of for the merchant of the record purpose), then transfer the fund with the amount after the deduction of Stripe fee.
