#movewithpulse-customers
meager prism
peak veldt
it's basically giving authorization to pay for the member (who is a child) using the parents card
the way we've built things, we've been creating a stripe customer using the dependents name
sorry, working my thoughts out here haha, so biggest potential issues I see with moving this direction:
- Inside Stripe, if we make the parent the customer, it's hard to find transactions related to a dependent. We could use metadata to associate payments with member, but is that searchable?
- Is there any security issues with exposing a parents card to a child? Basically, if we start to expose a card based on a relationship, it opens up the potential for cards to get wrongfully exposed to people who shouldn't have access...if that makes sense. I realize that would be on us with our SaaS to ensure the right person is getting access to the right card, but it was simpler when we made the customer in Stripe == the member in our system
if we went this new route, it would be customer in Stripe == parent, who makes their card accessible to their dependents to pay for their memberships
mossy edge
hey there just catching up here as @meager prism needs to step away
peak veldt
okay, cool, I appreciate it!
mossy edge
you should be careful to work with your legal team here regarding storing any information about children -- some jurisdictions have special laws in place about this
peak veldt
ah yeah, that part we have covered
mossy edge
but generally speaking, the customer and the billing details dont need to be for the same person
peak veldt
okay, that makes sense
mossy edge
so the "customer" is the person getting the product/service, say, while the payment method billing details correspond to the owner of the card/account/whatever is used to pay
peak veldt
okay -- and with how Stripe metadata is set up. Let's say "Chris" is the guardian, and "Lucas" is child 1 and "Stephen" is child 2, how would we find transactions for Lucas only.
mossy edge
that depends on your system, its up to you
you might set up separate customer for lucas and stephen, and both have payment details owned by chris
or you set up chris as the customer and chris pays for two subscriptions, which have metadata indicating its for lucas vs stephen
(id argue the parent is the customer, but this is your decision to make)
peak veldt
okay, and is metadata searchable in Stripe's interface?
mossy edge
it is now 😄
peak veldt
awesome!
mossy edge
example metadata search: https://stripe.com/docs/search-api#charges-metadata-search
mossy edge
quite welcome!