#cblin-connect-standard
eternal tartan
ah ok...
so I do I propose a link to an owner of an existing stripe acount ?
balmy spruce
You should use OAuth for existing accounts instead: https://stripe.com/docs/connect/oauth-standard-accounts
eternal tartan
alright, I will look into that
Ill go back here if I am not able to proceed
thank you for the very fast answer 👍
balmy spruce
Np!
eternal tartan
I can see in the docs :
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 won’t be able to connect to accounts that are controlled by another platform.
does it mean it is not ok to do that ? if so, I dont grab the reason why ...
or maybe it just mean that I must not request read_write scope ?
balmy spruce
We rolled our some changes for how standard accounts interact with multiple platforms. It's outlined here: https://stripe.com/docs/connect/oauth-changes-for-standard-platforms
eternal tartan
if I understand correctly, with oauth read_write, I've a complete access to the other account so I can see all their transactions
whereas with a new account, I only have access to the trnasactions I'm doing
is that correct ?
balmy spruce
It depends on if the existing account is already connected to a platform:
When connecting a second platform to a Standard account controlled by another platform, the user will create a new account to use with your platform instead. The Connect Onboarding flow will automatically direct users to create the new account. Your platform will then be automatically connected to the new account that the user has created.
eternal tartan
ah ok so if the existing is not already connected, that's fine but otherwise it's now required to create a new account
balmy spruce
Yep, but the OAuth flow will handle that automatically for you 🙂
And to the end user there's no difference
eternal tartan
so he will still see my transactions inside is own account (he wont be required to login to the new account) ?
robust dagger
Hi there 👋 jumping in as my teammate needed to step away.
eternal tartan
hi toby, thanks for stepping in
robust dagger
With the recent changes to account control, we now recommend that you create a new account whenever you onboard a new user. You can use the OAuth flow to try connecting to an existing account, but if that flow detects the existing account is controlled by another platform then it will quietly create a new account anyway.
eternal tartan
ok I get this
so maybe I found something strange with the "new" way
I mean, I followed https://stripe.com/docs/connect/standard-accounts
- I created a standard account
- I created an account_link
- the user opens the url and use his stripe email+pwd+2FA
- stripe asks all the company details that are already in the user account ...
i need to say that I've at the moment zero connected accounts so it's not a problem for me to use the new way (but i's a problem for my users to refill the data they already have in their existing stripe account)
robust dagger
Apologies for the delay. I believe that is expected behavior with this flow.
robust dagger
Any time!
eternal tartan
Final question : if the oauth is now not recommencded, can this feature be completely deleted in the foreseeable future ?
robust dagger
I haven't heard anything about that happening yet.
eternal tartan
ok