keithm5699

[opal violet]

In case it helps, this is the url of a test account we tried this on:

Not Working: https://connect.stripe.com/setup/s/acct_1OX03oEQ1o18FOEN/6BaxAlFkraaj

[feral slate]

This is just how onboarding via Acocunt Links works. It'll create a new Account (acct_xxx) that will be associated to their existing Stripe login credentials

[opal violet]

Working (Legacy platform): https://connect.stripe.com/oauth/v2/authorize?response_type=code&client_id=ca_7BxPXHpPffiSdXD2KEkcg0fFDyt6TRSk&scope=read_write&stripe_user[email]=[e-mail]&stripe_user[url]=https://mysplink.com/freetesttom&stripe_user[business_name]=freetesttom&state=4fb1348bf48db97ae369e165423d2a93

[opal violet]

Ah ok, so what would be the best way to get around this? I believe we used account links so we could prefill some data

[feral slate]

Yep, OAuth (legacy) onboarding allows users to use their existing acct_xxx with multiple platforms. That is deprecated largely though

[feral slate]

Get around what specifically?

[opal violet]

This limitation, we want existings stripe users to be able to use their existing accounts so they don't have to go through kYC, but we want to prefil some data for new stripe users to make the flow easier

[feral slate]

If you want to prefill fields then you can pass those parameters on Account creation

In cases where the person already has existing Stripe account(s) then we do automatically attempt to reuse existing verification/KYC data to de-duplication collection and simplify onboarding

Likelihood is you're not seeing that in testing because it's not configured to do that

[opal violet]

This makes sense and thank you for the quick responses. The problem is this was brought to our attention by a client that is saying they are being forced to re enter their KYC and they are a large org so need to go throug ha lot of layers to get this

Let me see if I can get their account id that they last used to try this

[feral slate]

I'd recommend you raise these concerns with support directly. It's not an integration/API issue as there's nothing that can be done to prevent the recollection of KYC info: https://support.stripe.com/contact

[opal violet]

Ah ok, thank you

ust to confirm there isn't another non deprecated way to create connect accounts we could use that would let you select an existing account?

[feral slate]

Unfortunately not

[opal violet]

Ah ok, thank you very much for the quick responses / help

Have a great day!