#salonmonster_best-practices
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/1362175223948116208
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- salonmonster_error, 1 hour ago, 54 messages
๐
He suggested that we follow this guid to refactor our old stripe express connect: https://docs.stripe.com/connect/express-accounts
I notice that there is another option for doing it via embed:
https://docs.stripe.com/connect/design-an-integration?connect-onboarding-surface=embedded&connect-dashboard-type=express&connect-economic-model=buy-rate&connect-loss-liability-owner=platform&connect-charge-type=destination
Our app is both a web app and mobile app.
I'm thinking the embed option would work better for our mobile app.
We build using Ionic Angular (An angular app with a capacitor wrapper for mobile) What would you recommend from your perspective?
We want to use best practices
Do they both follow the same flow of:
- creating an express connected account and prefilling information
- Getting the user to complete the setup
Just reading through your previous thread here
Thanks
One thing to consider is that Embedded Components are only supported on mobile for the iOS and Android SDKs and even then, those are both in private beta: https://docs.stripe.com/connect/get-started-connect-embedded-components?platform=ios
Ok, thanks - that answered my question ... we'll steer clear of those for now ๐ We need a 100% solution
I appreciate the feedback
Yeah, Embedded Components are newer and I think they're going to be popular over time - they offer more granular control and customization and do more, but the functionality is still being fleshed out and the documentation, in general, isn't as full as onboarding using Account Links