#Kristoffer-multiple-customers

1 messages · Page 1 of 1 (latest)

burnt ridge
#

Hi there!

prime timber
#

Hey 🙂

burnt ridge
#

The best way to handle linking multiple customers together is to set metadata on the Customer objects

#

This allows you to use an arbitrary identifier that relates the Customers together.

prime timber
#

Like a customer ID from our CRM or some other system yes?

burnt ridge
#

Exactly

prime timber
#

Do you have any experience with linking companies within conglomerates? I ask because there may be different ways of linking them. In some cases you'll want to link because multiple customer objects are related to the same company, while other times it may be to link all daughter companies with their mother companies.

burnt ridge
#

I don't have experience with this personally (I'm a Stripe Engineer), but yeah there are a variety of ways you might want to tie things together here and metadata should give you the flexibility to do so.

prime timber
#

To what extent can you or should you use metadata on subscription objects and payments in Stripe to decide what a specific user can see/access when setting up a Stripe customer portal?

burnt ridge
#

That is a pretty general question so it is pretty hard to say.

#

Most folks track most of their customer data in their own Database.

#

And then you can associate the Customer object in Stripe to that data via the metadata UUID

#

It is also common to store things like an order ID in metadata

#

But it is really up to you here.

prime timber
#

Okey, so it's common to generate an order ID in another system and add it as metadata on the subscription and/or payment. That's useful.

burnt ridge
#

Yep for sure

prime timber
#

Do you have any examples, presentations or videos that go through common usecases and what other common metadata is being used?

burnt ridge
#

Hrmm no not that I know of. You could try posting in the #841573134531821615 channel and asking the community there how folks use metadata. This channel is mostly for helping to troubleshoot specific integration issues.

#

Overall metadata was built to be really flexible, so you can use it for any data that you feel would be beneficial to store in Stripe and associate with a specific Stripe object.