#poacher2k
1 messages ยท Page 1 of 1 (latest)
Hi there
heyo! ๐
So you are looking to rely on the initial Price that is added to determine what other Prices should also be added to the Subscription?
Is that correct?
Basically, we want to make sure we have a single source of truth for what a Plan includes, as well as ensuring that we can easily grandfather clients when we update what a Plan costs, or how many of X or Y should be included
Close but not quite - the other prices we look up using the lookup key for each product
When you are using the term Plan here are you referring to a Stripe Plan object? Or just using that generally?
(generally ๐ )
let's say "Basic" at this point in time includes 10 API Calls or whatever, we want to generate usage records when the amount of API Calls exceed 10
but tomorrow we might want "Basic" to include 15
we could create a hard-coded object in our backend that maps the various price id's to included usage, but then we'd need to deploy new code before transferring the lookup key of the new plan price
sorry for the noobing here. perhaps it's better to have a table in our database with this information, using the price id as a key