#solidtea-connect-accounts
1 messages · Page 1 of 1 (latest)
I'm not sure what you mean to achieve here, can you provide an example of what you'd expect to do?
Yes
My client's customers are health practitioners
Some of them work together and share an account for payments
If it's just a single practitioner, we use the Stripe Python SDK to create a new express account and the frontend sdk so they do their onboarding
However that does not offer the ability to use an existing connect account
Say I'm practitioner A's colleague
and practitioner A already has a Connect express account
is there any sort of interface that would allow practitioner B to connect to their express account?
Or say practitioner A already has an express account they use for another app
would there be a way to reuse that account?
I'm aware this could be handled fully at the app level, but I'm wondering if Stripe offers an interface that could make this feature implementation easier on our developers
For the case with an account they use for another app/platform no, that's separate by design and unrelated to your platform
Looking into the case of an existing account to share for your platform
Makes sense
SO there is no native affordance for this, they'd need to be using the same email/phone for stripe to detect it
but on your app side two users could share credentials (email, password) for your app, and then you provide dashboard access via Login Links:
https://stripe.com/docs/connect/express-dashboard
Express provides its own account management and reporting features for users, built into a Dashboard hosted by Stripe.
So you're managing the authentication layer that allows for shared access
ok but say they use the same email/phone
I mean there's no way to do that prior to know which account to connect to
what I mean is currently, in test mode, if I create a new express account and use the same email and phone they show up as two separate accounts
because another account had to be created to even begin the onboarding flow
is there no way to retrieve an account id based solely on email/phone and maybe the app id?
no, but in this case you might want to collect the email before creating the account and onboarding. that would allow you to check for existing accounts in your system and direct them to login instead of creating a new account.
yes that is fair
that's what we were planning on doing if there was no other way
thank you for asssistance
Express enables your platform to manage payout schedules, customize the flow of funds, and control branding. Stripe will handle onboarding, account management, and identity verification for your platform.
np!
i think that approach will lead to the best experience -- it will allow you to guide the user to contact their existing account admin for access etc
"another person at your practice..."
yes you're right that is a good point
However I feel like if they were to be offered to link an existing account upon entering existing email/phone number during onboarding it could streamline the process
I understand it would require to expend the current architecture of the Stripe platform and it is far from a priority for you
I think existing account emails are detected in live onboarding, but i'm having trouble testing that right now to confirm
sit tight, will try to confirm
yep, when i try to onboard with an existing email i get pushed to log in to that account insted
so you have two flow options available to you
i still think it makes sense to manage this in your app, but that's your choice
ok so
I've gone throught that flow to log into an existing account in test mode
but after logging in it still has me do the whole onboarding flow regardless
is it because it's test mode?
and if so then would it mean that in live mode that second account_id references the first one ?
yea in test mode this is different because everyone used test@example.com
so it wouldnt work very well
to have to generate unique emails
not sure what you mean by reference, but there's no mapping to the account they log in to, you just end up with an incomplete express account that doesnt onboard
I see
so they'd need to "onboard" by logging in every time
and I wouldn't have any feedback from Stripe letting me know that they've logged into an existing account is that correct?
correct -- i really suggest trying to check emails in your system first if this is a common user experience/path
Thanks for this thorough explanation