#NewtReyes-account-type
1 messages · Page 1 of 1 (latest)
Here's the id: acct_1KTaAYC433BEDSLz
Also, we tried to OAuth into this account, but when we tried, Stripe created a new account instead of using this one. Any idea why?
Hello 👋
You can try retrieving the account using the API and check type property to see the account type
we tried to OAuth into this account
can you provide more context on this? As in what did you try using OAuth flow?
We have a Stripe Connect Platform Account
We implementing OAuth authentication for our clients using the following documentation: https://stripe.com/docs/connect/oauth-reference
Now, when we tried to OAuth into one of our test standard accounts, Stripe created a new standard account instead of OAuth'ing into our standard account
We were told in the past that if a Standard account had already OAuth'ed using a different platform account, then a new account will be created.
Is that what happened here?
If so, is there any way to find out the id of the platform account a standard account is connected to?
Yup, Standard Accounts can only connect to one platform. If they try to connect to another account, a copy of that account is made and the copy is then connected to the platform.
is there any way to find out the id of the platform account a standard account is connected to?
it was designed this way for privacy reasons. I don't think it is possible to tell what other platform the account is connected to.
The account holder can visit https://dashboard.stripe.com/account/applications to check what they are connected to but its impossible for a platform to see that information.
Oh
I am the account holder
I should be able to see then
Mmmmm
No Authorized applications on that account as far as I can see
and nevertheless, we were not able to Oauth it to our platform account
instead, a new account was created
Any ideas why that happened?
FYI: The account that got created has id acct_1KUGi4J3dgba7z45
The original one is this one acct_1KTaAYC433BEDSLz
We are tying to understand if this is a problem on our side or just expected behavior
hmm interesting.
AFAIK this is expected in case the existing account is already connected to a platform. Not sure why it'd happen if it was NOT connected to a platform
Is there anything you can review on your side that could help us understand what happened here?
Yup
Do you have a request ID for the account creation by any chance?
Sorry
I only have the ids
The account that got created has id acct_1KUGi4J3dgba7z45
The original one is this one acct_1KTaAYC433BEDSLz
@brisk mesa jumping in, one sec
Thank you!!!