#pascal_subscription-meter
tardy flameBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! We typically respond in a few minutes, but in some cases we might need a bit more time (e.g., server's busy, you've got a complex question, etc.).
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1255925982859235421
📝 Have more to share? Add details, code, screenshots, videos, etc. below.
idle trout
pascal_subscription-meter
@celest lotus If you only have one Product and report usage of 3 for example then each Subscription that has that Product would charge for the usage of 3. Since you mentioned the Customer will have separate Subscriptions for each mobile app, that wouldn't work.
So if you want to keep that approach you will need to have a separate Product and Meter for each mobile app I think
celest lotus
@idle trout thank you for your answer! Yes I need one bill (so one subscription) per app. Reading the documentation, I noticed that a Meter Event can only be associated to one Meter, but i was wondering if there was a way (using the same event_name for all apps) to further filter the events used by stripe to compute the amount to charge per app. I found https://docs.stripe.com/billing/subscriptions/usage-based/recording-usage#event-filtering but it does not seem available
idle trout
No there is nothing similar to what you are thinking of. Right now you need a separate Product and Meter for each app. In the future we want to allow you to have a MeterEvent for a specific Subscription id instead of just the Customer id
celest lotus
This is what I thought, I have to go for one product per app, I will try! Can I get back here if I have other questions regarding the usage reporting with Meter events?
idle trout
sure! We archive threads quickly here but you can ask a new question with the buttons in #help if this thread is closed already!
celest lotus
One last thing, I saw articles using usage records that seem to work for my case, but it looks like Stripe has deprecated this? https://docs.stripe.com/billing/subscriptions/usage-based-legacy#report-usage
idle trout
Yeah UsageRecord supported this just fine. The product team rebuild the whole API to be a lot more advanced and flexible but they don't support all use-cases yet. If you build on top of UsageRecord you'll likely have to migrate so I'd recommend avoiding it 😦