#dhew_best-practices
tacit quartzBOT
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always 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/1240008050417471529
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
marble oar
Hello! No, I don't think so.
coarse quail
Great--thanks!
May I ask another/somewhat unrelated question here about sharing payment details...or open a new thread?
marble oar
Sure!
coarse quail
On my platform, I have individual platform users organized into 'Companies.' If the Company (which would also be one of my Connect accounts, for when they were selling items) wanted to allow all of its sub-users (individual employees, each with their own email address) to be able to make purchases on my platform with the company payment methods (especially ACH), is there a good way to handle this?
marble oar
Not sure I completely understand. These companies are connected accounts to your platform, and their sub-users are... what? At the company connected accounts also platforms themselves, with their sub-users as connected accounts? Are the sub-users Customers on the connected account? Something else?
coarse quail
The Connected account is the "Company" and the sub-users are their employees. Consider a 2 person company: 1 owner, and 1 "buyer."
On my platform, the Connected account/Company could be both a buyer and a seller of items
marble oar
How are the employees modeled in Stripe?
coarse quail
This is what I'm solving for. I realized that when these companies go to purchase, my assumption is Stripe would treat each buyer as an individual 'customer', given they have individual email addresses. So they would each have their own payment methods, right? What I would like to understand is if there is a way to 'share' a payment method across these 'customers'. Put another way, the Company would be 'buying' the items (using their bank account, as one potential payment method), but through two different users/Stripe 'customers' (I think).
First thought was maybe allowing the main Company account to do a checkout session to setup a 'future usage' & off-session payment method? Then allow individual users under that platform account to 'checkout' as that user? I'm not sure here.
sterile brambleBOT
coarse quail
Or is there a native way in Stripe to have multiple people share the same payment methods/be grouped into a 'company' or some kind?
marble oar
That's not really how it works. Generally speaking, a connected account is something your platform sends money to, and a Customer is something your account/platform collects money from. If you have an entity where you want to do both, the general approach is to have them represented by both a connected account and a Customer, but those would be separate objects in Stripe.
coarse quail
Understood. For purposes of this question the Connected account piece is potentially not relevant. Just pretend we are trying to share a single payment method across two different 'customers' at a Checkout page (different pages, not real-time!). My platform will handle the company/employee relationship piece of it--but trying to understand if we can avoid a situation where two(+) people (stripe 'customers') have to go through the same bank account authorization process when, in reality, they are buying/paying as the same legal entity.
marble oar
In that case you would probably want a single Customer object that represents that one legal entity.
coarse quail
And how do I associate different individuals with that one Customer object? Or is it as simple as just specifying the same Stripe customer-id for each purchase/Checkout session, no matter what individual is placing it? There are no email-specific things (or SMS verifications or similar) that a "Customer" object may need to take later down the road that using a sahred object across multiple individuals would impact?
marble oar
There's no functional way in Stripe to have multiple individual people associated with a single Customer. That's something you would have to keep track of on your end. Metadata might be of help: https://docs.stripe.com/api/metadata
You would need to decide on a single email for the Customer, like a shared email that all the individual would have access to.
Or you would have to handle emails on your end and turn ours off.
coarse quail
Ok, thanks. Is there a doc on the specific emails sent for checkout/payments that I might have to mirror?
coarse quail
Excellent. Thank you for all the help!