#scif_unexpected

1 messages Β· Page 1 of 1 (latest)

pine sandBOT
#

πŸ‘‹ Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

πŸ”— This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1314440830966038569

πŸ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

signal plaza
tough raven
#

Does your Connected Account already connect to another different Platform?

signal plaza
#

@tough raven , nope
Settings β†’ Team and security β†’ Installed apps are empty

#

Moreover, newly created accounts New business were immediately disconnected from platform so for sure there are some accounts which are not connected

tough raven
#

Okie, are you using the OAuth URL or the Account Link URL?

#

Also, what type is your Connected Account?

signal plaza
#

Oauth URL

#

Also, what type is your Connected Account?
Standard one

tough raven
#

Yeah that should works though. Was it working in the past but stopped recently?

signal plaza
#

Yes, it's was working for ages (5+ years) and suddenly stopped working. I mean the authorize url is properly composed but Stripe's connection page went mad

tough raven
#

Can you share the Test mode OAuth url?

signal plaza
#

Btw, how to make sure the connected account is standard? The account allows to have team members and was created manually by the merchant

#

Can you share the Test mode OAuth url?
The one with client_id and other arguments?

tough raven
#

Yeah the one. And a normal Stripe Account can be considered a Standard Connected Account once connected

signal plaza
#

I don't use test mode for production account. Do you want me to create the url for any other account?

tough raven
#

The URL is from the Dashboard, correct? You can just turn on the Test mode toggle and copy the link

signal plaza
#

Nope, I use OAuth::authorizeUrl($params) to build the url

tough raven
#

Sorry, can you share the Doc you are following to create the URL?

#

Or the request Id (req_xx) from your Dashboard log that created 1 OAuth URL

pine sandBOT
signal plaza
#

Will provide you with the request id in 5 mins

#

Hm, there is no request id as this is an url to oauth rather than to API

winged raven
#

Connecting an existing account using OAuth is no longer recommended due to one account to one platform policy. This means that an account that has already been connected to another platform won't be able to connect to yours.

https://docs.stripe.com/connect/oauth-reference

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.

You should create a connected account for your own platform instead: https://docs.stripe.com/connect/standard-accounts

This reference lists available public methods for our OAuth endpoints for Connect.

Use Standard connected accounts to get started using Connect right away, and let Stripe handle the majority of the connected account experience.

signal plaza
winged raven
#

I understand that. What I am trying to explain is that in production, an account would have been connected to a platform, not specifically to your own account.

Your integration shouldn't use OAuth flow at all, i.e. never use an OAuth link to create an account at all.

signal plaza
#

The account was created by a merchant beforehand.

#

an account would have been connected to a platform, not specifically to your own account
Could you please elaborate on that?

winged raven
#

In production, your merchant might have a Stripe account connected to another platform not yours. With the single platform policy, this account will not be able to connect to your platform.

The recommended solution is to always create a new connected account for your merchant instead of allowing them to connect an existing account: https://docs.stripe.com/connect/standard-accounts

Use Standard connected accounts to get started using Connect right away, and let Stripe handle the majority of the connected account experience.

signal plaza
#

@winged raven , my Stripe user was granted admin permission in merchant's account so I checked Installed app which I mentioned before

winged raven
#

Are you using integrating Stripe Apps or Connect?

signal plaza
#

Connect

#

Could you advise how to make sure there is nothing connected yet?

winged raven
#

Is there any reason why can't you create a new connected account for your merchant? OAuth is no longer recommend and creating the new connected account is the recommended solution

signal plaza
#

I created a ticket to investigate this but currently business cannot complete onboarding of clients.

winged raven
#

This channel is for direct technical integration questions with Stripe. We don't have necessary expertise about the loading page in your screenshot. Our support team will be able to assist you better than I can: https://support.stripe.com/contact/email. Please include the OAuth link and connected account ID (acct_xxx), so that they can check why this happens.

In summary, OAuth flow is no longer recommended and you should create a new connected account.

signal plaza
#

Wow, it's a bit unexpected outcome of 1.5 hour long conversation πŸ™‚ Ok, thanks!

#

Just one final question β€”Β we should use /v1/accounts to create a new Stripe account for merchant. Then to use Account Link in order to authorize my account to make purchases on behalf of the newly created account. Is this just a replacement for oAuth authorization routine? What's about deauthorizing the app?

winged raven
#

When you create the connected account with /v1/accounts, the account has already been connected to your platform. The Account Link is for your merchant to complete the onboarding process. This is the replacement of OAuth integration

#

Your platform has full control of the connected account since this connected account belongs to yours

signal plaza
winged raven
#

If the ticket here refers to the Support ticket with Stripe, I'd recommend following up with them

signal plaza
#

Whooops, I quoted wrong message πŸ˜„

#

Could you advise how to make sure there is nothing connected yet?

winged raven
#

I'm afraid there is no good way to check whether an existing account is connected to another platform

#

If you're using OAuth link to create a new account like the screenshot above, our support will be able to help on why the onboarding can't be completed. This can't be controlled by the API or code

signal plaza
#

What's about installed apps?

winged raven
#

Stripe Apps and Extensions under Installed apps are the platform that extends Stripe's user experiences

#

As a platform, there is no way to check whether an account is connected to another account

signal plaza
#

My stripe user was authorized to have access to merchant's account