#u_237936102 - connect

1 messages · Page 1 of 1 (latest)

radiant impBOT
wise dirge
#

They all can work for various use cases. Have you seen this doc on choosing your account type? Has info on how each works and that may help clarify what is best for your business model https://stripe.com/docs/connect/accounts

#

Can you tell me a bit more about your use case and what is drawing you to separate charges and transfers?

#

u_237936102 - connect

pale rampart
# wise dirge Can you tell me a bit more about your use case and what is drawing you to separa...

We are a service platform where we have service providers who showcase their digital services. Somewhat like a marketplace but controlled. When global users see a digital service they are interested in they purchase it one-time. If the service is 10 euros we expect the customer to pay via stripe and 4 euros goes to the service provider, the rest is divided between stripe charges and our platform markup

wise dirge
#

Gotcha, so yeah any account type could work with that flow really. Has that doc been clarifying to you on what control it gives you vs your connect accounts and whether any of those particularly align with what you are trying to do?

pale rampart
#

I am leaning towards this workflow:

  1. Create a custom account for the service provider https://stripe.com/docs/connect/custom-accounts (needs alot of effort but minus all the rules and caveats I am seeing for all the other options)
  2. Create separate charges and transfers - make charges on our platform account on behalf of connected accounts (Service providers), perform transfers separately, and retain funds (our markup) in the process
  3. Create invoices with Connect for our service providers - https://stripe.com/docs/connect/invoices
    4. ? what am I missing here ?

Caveats

  1. https://stripe.com/docs/connect/cross-border-payouts
  2. Platform in a supported country

**From stripe this is OUR flowchart **https://b.stripecdn.com/docs-statics-srv/assets/charges_transfers.a95f5bf398651fba0fb303e32a742546.svg

lime rampart
#

HI 👋

Catching up here.

#

To handle the regional restrictions we recommend creating a Platform Account for each region you wish to do business in.

pale rampart
lime rampart
#

That's a bit too general of a question. I can offer advice on specific API calls and Stripe behavior but I can't do a full review of your integration.

pale rampart
#

I am not asking you to review my integration (none of our code is posted here) am asking you to point me in the right direction do those API calls work all together to accept payments and payout to other connected accounts

lime rampart
#

Can you just provide the API calls rather than reference back to an old thread

pale rampart
lime rampart
#

What are you invoicing your service providers for?

pale rampart
#

For sending the connected accounts their split of the money. docs sstate "You can create invoices for connected accounts, which support several approaches for collecting payments" the several approaches are https://stripe.com/docs/connect/charges

lime rampart
#

That is a destination charge, not a Separate Charge & Transfers approach.

#

With separate charge & transfers all the "charge" parts are done solely on the Platform Account and then funds are transferred to Connected accounts.

pale rampart
# pale rampart

Kindly read what is written there. If you a right then there must be an error in the docs then "on_behalf_of parameter for a new invoice by USING SEPARATE CHARGES AND TRASNFERS"

lime rampart
#

Ah sorry, NVM

#

I was looking at the second code snippet

pale rampart
lime rampart
#

I don't see any obvious problems but I would still create a basic MVP in test mode to validate the behavior.

pale rampart
lime rampart