brenbit

Thanks for the feedback! I do apologize for the lack of information in my original post. Here's some additional color that hopefully clarifies my use case a bit more:

Stripe offers a service called Stripe Connect (https://stripe.com/connect) which enables platforms to have intermediary sellers / merchants which collect money from end customers. Ultimately, this can lead to a scenario where an end customer pays a connected account without ever realizing that the primary account (me) is taking a percentage as well (this is allowed and is a primary use case for Stripe Connect).

Ideally, for my scenario, I want connected accounts to have connected accounts of their own. Here's the hierarchy:

My product -> Connected account owned by developer -> Connected account owned by merchant -> Customer paying the merchant

Note: The developer is building tools for the connected merchant account, thus taking a percentage of profits.

Unfortunately, this multi level tree hiearchy is not possible. My proposed workaround is to flatten the Connected account tree (since connected accounts can't have connected accounts of their own), and then allow the "Developer Connected Account" to reach my API so I can piece the two together.

One crucial piece of information here is that the end customer who is entering the credit card information will ultimately be paying the connected account that they are interacting with, so the bank statement will show the correct company.

Also, my API would have checks to ensure that only Connected accounts can interact with it, so Stripe ultimately knows who their customer is.