accua

[mossy pecan]

Accounts each have a Unique ID and do not have Customer IDs

What ID are you talking about?

[plain salmon]

What's the name of the parent object who has one or many associated accounts?

[mossy pecan]

The Platform Account

[plain salmon]

ok, let's say if you're creating n number of connected accounts for a single user, a simple model for that would be user.stripe_account_ids = [an_array, of_ids] correct?

[mossy pecan]

You would create multiple accounts and specify the same email for each of them.

That would be pretty straightforward

[plain salmon]

ok, so if I then wanted to create n number of additional connected accounts for that user, and was using stripe hosted connect onboarding, can I get all the data I need to create that account from the Accounts api?

[mossy pecan]

So you create Account A and they go through onboarding. Then, to create Account B you want to retrieve Account A and populate all the data so Account B doesn' t have to onboard?

[plain salmon]

Is that even possible?

[mossy pecan]

Nope

You can prefill most of the info

[plain salmon]

ok, that's my understanding

[mossy pecan]

but there are some PII stuff that we won't return in the API

So you can cut down on the amount of onboarding for Account B but they will still need to onboard

[plain salmon]

what if we wanted to batch create the accounts.. can we collect the PII from the user once and then send it over to create 5 different accounts?

or is that collection required one at a time, every time

[mossy pecan]

Nope, one at a time.

Wait... have you tested this flow yet?

[plain salmon]

I'm working on testing it, but want to make sure it's possible.