#quercus-Standard-Connect
1 messages · Page 1 of 1 (latest)
Hi there! Are you worried about a customer who already has a Standard Account that is Connected to your platform and them attempting to sign up again, or if they already have a Stripe account before connecting to your platform?
Right now more if they already have a Stripe account before connecting to my platform
Are you using Connect Onboarding or the OAuth flow?
Connect Onboarding is recommended and is the newer flow.
Connect Onboarding
Great, so in that case a new account will be created with your platform and the Connected Account user will have access to both accounts (their previous one and their new one). They also can pre-fill their onboarding information based on their details of their already-created account.
"They also can pre-fill their onboarding information based on their details of their already-created account." - So they can use the same information, EIN, email, business name, etc. but they will have two separate accounts?
Yes, since your platform will "control" the new Standard Account two accounts will be created, but yes they can use their previous business details so they don't have to enter them again. We have some info on the platform controls that I'm talking about here: https://support.stripe.com/questions/standard-connect-with-platform-controls
thank-you! So you also kind of answered another question. I was wondering if I should give customers an option to use OAuth flow with Stripe, but it sounds like no?
Yes Connect Onboarding is definitely recommended — it gives you much better control and avoids pitfalls like the user dropping off of the OAuth flow midway through and you having no insight into their account.
Is there a way to allow them to use Stripe credentials for authentication? Right now I am using Google and magic link as options.
Can you clarify what you mean by that?
What authentication are you referring to here?
I am using next-auth to handle authentication to my app. They use OAuth providers google, twitter, magic-email. etc. It crossed my mind that since I am building on Stripe and Stripe has an OAuth flow of its own, that maybe it would make for my customers to use that, similar to the way Donorbox's authentication works if you are familiar with that service.
Ah I see. No this wouldn't work. Stripe OAuth is only to Connect to a platform. Then the user would login to their Stripe Dashboard directly if they want to access that, but they would never use OAuth via Stripe again.