Godspeed

[weary oriole]

Hi there!

I'm not familiar with Figma, so I'm not sure exactly what you mean.

How are you creating the subscriptions? With Payment Links, Checkout Session, the Subscription endpoint, etc.?

[jovial helm]

Currently using a Checkout Session in my .NET web app

Created with Stripe.net

[weary oriole]

1. Does Stripe automatically recognize if the input email / info is the same, and merging it into the existing customer object? Or does it create a new, even if the mail is the same?
   It will create a new customer, unless you specifically pass the customer parameter https://stripe.com/docs/api/checkout/sessions/create?lang=node#create_checkout_session-customer

2. Is it recommended practice to have one customer id that has all subscriptions? Or to have one customer id per subscription?
   That's completely up to you. But using a single customer might be better, since you would only need to collect the payment information once.

[jovial helm]

okay, so even if all the information is identical to an existing customer object, you need to pass the customer id in to the session to link it?

[jovial helm]

makes sense - but what if I want to let a user sign up to a Team Subscription for a group of users.

With a single customer id, there would only be one user (the buyer) who could access the billing portal and manage this subscription. Otherwise, the other users would be able to see and manage all of their subscriptions, which would be out of scope.

But what if I wanted to let them transfer the sub to another user, e.g. if they leave their company? Or to allow multiple users in the group of users to access the billing portal? Does this require a different system, or should it be possible with subscriptions as well?

[weary oriole]

okay, so even if all the information is identical to an existing customer object, you need to pass the customer id in to the session to link it?
Correct.

makes sense - but what if I want to let a user sign up to a Team Subscription for a group of users.
To me that sounds like a single subscription, but that will impact multiple users of your application?

[jovial helm]

yes, indeed! I have an app with specific features for groups of users (e.g. companies or sports teams), and a user should be able to sign up for and create multiple groups as well (e.g. being in multiple sports teams).

[weary oriole]

Then I recommend creating just one subscription, and then managing your users access though your own app.
FYI we have a per-seat pricing model for subscription, https://stripe.com/docs/products-prices/pricing-models#per-seat

[jovial helm]

Alright, thank you