#meh-connect-oauth
wooden wolf
Hello
Hmmm that doesn't sound right overall
They should be able to choose the account they want to connect after they login on the initial screen stating they already have an account.
That said let's back up a second...
You are using OAuth here yes?
static prairie
yes
i use the account link create api endpoint with 'type' => 'account_onboarding', set
wooden wolf
Hmm you wouldn't use Account Links with OAuth
Are you following this flow: https://stripe.com/docs/connect/standard-accounts ?
static prairie
sorry i was looking at the wrong code. yes we're following that process
the accounts link was for returning them to onboarding later
wooden wolf
Yep okay so that process always creates a new account
static prairie
here is an actual ticket from a user:
That customer service stripe account does have access, but it is not the stripe account I want to use for hooking everything up.
When I click “update account” in the payment settings for the storefront we've already upgraded, it prefills the correct email address, [redacted]```(we create a connect account per store)
limpid pendantBOT
wooden wolf
If you are trying to onboard already-created accounts then you need to use the OAuth flow
static prairie
"OAuth is not recommended for new Connect platforms. We recommend using Connect Onboarding for Standard accounts instead."
^ from that page 😄
wooden wolf
Correct. That is the recommended route if you are creating new Standard Connected Accounts
If you are onboarding users who already have a standalone Stripe Account then you have to connect that standalone account to your platform via OAuth, not create a new account for that user.
static prairie
hmm ok