#elfeloe-connect-oauth

1 messages · Page 1 of 1 (latest)

acoustic relicBOT
mossy ridge
#

Hi there 👋 I'm not sure offhand if that is possible, but am working on double checking that. In the meantime, if you access the page from a browser that has its default language set to something other than english, does the onboarding flow inherit the browser's default language setting?

tawdry egret
#

Hi Toby, thanks for the suggestion but it's possible that the end user will not have their browser language set to other than english and yeah I checked that oauth reference page but was hoping there was like an undocumented field that could be used to set the page language. Any possibility of this becoming a feature?

mossy ridge
#

Gotcha, I'm also not having any luck finding an undocumented parameter to pass to change the locale, and didn't have any luck trying to find how the page itself is triggering the translation to see if you can force that.

I can file feedback for this, but it isn't something I'd expect to be changed. We don't recommend the OAuth flow for onboarding accounts for new Connect integrations, we now typically reocmmend using Account Links instead, so I wouldn't anticipate seeing too many updates to the OAuth flow moving forward.

tawdry egret
#

Oh that's new. I hadn't heard of Account Links

mossy ridge
#

We began discouraging the use of OAuth with new Connect integrations in 2021, due to the introduction of Platform Controls and how those can lock accounts. I'm not sure which type of Connected Accounts you're using, so I'll point to the docs for Standard Connected Accounts for now.

There is a note near the top of this doc about not using OAuth:
https://stripe.com/docs/connect/oauth-standard-accounts
and it points to our currently recommended approach:
https://stripe.com/docs/connect/standard-accounts

tawdry egret
#

We are using the Standard accounts 🙂

#

Hmm this means we can't use the Account links with existing Stripe accounts?

mossy ridge
#

Correct, you would first create a new Connected Account. That flow is recommended because if an existing account is already controlled by another Platform when it attempts to go through your OAuth flow, a new Connected Account is created because an account controlled by a Platform can't be connected to another Platform. That new account creation happens without any awareness to the Platform, so you likely wouldn't realize you didn't connect to the existing account as you had intended to.

Always creating a new account and using Account Links helps to avoid any ambiguity with the flow where you don't whether you connected to a fresh account or an existing Stripe account.

acoustic relicBOT