aught66 | Stripe Developers | Page 1

celest bisonBOT Sep 21, 2022, 4:20 AM

#

marsh solar Sep 21, 2022, 4:22 AM

#

I don't quite understand your question

#

What are the lookup and synthetic keys for and how are they related to products or prices?

sour plank Sep 21, 2022, 4:43 AM

#

I am billing for consumed resources, like text messages. To submit the usage from my platform I used the lookup_key to find the correct subscription_item/price_item.

It works great, up until I change prices and launch new prices. To maintain billing for previous customers, I need to maintain a lookup_key on the archived price to keep billing older customers whatever rates they have.

marsh solar Sep 21, 2022, 4:52 AM

#

What is this lookup_key? Is it an ID you self defined or Stripe object ID?

#

What's the relationship between lookup_key and the prices?

sour plank Sep 21, 2022, 4:55 AM

#

https://stripe.com/docs/api/prices/object?lang=ruby#price_object-lookup_key
https://stripe.com/docs/products-prices/manage-prices#lookup-keys

marsh solar Sep 21, 2022, 5:09 AM

#

I'm going to step away. My colleague @terse kiln will be taking over this thread

terse kiln Sep 21, 2022, 5:11 AM

#

👋 taking over

sour plank Sep 21, 2022, 5:21 AM

#

Think I found a solution. It involve using one PriceItem as a "template" and creating an "In Use" price with a lookup_key composed of the original key + original Price Item ID.

This allows archiving and replacing the published prices (used in Pricing Tables) without interrupting processing of usages on establish customer accounts that rely on looking up the subscription item (price) using the lookup key.

#aught66