#BrooklynAndy-connect
1 messages ยท Page 1 of 1 (latest)
hey @frank plinth -- I've re-opened this
Thanks @hoary plaza
We're building a platform for small activities studios (dance etc).
My understanding was that Stripe Express was the best way to implement a platform based payment system for these businesses. Ie they sign up with us, they create a stripe account through Stripe Connect Express, then we manage payments on their behalf
In this model:
Us: The Platform.
The studio: "Users"
Their customers: "Customers".
A Customer signs up to a class via The Platform, attaches a payment method (card), and attends a class and makes a payment.
The Platform initiates a payment on the User's Stripe Account, via Stripe Connect.
The Platform can take a small fee for this transaction, on top of the basic Stripe fee.
The Customer sees a charge from "Bobs Dance Studio" on their bill.
Bobs Dance Studio can log in to The Platform, and see payments being made by their Customers. They can also click a button and get sent to their Stripe Express dashboard under the Stripe domain.
Hey there, just coming back to this
What exactly do you need help with?
I was expecting more messages or a question
I want to make sure we understand the domain model correctly
What you've stated so far is valid and makes sense
Ok great.
This sounds like a good fit for Express account usage ๐
We wanted to make sure we understood how the model for how Express works etc
Why would we need Custom over Express? Just out of interest
I guess the other question(s) I have are around disputes. Who "owns" the dispute process in the Express case?
Custom would be for when you want more control over the connected account experience: building your own dashboard for account holders etc
You should use test mode to try the onboarding & Express dashboard experience your connected account will see
along with test payments and payout etc
Express still gives us some ability to display account information on our own Platform though, correct?
Sure, you can build more information into your platform if you like, but its optional
with custom you must build this, as nothing is provided out of the box
Ok awesome, thanks for confirming
Yea i went through the RocketRides example
But that's a little different because the customer would see a charge from RocketRides
We wanted to have that charge come from the equivalent of the driver
if that makes sense
Re-upping that question around disputes. Who "owns" the dispute process and how does that work?
Ie the Platform has a User. A User's Customer makes a payment, that is then disputed.
How is that managed? Does the dispute count happen on the User level or the Platform level?
Do you want your platform to appear to the customer at all?
or only the connected account?
(on the bill)
Ideally just the connect account. But not the end of the world if we show up as well
But the connected account should show up
Alright, you need to review how statement descriptiors work for connect here: https://stripe.com/docs/connect/statement-descriptors
and you'll note for what you want with destination charges you'll end up needed to use "on behalf of" to specify the settlement merchant: https://stripe.com/docs/connect/destination-charges#settlement-merchant
Disputes remain the responsibility of the platform: https://stripe.com/docs/connect/accounts#choosing-approach
though Stripe does try to debit the connected account bank account in supported regions: https://stripe.com/docs/connect/account-balances#accounting-for-negative-balances
With Connect, you can create charges on your platform account, take fees, and then transfer remaining funds to your connected accounts.
Ok, thanks thats good to know!!
Thanks for the links, will give it a bit more reading and share with our engineers
Thanks @hoary plaza
NP! Good luck ๐