#faaz_api
fossil vesselBOT
👋 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/1465868058315980842
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tepid wharf
I would expect to see a list of existing accounts tied to the login email like the first or second image . But I'm seeing it ask the customer to always create a new account
amber ledge
👋 hi there, give me a moment to catch up
tepid wharf
hello @amber ledge no worries. I'm just trying to provide as much info as possible. I also see weird developer console logs when the customer is trying to use the generated standard link. I can provide those if it would be helpful
amber ledge
A possible a reason why your customer don't see an option to link their existing standard account to your platform could be that your customer's account is already linked to another platform.
Do you have your customer's Stripe account ID? (i.e. the Stripe account ID you're trying to have a connection with)
I can do a lookup to check if that's the case
tepid wharf
@amber ledge Thanks, I did not grab that but I will get you those ids. It might be a little wait. This customer does already have hundreds of stripe standard accounts connected with us and this wasn't an issue until this past year.
amber ledge
Hmm..could you share one of the account ID that successfully connected please?
tepid wharf
Yes, acct_1D6qVvEJnu0k0tTT
amber ledge
Thank you, at least for this connected account, I can see it is only connected to one Platform, likely yours (acct_18WDA5CMpnBh61hX)
We will still need to check using the IDs to some of the accounts you're intending to Connect with.
Ideally, you should ask your customer to contact Stripe Support to ask why their existing accounts aren't able to connect to your platform. This is because your customer likely needs to be present to authenticate the support request for our team to look into their account. You can ask your customer to provide screenshot to aid the investigation
tepid wharf
Thank you. The customer has talked to Stripe support in the past and support, from what was relayed to us, said the issue was that it was because we were using an outdated Stripe version with the oAuth way and that we should support the new Networked Onboarding API. So we updated the Stripe Version when generating the Standard Account Link and added a way to use the new Networked Onboarding API flow, but no luck.
Not sure if any of these console logs are relevant either. But included them
amber ledge
Hmm..I'm a little confused. The purpose of Networked Onboarding [0] is to share business information, so its about reusing information and not connecting existing accounts.
Connecting an existing account usually require the customer to use the same email and password as their existing account during onboarding
Is this the OAuth guide your integration is following: https://docs.stripe.com/connect/oauth-reference ?
tepid wharf
Apologies, i'm going AFK soon for the end of my day. Yes, it is. So they don't mind creating a new account, which is why we added support for Networked Onboarding, the paint point for them lies in re-filling out the business information everytime. So fixing that, for either the oAuth API for connecting the Standard Account, or using the new Networked Onboarding API to just copy it over solves that for them.
amber ledge
I see, thanks for clarifying. If you still want to look into why some of their existing connected account can't connect directly to your Platform, you can contact us again with the account IDs.