#anoop-nexeng_api
wispy epochBOT
👋 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/1423680082719015014
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
wanton ruin
Hello
I don't believe we send any emails to the Connected Accounts that are created via the API or the dashboard.
The flow is
- You create a Connected Account
- You create an Account link
- You share the account link with the Connected Account based on your preferred method
Generally, we don't recommend emailing, texting or sending the links outside your "application" meaning you'd bring the person onboarding on your website/application and then create an account link on-demand & redirect them (assuming you're using Stripe hosted onboarding)
vital willow
Thanks for the response.
Our usecase is this:
We have a platform (NexEng AI platform) where there are users, and each user needs to invoice their multiple customers (inside our platform through Stripe).
So, when a user signs-up to our platform, we create an analogous Stripe "connected-account" for that user immediately, which we could use for him/her to send their invoices to their customers. This creation of "connected-account" for them is through API.
However, if we have to share the connected account with them manually, we might have to do it for every single user who signs up, manually!
Is there a better way to achieve this? (AKA are we getting the flow wrong here?)
Summary of how our platform works:
- User signs up to our platform (NexEng)
- NexEng creates a "Connected-Account" via API for the signed-up user on Stripe
- User adds multiple customers on our platform
- User invoices those customers
- Customers pay those invoices via the Stripe payment link
- Money goes to the user's Stripe connected-account
wanton ruin
What type of Connected Accounts are you creating?
vital willow
If you're referring to the Business Type, most are "Companies" Connected-Accounts (US and Canada being the location). A few could be Individual.
These are not types accounts.
(Screenshot of an equivalent manual account to our API settings is attached)
wanton ruin
Ah you're using "Account properties"
They are an alternative to account types
vital willow
Should I be using "Types"?
Does that change the verification behavior?
wanton ruin
Not really, no. Account onboarding requirements are almost the same regardless of what type you use.
There are 3 ways you can onboard an account - https://docs.stripe.com/connect/onboarding
Stripe hosted onboarding is the easiest as you can create an Account link and redirect the user to that URL. Stripe will collect the required information and verify it.
With Connect, platforms like to control the experience with regards to how Connected Accounts go through the onboarding. Hence, we don't really send any emails ourselves.
You can though. For example, if a user returns to your website without completing onboarding - you can create a new Account Link and redirect them there - https://docs.stripe.com/connect/enable-payment-acceptance-guide?platform=web#handle-incomplete-onboarding
One more option would be to listen to webhook events. Specifically, account.updated - after creating an account you may receive account.updated webhook events for any activities on your connected account. You can look into the payload and check if the account has onboarded. If not, you can write your custom logic to send an email
vital willow
Got it. Okay, let me try these out. Appreciate the help.