#pocketvendor_api
1 messages ยท Page 1 of 1 (latest)
๐ 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/1352009324838256670
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hello there
I'm not sure what you are referencing exactly with onbrd_xxxx, but no, that's not an object we expose in our API.
When a user wants to onboard you should generate a fresh Account Link.
That is indeed the proper way to do this.
Which is what is generated at https://dashboard.stripe.com/connect/accounts/overview, then pressing +Create.
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
Yeah that's an OAuth link so that is a bit different.
But overall that isn't the way you would want to programmatically handle onboarding
I've used AccountLinks as well, but merchants have a hard time with it. They'll click it, then try to go back later to see it expired. (e.g. https://connect.stripe.com/setup/s/acct_1R4StKQoLdcTawXs/4Cluy6jBxwDl)
You should be using the Connect Onboarding flow: https://docs.stripe.com/connect/standard-accounts
I do, as my platform doesn't require all accounts to be CBSP.
It's for a small subset of people that want to install my POS apps on their readers.
Ah you are onboarding already-created accounts.
So basically they want to setup a new account very quickly
To be CBSP, to allow for registering/installing
For CBSP you should use the flow I mentioned above.
... it's the most efficient way I've found so far, unless you have a better idea!
If you are onboarding already-created accounts then you should create your own OAuth link: https://docs.stripe.com/connect/oauth-standard-accounts
You really should only use the Dashboard generated link for one-off onboardings
Maybe I am misunderstanding, but are you saying I can convert Standard Connect accounts to be CBSP?
No
My app has onboarded hundreds of thousands of users via OAuth over the last 10 years, and none get converted to CBSP so I assumed I had to do this
New accounts created by your platform will be CBSP.
To do that, you use Standard Connect Onboarding.
Right, but not all accounts are new that OAuth with my platform
These people may already have an account, connected to another platform, but still want to use the POS on the S700
Also I was born in Bismarck ๐
Yep if they already have an account you can connect them via OAuth.
However you won't have platform controls (CBSP) for those accounts.
Right
You are saying your issue is short expiring OAuth links, right?
Short expiring links for these people to create a new Stripe account, secondary to their main account, for S700 installation
I've done it both ways (AccountLinks and the Dashboard button). But the latter requires me to send an additional support email to them. I was hoping to make it self service.
- User visits my website
- Toggles country
- Website creates link to create new (cbsp) account
Which ideally looks like this: https://connect.stripe.com/oauth/authorize?redirect_uri=https://connect.stripe.com/hosted/oauth&client_id=ca_55LxoMsExjmikRwlsg4mVe5fPQpgb8qg&state=onbrd_Ry3V95Ue8aN6e8Xr2ZEKRd6hW0&response_type=code&scope=read_write&stripe_user[country]=US
as the expiration is 7 days and doesn't require me to know an email to create the account to start.
You can do all of that with the Connect Onboarding flow: https://docs.stripe.com/connect/standard-accounts
You don't need an email
Just the country as you stated.
But this is the 5 min link, not 7 days correct?
So they visit your website, toggle country, you create a Standard Account, you redirect them to onboarding via an Account Link. If they leave and return then you create a fresh Account Link to redirect them back to onboarding.
That is the typical and recommended flow here.
Yep
Thank you for clarifying. I guess the point I was hoping to avoid was having to regenerate a link each time it expires, but sounds like that is unavoidable
And lastly, will this flow create a sub-account or should they be logged out to use it?
Consider this: will the user, who already have a Stripe account, be able to use the toggle in the upper left corner of the Dashboard to get to this new account, or will they need to log out and into a new account?
If they use the same login for the new account then yes they can toggle between all of their accounts with that login.
Awesome, thanks for your help!