#Rahul1998
1 messages · Page 1 of 1 (latest)
Hm interesting. But if they're existing users, why did they need to go through the onboarding form again?
They are existing stripe users that are trying to complete the onboarding flow of a new connect account.
Our platform creates a new connect account for our customers and lets stripe take over the collecting information flow. We request a onboarding URL from stripe and redirect the customer to that page
So the endless loading is happening on newly created connect accounts?
No, it's happening for existing accounts.
That is why it is so odd, if a new stripe account is created during the onboarding flow, everything works fine...
I don't understand then. Why would an existing account go through the onboarding flow? That doesn't make sense
This is the API that generates the Connect onboarding URL https://stripe.com/docs/api/account_links. The first page that the user lands on when directed to the link is to create a new account of login with an existing email.
Complete reference documentation for the Stripe API. Includes code snippets and examples for our Python, Java, PHP, Node.js, Go, Ruby, and .NET libraries.
I understand, but Account Links are meant for brand new accounts to onboard and collect info
They're not meant for existing accounts that have already been fully onboarded
This is a brand new standard connect account.
But you told me right here the error is happening on existing accounts... #1104120109687111791 message
New standard connect account and existing Stripe account. Sorry about the misunderstanding.
Ok. So the existing account you're referring to is just the platform account under which you're creating new standard accounts?
My fault, I responded poorly for that question.
The existing account can be any stripe user. For example, I have my own stripe account. I generated a new standard connect account under our platform account. I want to complete the onboarding flow for this new standard connect account. However, when I try to login with my own stripe account, I am stuck in this screen.
according to the network logs, ajax/connect/seamless_standard/associate_user/<account-id> api returns with "This action requires additional permissions"
Yes, acct_1N4F9Y2YzfEXG0iM is the new standard connect account. Will you need the platform account id as well?
I can get it from that
That verification code above is for when you try to log in to your platform account?
No, it's when I try to get started with the new standard connect account onboarding flow.
I have no issues logging in to the platform account.
Ok and that screenshot of the verify your login page is in the onboarding flow (Account Links)?
Yep
Got it
Sorry it took so long for me to put this together
This is weird though
Let me rope in a colleague to help take a look
No problem, it is a very odd issue. We recently updated our API SK, but we do not see how it can be related. All other actions/payments are running smoothly after the key update.
Thanks!
Hey there @hoary pike -- i'm helping @marsh mural look into this
Are you explicitly trying to associate this new account with your existing dashboard user account, or is this incidental?
I'm curious whether this is the actual problem, or an intermediary problem you're having while trying to support a user who is having other issues while onboarding
This is the actual problem. Our users and us are getting blocked at this step.
You users are also getting an onboarding link from you for a new account and trying to log in to their existing dashboard user accounts, and describe this same issue you're having?
Yep
Ok, thanks for clarifying
We also reproduced with other coworkers
For your own case, is the account you're logging into the same one associated with the platform?
or a different/separate dashboard user account?
(trying to be clear here to distinguish stripe accounts from dashboard user accounts)
Yes, I tried one user account that is associated with the platform and one user account that is not associated with the platform.
Perfect, thanks.
Thank you for the update!
@hoary pike I was informed that we deployed the fix, can you try now?
It works now! Thank you so much!