#denjaland-connect
1 messages · Page 1 of 1 (latest)
Hi! So you would like the platform A to be connected to account B, and the platform B to be connected to account C?
yes
but I only have the pk for A whoc is the "mother of all accounts"
so my question is: can I, as A, onboard a connected account C on behalf of account B
Got it! I'm not sure, I'll have to test this. Please give me a few minutes.
This didn't do the trick for me:
$stripeAccount = \Stripe\Account::create($accountData, [
'stripe_account' => Tenancy::supplier()->getExternalReference(ExternalReferenceType::stripeAccount())
]);
So I tried and I got this error:
Connect platforms cannot create new accounts on behalf of their connected accounts.
So it looks like what you want is not possible.
thought so - thanks for checking into it though - I'm guessing it has legal reasons.
there is now way that I can customise the name that you guys show when redirecting to the onboarding url, right?
Can you clarify which name you are talking about? A screenshot would be great.
This is the onboarding page of connect for standard accounts. The marked area is always showing the data from account A, when we onboard C. For C... (we have to connect them directly to the root account as I can't create connected accounts for a connected account...)
to be clear , we explicitly ban trying to set up that model of Connect, so I'd suggest not trying to work around it. The C account has no legal relationship to A or to allow A to see their Stripe information, for example, wen you do this C->B->A setup
anyway the name in that onboarding flow comes from the Business Details on https://dashboard.stripe.com/test/settings/connect from the platform account that created the AccountLink
yeah - totally understand. we just need to make it clear to the user that they will be connecting to DENJA and who DENJA is in this flow
one thing I'd really like though is the ability of having the onboarding pages in a modal / iframe so we remain within the website. Not sure why you don't allow it 🙂
you have the option to use Custom accounts for a whitelabel flow(but I wouldn't actually recommend it, it's just an escape hatch).
it's because there are all sorts of potential limitations and bugs/bad interactions in a complex web app like that one(for example in some flows we might want document uploads, or to access the device's camera, or integrate with third-party bank account connection logins etc etc) when you don't control the viewport and are framed
we'll stick to standard accounts just because of liability to be honest. I don't want to take liability for any of the connected accounts.