#michael.ashton-connect-onboarding

1 messages · Page 1 of 1 (latest)

brazen jasper
boreal mica
#

Thank you-- so is it true that using Connect Onboarding with a standard account that does not have a pre-existing integration/connection should not create a new account, but rather connect the existing one? There must be another way to get the URL for onboarding, since you must provide an existing account ID to the AccountLinks.create endpoint.

brazen jasper
#

standard account that does not have a pre-existing integration/connection should not create a new account, but rather connect the existing one
As I understand it, no (per the docs above). Standard accounts now can only be connected to a single Platform – so it's 'cloned' (as you're seeing)

boreal mica
#

But if the account is connected to no other platforms, then it will not be cloned-- right?

brazen jasper
#

If you have an existing account, you should use OAuth and not Connect Onboarding

boreal mica
#

Ah

brazen jasper
boreal mica
#

Ok, I think that answers it. To sum up, for pre-existing accounts we should use OAuth, and for new ones, Stripe Onboarding is the way to go.

#

Accurate?

brazen jasper
#

Yep, for standard accounts

boreal mica
#

And finally-- does a "parent" account have the same access to accounts connected via OAuth as it does with accounts connected via Onboarding?

brazen jasper