#ynspc
1 messages · Page 1 of 1 (latest)
Your use case is a perfect example for Connect, can you tell me why you don't want to use connect?
I have already implemented this with stripe connect and while showing demo to the client; the platform account can view all the details of the connected account so client dont want to see the detail of the connected account. As the platform is not taking any commission from the connected accounts but the connected account subscribes to the appropriate plan of the platform
I still don't understand why you don't want to use connect.
Our main concern is not to see any detail of any connected accounts from platform account
What details?
connected accounts related information which are like
- its customers details
- payment details
- others
Can you tell why having connected account info is a problem to your client?
If i can recall properly
- want the connected account to handle everything at their own end like: creating subscription, payments, payouts and disputes
- since all other information is been seen from the connected account so, client believes we are illegaly viewing the data from the businesses
Other developer at office is consulting with support and have posted me this screen shot below
I'd suggest their leagal team to review the Connect Legal agreement https://stripe.com/legal/connect
Is there any way we can hide the information from the dashboard of the platform account?
No it is not. You'd need to build a custom dashboard/UI if that is problematic
Can you let me through some documentation to achieve the custom dashboard flow
currently standard connect account is being used so is it achieveable with this type of connect account or need to switch to custom type
There's no documentation really. You'd just utilise the APIs and build a UI that achieves the desires dashboard functionality you want
Is this also a solution for this use case?
Yes if the standard Stripe Dashboard doesn't meet your requirements. We have come UI components you can embed/utilise: https://stripe.com/docs/connect/connect-embedded-components/quickstart
Don't understand the use case
I have a platform where businesses register and use it to manage their businesses. Businesses pay fixed subscription fee to the platform. Each business have their own customers and they collect fees from the customers. The business does not need to pay any commission to the platform.
You're basically describing Connect there. Unclear about which specific part requires a custom UI/dashboard?
Yeah its so confusing, the use case clearly points towards connect but the connect dashboard is showing data which the client dont want in the dashboard which i have pointed above
Then you'd still utilise Connect, but just don't use our Dashboard and build your own as I've explained
If you're moving money between multiple parties, which your use case predicates, then you need Connect. That is a non-negotiable
Whether you use the Stripe Dashboard or build your own is entirely up to your needs. Obviously significant amount of work building your own but if that us your requirement then that's the only option
We will let client have meeting with stripe team for this use case. Mean while if you could give us suggestion to achieve this use case with alternative of connect account. Like creating separate stripe account.
There's no alternative to Connect for the business/use case you described I'm afraid