fredkzk-connect-onboarding | Stripe Developers | Page 1

timid ether Sep 8, 2021, 11:11 AM

#

You are using OAuth link to connect the two accounts right?

surreal stag Sep 8, 2021, 11:12 AM

#

No, I read it is not recommended for new Connect platform like mine

timid ether Sep 8, 2021, 11:13 AM

#

yeah, the only way to connect an existing account is through oAUTH

surreal stag Sep 8, 2021, 11:13 AM

#

Following this https://stripe.com/docs/connect/enable-payment-acceptance-guide?platform=web#web-create-account-link

Enable other businesses to accept payments directly

Facilitate direct payments between other businesses and their own customers.

timid ether Sep 8, 2021, 11:13 AM

#

otherwise it will always create a new account

surreal stag Sep 8, 2021, 11:14 AM

#

oh... but what will happen to oauth?

timid ether Sep 8, 2021, 11:14 AM

#

you mean if Stripe will deprecate oauth?

#

no, as far as I know it will stay.

#

as it is a legit case for existing account connecting to a new platform

surreal stag Sep 8, 2021, 11:15 AM

#

I read this in your page:
OAuth is not recommended for new Connect platforms. We recommend using Connect Onboarding for Standard accounts instead.

Starting in June 2021, Platforms using OAuth with read_write scope will not be able to connect to existing accounts.

#

your live chat support also confirms this is no longer recommended for my case

stoic laurel Sep 8, 2021, 11:18 AM

#

yep indeed. You should connect as an 'extension' , which means using scope=read_only in the OAuth link.

Also do you have the account ID of your 'own personal separate stripe account ' ( acct_xxx it's on https://dashboard.stripe.com/settings/user )just so I can be sure I understand the context?

surreal stag Sep 8, 2021, 11:20 AM

#

ok hold on

#

acct_1JWhC6EhiPJMElyW this is my real live acct. I tried to connect it to the platform I'm building and testing (in test mode)

#

I''ve used https://stripe.com/docs/connect/enable-payment-acceptance-guide?platform=web#web-create-account-link
for onboarding and connecting. But it created a new acct yet I clicked the "Have an account?" link there:

Enable other businesses to accept payments directly

Facilitate direct payments between other businesses and their own customers.

#

stoic laurel Sep 8, 2021, 11:23 AM

#

thanks! so hmm, I feel like you platform should be able to connect to that, since Platforms that use read_write will be able to connect to the user’s existing account as long as they’re the first platform to connect. should apply here

stoic laurel Sep 8, 2021, 11:23 AM

#

surreal stag I''ve used https://stripe.com/docs/connect/enable-payment-acceptance-guide?platf...

oh but that's not OAuth then.

#

that integration(calling /v1/accounts and v1/account_links) does create a brand new account all the time, yes.

surreal stag Sep 8, 2021, 11:24 AM

#

I see, so oauth is the only path?

stoic laurel Sep 8, 2021, 11:25 AM

#

clicking that stuff in the onboarding is just associating the account with your email address/Stripe user, so you can see it on https://dashboard.stripe.com/settings/user and the dropdown in the dashboard and so on, it's not re-using the same account and connecting that to the platform — if you want that, then you would use OAuth, subject to the caveats above that only one platform can have read_write access

stoic laurel Sep 8, 2021, 11:25 AM

#

surreal stag I see, so oauth is the only path?

well it depends really! is there a specific reason your platform wants to connect to the existing account? What does your platform do?

surreal stag Sep 8, 2021, 11:26 AM

#

using scope=read_only in the OAuth then?

stoic laurel Sep 8, 2021, 11:26 AM

#

that lets you connect to existing accounts yep! But again, what does your platform actually do?

#

using read_only to connect to an existing account makes sense if you e.g. provide some reporting product for the connected account(like visualising their revenue or you listen to their webhooks and trigger things in some external system)

#

if you want to process payments with the account, you generally would be suggested to use https://stripe.com/docs/connect/enable-payment-acceptance-guide (and this creates an account for the user to use exclusively with your platform) instead of OAuth.

surreal stag Sep 8, 2021, 11:28 AM

#

stoic laurel well it depends really! is there a specific reason your platform wants to connec...

My platform allows Consultants to create their own new stripe accounts (to get paid!) or to connect to their existing stripe acct (which is what I'm testing w my own stripe acct)

#

My platform setup: Standard Connect with Direct Charge btw a user and a Consultant.

stoic laurel Sep 8, 2021, 11:31 AM

#

My platform allows Consultants to create their own new stripe accounts (to get paid!)
Standard Connect with Direct Charge
great! then you should use https://stripe.com/docs/connect/enable-payment-acceptance-guide and forget about OAuth I would say.

#

you can try to connect to existing accounts using OAuth but again, if you want read_write access(which you probably do since you want to create Charges on their account), it will only work if their existing account doesn't already have another platform connected to them(https://stripe.com/docs/connect/oauth-changes-for-standard-platforms) so it's of limited use.

#

We really intend for you to build things that way(with /v1/accounts) and have the user create a new Stripe account for use with you even if they happen to have an existing one, it's an intentional design(and change from how things used to work); OAuth is mostly for legacy platforms and for "Extensions" that just do read_only reporting like the example use cases I mentioned above.

surreal stag Sep 8, 2021, 11:34 AM

#

stoic laurel > My platform allows Consultants to create their own new stripe accounts (to get...

This is exactly what Ive setup here, so you mean that each Consultant will have to re-create a new stripe acct just for being connected to our platform? This is no good UX...

#

because that setup enables acct creation only

stoic laurel Sep 8, 2021, 11:37 AM

#

so you mean that each Consultant will have to re-create a new stripe acct just for being connected to our platform? This is no good UX
yep! I take your point on the UX but again, this was an intentional design

#

it allows for data to be separate between platforms and it also allows you to have more control over the account since it's not shared with other platforms : https://stripe.com/docs/connect/platform-controls-for-standard-accounts

#

also the onboarding should be pretty quick since we share the legal entity state internally so you shouldn't have to fully sign up again https://support.stripe.com/questions/legal-entity-sharing

#

totally take the feedback, it's a big change!

surreal stag Sep 8, 2021, 11:47 AM

#

Sorry, was away.
I got it. And indeed, stripe accounts for the same person as grouped within same dashboard if same email is used right?

stoic laurel Sep 8, 2021, 11:49 AM

#

yep!

#

Upon completion, two Stripe accounts will appear under the toggle menu in the top left hand corner of your Stripe Dashboard. like mentioned in one of those links, and you see them on your profile page like the one you looked at earlier to get the acct_xxx

surreal stag Sep 8, 2021, 11:56 AM

#

Indeed, I see both of them.
But i did have to complete an entire registration process with address, bank details etc... Any shortcut possible to improve that user exp?

stoic laurel Sep 8, 2021, 12:00 PM

#

nothing you can directly control no

#

as I linked above there is a concept of sharing the information but maybe it doesn't work in test mode or not in your specific case, it's hard to know; either way this is something below an abstraction layer from your perspective

surreal stag Sep 8, 2021, 12:01 PM

#

I'll recommend th users to Connect with the same email address then

#fredkzk-connect-onboarding