felix-schmid_billing-meters

[dusk sky]

👋 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/1250064622023872524

📝 Have more to share? Add details, code, screenshots, videos, etc. below.

[edgy comet]

I’m building a B2B SaaS application that allows users to manage their hotels. Users are billed a fee per hotel and a usage-based price depending on the number of guests during the current usage period.

Users can group their hotels into multiple “billing accounts” to avoid entering the same card or billing details multiple times. Each billing account represents a Stripe Customer. For accounting reasons, I need to create separate subscriptions within each customer so that every hotel receives its own invoice.

For usage-based billing, I would like to use the new meters to track guest numbers, but I need to associate this tracking with the subscription rather than the customer. Every hotel should receive its own invoice detailing both the fee and the usage for that specific hotel, while the payment methods should be derived from the billing account.

[bold linden]

hi there!

If a Customer has 2 separate Subscriptions each with the same Price associated with the same Meter, then the usage will be "double counted" since there's no way to report usage for a specific Subscription/SubscriptionItem.

the legacy usage based billing doesn't have this limitation

[edgy comet]

So you would recommend me using the old legacy usage based billing even though it's a new project and therefore I usually not want to integrate legacy APIs? Are there any plans that the old usage based billing get discontinued anytime soon?

[bold linden]

for your specific use case, yes I think the legacy one makes more sense.

Are there any plans that the old usage based billing get discontinued anytime soon?
there are many merchants using this integration, so it will continue working for the foreseeable future

[edgy comet]

Thanks! Do you know if there are any plans in the future that the new metered billing can handle those use-cases as well? Would love to use the new API's but I'm afraid that's a deal-breaker for me

[bold linden]

we are aware of this limitation yes, but I have no idea if/when this will be improved.