xarm | Stripe Developers | Page 1

daring sandal Sep 10, 2021, 5:41 PM

#

It doesn't really matter on our end - you can have as many customers as you want with the same email/name and we don't do any duplication. As long as your integration is equipped/built to handle it, it's fine

tawny halo Sep 10, 2021, 5:48 PM

#

agreed with that position though I prefer karllekko's version of not having those on Stripe since you won't really use those customers and the important one is the customer for the "org"

quasi ingot Sep 10, 2021, 6:12 PM

#

thank you

#

the org's email or closest to it would be the org's owner, and that owner could have another org as well, thus creating to customer objects with same email

#

anyway makes sense thanks

#

in general with the conversation I shared above, using this modelling, is there a rationale for this vs. having a customer per user? instead of org

tawny halo Sep 10, 2021, 6:17 PM

#

Mostly the customer in Stripe represents the person who pays for something

#

So if you have one org that pays for 10 employees, having 10 customers for those employees won't really do much since they won't pay/have payments/have payment methods attached

quasi ingot Sep 10, 2021, 6:37 PM

#

I guess I was weighing customer per org vs customer per user that pays for an org, as opposed to every user

#xarm