#romaten1-q
bright oxide
hi! if you have some specific development questions about coding with the Stripe API, please ask away
warped loom
We are developing an opportunity for our users to divide projects by workspaces. Each workspace will have its own separate subscription of one product. And there is a question how best to move the current scheme of "one user/one stripe customer/one subscription" to a new one. So far we have two options - 1) create one stripe customer for a single user and for each individual workspace add a new subscription for customer . 2) for each workspace add a separate stripe customer with one subscription. Regarding the first option - would it be a problem if there were multiple subscriptions for one customer? For the second - there will be a lot of customers with the same email. Perhaps you can advise which option is better, or is there a third option as well?
bright oxide
Regarding the first option - would it be a problem if there were multiple subscriptions for one customer?
not really, that's fully supported. Note that it generates entirely separate invoices instead of one combined one.
Other note is that all subscriptions have to be using the same currency.
For the second - there will be a lot of customers with the same email.
Stripe doesn't have any requirement that your Customer objects have unique emails so that's not a problem on our end at least.
I don't really have any thoughts or recommendations here, both approaches are valid so it's up to what works best for your systems and databases
warped loom
Thanks for help!