kasparkallas

[blissful hill]

Hi

I'm thinking of creating a "fake" Customer or Product for this use-case and use the metadata field for my integration data.
Why you want to create fake data? you don't have Customers and Product in your integration ? and yes you can use metadata to set your own fields/values

[viscid pollen]

It would be a Customer or a Product with a specific fixed key that I load from my back-end integration. There would be many installations of the back-end integration and all of them would load the same fixed key entity from Stripe and store a tiny bit of arbitrary metadata there.

There would be only a single "fake" entity. All of the rest would be real.

I guess I don't have much of a question, just doing a sanity check whether it's viable and looking for some stylistic preference. 😛

I guess it will probably come down to for which I can set the fixed key that will make it easy for me to load the entity (or create it if it doesn't exist yet) without loading other entities in a list query at the same time.

Will go with a Customer. Thanks, have a nice day!