Metered Billing
Metered billing (also called usage-based billing) charges customers based on what they actually consume during a billing period. The charge is calculated and billed in arrears at the end of each period. This works well for API products, cloud services, or anything where consumption varies significantly between customers.Plan configuration
Use themetered pricing rule:
unit_price is in minor currency units (2 cents per unit in the example above).
Creating a metered subscription
amount is 0, no charge is collected upfront.
Reporting usage
Report consumption with theRecordUsage action. Call it at the end of a job, request batch, or any discrete unit of work:
idempotencyKey parameter ensures that if your job is retried, the same usage is not counted twice.
Reading current period usage
Billing
At the end of the billing period, Subscribd multiplies total reported units by theunit_price to produce the invoice amount. The invoice is charged to the customer’s payment method and a new usage period begins.
For gateways with native metered billing support (Stripe), usage records are synced to the gateway and billing is handled by the provider. For other gateways, Subscribd calculates the amount locally and issues the invoice directly.
Combining metered usage with a base fee
Add a non-zeroamount to charge a fixed monthly base fee on top of the usage charge:
Next steps
- Tiered Billing — Volume discount thresholds
- Plans — Full plan configuration reference