Usage-Based and Metered Billing

This package adds usage-based billing to a SaaS, API, telecom or cloud service that charges for what customers consume, such as API calls, gigabytes stored, call minutes or active seats: usage comes in, rating rules turn it into money, and you see an invoice preview before anyone is charged. It works with a custom billing system or an existing Laravel app, and with any gateway, which is the difference from the Laravel Stripe Billing package, where metered usage is reported to Stripe and Stripe does the pricing.

From raw events to an invoice line

Usage arrives as a CSV upload or through an API endpoint your app calls. Each record carries an event ID, so a file sent twice or a retried request is counted once. At period close, the rating step groups usage per customer and metric, applies the price rules and writes invoice lines such as "48,200 API calls above the included 25,000".

• Starter rates one metric at a flat price per unit.
• Business adds tiered and volume pricing, included allowances with overage, and contract prices for individual customers.
• Premium adds prepaid credits, minimum monthly commitments and re-rating of a closed period when a price was set wrong.

Checking the numbers before customers do

The preview shows each customer's draft invoice with the usage behind every line, so finance can spot a spike before it becomes a dispute. Customers see their running usage in the portal, and on Business they get an email when they pass thresholds you set, which is kinder than a surprise bill.

Where the limits are

The quality of the bill depends on the quality of the usage data. I build the import, validation and rating; producing accurate usage in your app or network stays with your team, and I flag gaps I find in the samples you send.