#greg_best-practices
twin summitBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can 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/1255951659251667114
đ Have more to share? Add details, code, screenshots, videos, etc. below.
desert prairie
Hello! It's common for a Customer in Stripe to represent a business or other entity with multiple people. There isn't a better way to model what you're describing, really.
Just to make sure I understand fully, though, when someone at the business decides to upgrade to a paid plan, that paid plan would apply to the entire business, not just that individual, correct?
crystal shard
Correct.
desert prairie
Yeah, in that case having a single Customer that represents the entire business is appropriate.
crystal shard
Got it. And then I just update the email of that Customer and handle who is allowed to edit subscriptions, payments, etc. on my end?
desert prairie
Yeah, in a case like this I recommend using the Stripe Customer to represent the business, and then keep track of details about specific individuals on your end, or in the Customer's metadata: https://docs.stripe.com/api/customers/update#update_customer-metadata
crystal shard
Got it. Super helpful, thanks. Just wanted to make sure I wasn't missing anything.
desert prairie
For example, the email on the Customer should probably be a generic company email, and then you'd keep track of specific employee emails elsewhere.