Usage-based pricing has become the default model for AI products, API services, and infrastructure tools, but implementing it with Stripe Billing v1 was unnecessarily complex. You needed custom metering infrastructure, manual invoice calculations, and often a separate revenue recognition tool. Billing v2 handles all of this natively.
The metering system accepts usage events in real time and aggregates them according to your pricing model - per-unit, tiered, volume-based, or custom formulas. Invoices generate automatically at billing cycle boundaries or when usage hits custom thresholds. The revenue recognition engine applies ASC 606 rules automatically, which matters once you reach the stage where investors or auditors care about your accounting practices.
The incremental migration path is the smart design decision here. You can keep existing subscriptions on v1 while building new pricing plans on v2. There is no big-bang migration required. For founders considering usage-based pricing, Billing v2 removes the technical barrier that previously made flat-rate subscriptions the path of least resistance. The main gap is that Billing v2 does not yet support prepaid credit models, which are popular with AI products - Stripe says this is coming in Q3.
If you have been avoiding usage-based pricing because of implementation complexity, Stripe Billing v2 makes it as simple as flat-rate subscriptions.
