#Mikail

1 messages · Page 1 of 1 (latest)

errant horizonBOT
bronze breach
#

Any particular reason why you're using OAuth to onboard accounts? You could achieve this with Account Links, which is the recommended onboarding flow.

deft estuary
#

Reason we are using oauth is that we had issues with onboarding existing standard accounts

#

This was the response we recieved via email from the email support

After further research,it looks like you are creating an Account link[0] to connect the existing standard account to your platform, and I’m afraid this will not work. It is highly recommended to use a standard OAuth integration in order to connect the standard connect account to your platform[1].

deft estuary
#

This was done by an Indian user who has an existing Stripe account under the email address admin@mtlegalteam.com.

  1. User logs into their Stripe account.
  2. User demonstrates their Stripe account is active & valid.
  3. User initiates on Stripe Connected Account onboarding on our website (Livelogue).
  4. User logs into Stripe as part of the onboarding.
  5. User elects to connect their existing Indian Stripe account.
  6. Stripe throws the user to a screen that looks like it's for a new UK entity (?). User is unable to connect their existing account (preferred solution) or to change country back to India and create a new entity (second-best solution).
#

this happened to 3 users from india

#

when we used account links

bronze breach
#

Well it would depend how you were creating the Account and Account Link

deft estuary
deft estuary
bronze breach
#

It can be, you'd just set the redirect_uri on a per customer/session basis when they click the link (https://connect.stripe.com/oauth/authorize?redirect_uri=livelogue.com/mikail)

bronze breach
deft estuary
bronze breach
#

Ah yes

#

In that case that's not an option I guess

deft estuary
#

with options

account: stripe_account_id
refresh_url: livelogue.com/mikail?{{query}}
return_url: livelogue.com/mikail?{{query}}
type: 'account_onboarding'

bronze breach
#

Can you share an example req_xxx?

deft estuary
#

sure

bronze breach
#

Checking

deft estuary
#

this one works, i can also try to send the url of the failed account

bronze breach
#

acct_1MlVW5IYg53eDDM0 is your platform account, right?

#

Sorry: acct_1K3zjCETJwELHMW2

deft estuary
#

not sure, need to check

#

one sec

#

by platform account, you mean the account on which we connect users right?

bronze breach
#

Ok, the issue is that for standard accounts the country defaults to the platform account country unless you pass the parameter (https://stripe.com/docs/api/accounts/create#create_account-country) on account creation. See: https://dashboard.stripe.com/test/logs/req_ap7W3FOHl22Dom

#

So if you know the country of your users, you'd pass country: 'in' for example when creating the account

deft estuary
#

aha i see, is there a way for it to default to their country where they already created their account?

bronze breach
#

FWIW, I just tried an Account Link with an account I didn't pass country param and I saw a list of countries.

bronze breach
#

An alternative approach would be to keep the OAuth integration, and use a generic redirect_uri but also pass state that you can use to redirect to their custom page.

deft estuary
#

ok thank you, that helps a lot

#

can we leave this thread opened for a few more hours, so we don't loose context?

I have all this info now, need to process 😄

bronze breach
#

We normally close after ~1 hour, but we can easily re-open it if you need more help!

deft estuary
#

understood

#

thank you very much @bronze breach much appreciated