#developerharris

1 messages · Page 1 of 1 (latest)

knotty badgerBOT
exotic nest
#

What you ask sounds like a Connect use case, when you are a Platform and there are multiple Connected Accounts. Depends on the Connected Accounts type (Express/Standard/Custom), the fund flow could be Destination Charges or Direct Charges or Separate Charges and Transfers

#

In case of Destination Charges / SC&T, each customer will still be customer of the Platform, where Platform shares some profit to the Connected Account

vocal sage
#

Ah I've never used connect, and it sounds a little daunting 😅 I'm not sure I understand how it applies

exotic nest
#

Reversely on Direct Charges, each customer will be customer of the Connected Account, share some comission fee to the Platform

vocal sage
#

Traditionally we've used Subscription and Customer portal flow before

#

we're not trying to route payments at all

#

we're essentially trying to mimic how Vercel has it setup if you're familar, where each user has a personal account, but also other teams they're assigned to

#

each team can be on it's own plan

exotic nest
#

I am not familiar with Vercel unfortunately, and even if I know how they are doing I can't reveal (I really don't btw)

#

But I think, conceptually, Vercel could be a Platform, and each team could be one of their Connected Account

vocal sage
#

I'm a little worried in leaving in the Subscriptions flow I've used before, just because I'm really not familar with platforms/connected accounts

exotic nest
#

Does Hobby/Pro/Enterprise changes per team?

vocal sage
#

yes

exotic nest
#

ie. you have $0, $20 and custom for Athena AI, but $0, $50, $100 with Camcorder AI?

vocal sage
#

oh do you mean different prices?

#

I can give a better written example

#

We're Camcorder AI, we're building a browser based video editing SaaS product where users can upload videos and easily extract clips to export to youtube/tiktok/instagram, etc

Each user, when they sign in for the first time, is created a personal organization that only they have access to.

However users can create teams where they can invite others, host projects & assets, etc. Each team would have it's own billing plan associated with it

#

And so in this case, I think each user would have their own stripe customer id, but then after a checkout flow the resulting subscription object would be tied to the team

exotic nest
#

How about letting "team" here a concept only exists in your own system? Tehnically when you communicate to Stripe, you just need a customer, and multiple Subscriptions they are in

#

Let's say your user A belongs to team X,Y,Z, you can have 1 Stripe Customer, with 3 activated Subscriptions

vocal sage
#

gotcha, and then each subscription would be associated with a team?

#

on my end

exotic nest
#

Yeah

vocal sage
#

cool I think that makes sense, so I'd create a stripe customer id for every user on signup and then based on whichever team they have selected in the frontend, bring them to the same checkout flow, but then save that subscription to the team

#

and then until we get our own UI setup we can just use Stripe customer portal to allow folks to manage which team they're doing the billing for

exotic nest
#

Yeah, but keep in mind Stripe Customer Portal can only display the Subscription description, so make sure the team name is clear there