baller-connect-onboarding

[grave sky]

The Account Link URL should be visited by the connected account. Similar to Express onboarding, Stripe will walk them through the necessary onboarding form(s)

If you're trying to simulate the connected account visiting the Account Link URL, I recommend visiting the link in another browser or using an incognito/private browsing window

[grave sky]

@inner jungle let me know if you still need help!

[inner jungle]

hm

I am visiting the url as the connected account

but I'm not seeing any setup page

just a login page

[grave sky]

did you try in incognito/private browsing mode?

[inner jungle]

is it possible to hop on a call? I feel like it will be easy to show

[inner jungle]

yes

[grave sky]

No, we don't have screenshares or calls in this channel

[inner jungle]

ok no problem

like a direct call? Is that possible?

just been struggling with this for a while, not sure what I'm doing wrong

[grave sky]

Is this what you see when you navigate to the account link URL for a standard connected account? If so, this is expected

[inner jungle]

yeahh that's exactly what I see

but its asking for a pasword, the create account api has no password field even.. I'm a littlee confused. I thought this step should prompt for account setup, and actually create the stripe account. Not login.

[grave sky]

This flow will prompt for merchant/business information after this screen. The reason you see a password field above is kind of separate: each user account on Stripe can have access to multiple merchant accounts. So, you can log into dashboard.stripe.com as [e-mail] and have access to multiple merchant accounts

[inner jungle]

ah ok that makes sense

[grave sky]

If you're using Stripe for the first time, the "Continue" button will prompt you to set a password to create your user account

[inner jungle]

ahh ok

yep I just tested that out and it worked with a different email

so one thing I'm still confused about

This is how I'm creating the account in django

        if not request.user.wallet.account_id:
            account = stripe.Account.create(
                type="standard",
                country="US",
                email=request.user.email,
                business_type="individual",
                business_profile={"product_description": f"{request.user.username}'s account/"},
                individual={"first_name": request.user.first_name, "last_name": request.user.last_name, "email": request.user.email},
            )
            print(f"account id: {account.id}")
            request.user.wallet.account_id = account.id
            request.user.wallet.save()
            account_link = stripe.AccountLink.create(
                account=f'{account.id}',
                refresh_url=f"{BASE_URL}/accounts/user/stripe/reauth/",
                return_url=f"{BASE_URL}/accounts/user/stripe/account/",
                type="account_onboarding",
            )
            return JsonResponse(account_link, status=200)
        return HttpResponse("Account is already connected to stripe")```

I see the account in the dashboard after stripe.Account.create. I'm still confused as to what the password is though? The user is never prompted for a password and API never asks for one.

I'm guessing that the stripe page detects that the account with email [e-mail] already exists since I created it in this step. but I haven't provided any password for the account. s there a default password?

this is what I see in dashbaord btw, so the account does exist, but just unsure of password since I never provided one in the API call

[grave sky]

that's correct, we're detecting a user account with that email exists. there is no default password

The confusing part here is standard accounts have full access to the Dashboard so, as part of onboarding, a user account is needed (either by linking the newly-created merchant account to an existing user account, or by creating a brand-new user account)

[inner jungle]

ah I think I might know what happening

so my app prefills the form with some user info that the user entered while registering their account on our app. I created a test user with a random email "[e-mail]" but I think by coincidence, this email alrady has a stripe account connected to it. So it prompts me to login.

Could this be a possible explanation? Or is it due to the fact that I created this account through stripe api?

[grave sky]

Yep you got it!

[inner jungle]

oh, I think I just understood your point, my bad. So this API that I called creates a merchant account, but I also need to create a user account and connect the merchant account to it right?

[magic wing]

there's no "user account" or "merchant account"

baller-connect-onboarding

[inner jungle]

ah ok I think it must be this then

but then shouldn't the create api fail? Create api should reject and say that user with that email already exists.

[magic wing]

No there's no such validation today as far as I know. They can have multiple separate accounts under the same email address

[inner jungle]

ah

but then in user setup how would I check to make sure that account doesn't already exists

is there another API I can call?

[magic wing]

There's no reason to do this.

I'm really sorry, I don't understnad the way you describe the issue at all unfortunately

[inner jungle]

so the use case is as follows

a user registers their account on my platform, they enter an email and other required info

then they can setup or connect a stripe account by entering payment information. I follow the standard account onboarding. I prefill some of the account information based on the information they provided when they registered on my platform.

The issue is that if that email is already having a stripe account, it will prompt for login

ah I guess in that case they can just change the email