joshglazebrook

[twilit tinsel]

Hi 👋 for the monthly scenario, I would recommend taking a look through our usage-based billing as we have prebuilt functionality for aggregating usage and charging at the end of a billing period for that:
https://stripe.com/docs/billing/subscriptions/usage-based

That being said, the approach you're describing for the monthly scenario also seems feasible and should work.

The yearly subscription with monthly usage is going to be more challenging though, as our Subscriptions don't support multiple billing frequencies within them.

For the yearly scenario, your approach sounds viable. The only alternative that is readily coming to mind is to generate two Subscriptions for the customer, one for the yearly price and one for the monthly usage, but if you're leveraging prebuilt UIs like the Customer Portal that could appear confusing to your customers.