#videovillain_best-practices

1 messages · Page 1 of 1 (latest)

velvet sluiceBOT
#

👋 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/1291028899962032280

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

tough crag
hoary kiln
#

We are also wondering, since we have the subscription as well, how to separate things like the subscription from the 1on1 coaching payments, for tax purposes, to provide a receipt and tax info to the coach. Is that sort of separation easy to do for a coaches stripe account?

tough crag
#

Subscriptions and One-time PaymentIntents are separate objects so yeah should be simple enough to differentiate

hoary kiln
#

So just to be sure, Stripe Connect is definitely the way to do this player -> coach payment right?

tough crag
#

Yes as you're felicitating the services as a platform, Stripe Connect is the way to set these up.

hoary kiln
#

So the Connected accounts are the coaches and players accounts then?

#

they make Stripe accounts and we connect it to our Stripe account and then we can make API calls as necessary?

tough crag
#

The users that you want to pay out to -> you will need to create connected accounts for them. In your case, those would be the coaches right?

Players as they're just part of pay-ins (you don't pay out to players), you can just create customer objects for them

hoary kiln
#

Okay. But players can become coaches if they want to, at that point is there going to be a struggle to turn the customer object into a connected account?

tough crag
#

You can create a connected account for the players when they become a coach.. You should still keep customer objects separate as that will allow you to charge the players if they're still wanting to subscribe to a coach after becoming a coach themselves or if you want to charge the players for anything else

hoary kiln
#

Great! And we will either send a dashboard link to the connected accounts to the respective players and let them handle their dashboards that way or we can integrate it into our app right?

What should we be cautious of storing in our database when using Connected accounts? Is there a page of dos and don'ts specific to that?

#

Like, we can store the Customer ID in our database to retrieve that object's info. what about Connected accounts? do we store the ID only or is there more to worry about?

Will the connected accounts we make for the users be in any way associated with their subscription, or will it be completely separate?

tough crag
#

And we will either send a dashboard link to the connected accounts to the respective players and let them handle their dashboards that way or we can integrate it into our app right?
Yup, depending on the payment flow you choose and the type of connected accounts you create, you can do either..

What should we be cautious of storing in our database when using Connected accounts? Is there a page of dos and don'ts specific to that?
Like, we can store the Customer ID in our database to retrieve that object's info. what about Connected accounts? do we store the ID only or is there more to worry about?
I don't believe we have any best practices around that as it defers from usecase to usecase..

Will the connected accounts we make for the users be in any way associated with their subscription, or will it be completely separate?
Depending on the payment flow you choose, you can create subscriptions directly on the connected account if you prefer that. The other option is to create subscriptions on the platform, where the subscription object is owned by the platform but then you transfer the amount to connected accounts separately

hoary kiln
#

Depending on the payment flow you choose, you can create subscriptions directly on the connected account if you prefer that. The other option is to create subscriptions on the platform, where the subscription object is owned by the platform but then you transfer the amount to connected accounts separately

Sorry, I mean the subscription to use our platform to begin with, not subscriptions between coaches/players (we are only doing one-time payments between them for now, though we might allow recurring payment styles in the future)

I don't believe we have any best practices around that as it defers from usecase to usecase..

Is there anything we definitely don't save?

tough crag
#

Sorry, I mean the subscription to use our platform to begin with, not subscriptions between coaches/players (we are only doing one-time payments between them for now, though we might allow recurring payment styles in the future)
Oh typically I've seen platforms charge an application fee on each payment connnected account merchants accept. If you're modeling subscriptions for coaches too then you'd need to create a customer objects for them on your platform account so that you can have them save their preferred payment method and charge their saved payment methods.

Is there anything we definitely don't save?
Not that I know of..

hoary kiln
#

Okay thanks! So

  • Customer Objects for all users basically
  • Connected Accounts for people who become coaches
  • In-app dashboard for subscription management
  • In-app dashboard for course management
  • Store only what we is necessary in our database

Are web hooks quite necessary for Connected Accounts? And do you know if Laravel's Caschier handles all the necessary hooks already? or will we need to create custom hooks?

tough crag
#

Webhooks are essential to receive notifications about successful/failed payments, a connected account getting restricted for additional requirements etc..

Unfortunately, I don't know much about connectors so don't know if Cashier can handle everything automatically

hoary kiln
#

Alright! Well maybe it doesn't seem like it, but being able to talk it out like this is super helpful for me. Thanks a bunch!

tough crag
#

NP! 🙂 Happy to help