Skip to content

Understanding usage-based billing

Consumption-based billing models (usage-based billing or pay-as-you-go) allow you to bill your customers for services based on actual consumption (e.g. API calls, data volume used, emails sent or server time used) rather than at a flat rate.

Due to the high complexity and the individual requirements for the data connection, a complete configuration of this model is currently not possible in the tebio business portal.

Instead, usage-based billing is always implemented as part of a joint integration project with the tebio team.

A consumption-based model makes sense when:

  • Your service is measured in fine-grained metrics (e.g. megabytes, minutes or views).
  • You want to offer customers a low starting price (or a free base fee) and monetize the actual value through usage.
  • A customer’s usage is subject to strong fluctuations and flat rate models would be unprofitable or unattractive for the customer.
  • System-side measurement: You must be able to reliably record consumption in your own IT systems (metering).
  • API connection: Your system must transmit the aggregated or raw consumption data to the tebio platform at regular intervals via the API.
  • Project setup: You have coordinated the exact use case in advance with tebio support or your project manager.

Since the configuration is not entirely done in the portal, the process for introducing usage-based billing looks like this:

Together with tebio, you define the basic parameters as part of the integration project:

  • Metrics: What exactly is being measured (e.g. SMS sending)?
  • Billing model: Are there free quotas? Are there tiered prices or a fixed price per unit (volume pricing)?
  • Cycle: How and when will the collected consumption data be billed?

The tebio team sets up the complex, consumption-based products, options and price lists as part of the project so that they are ready for your system.

Your development team connects the tebio consumption API. Your system reports regularly, for example hourly or daily, the recorded units of the respective subscriptions.

On the deadline of the billing cycle, tebio automatically records the transmitted consumption, applies the defined pricing models and generates the invoices for your customers.

  • Missing or delayed data submission: The system can only bill for what is reported. If your interface fails and consumption is not transmitted on time, it may no longer be included in the current billing cycle.
  • Uniform metrics: Make sure that the unit measured in your system matches the unit defined in the tebio price list (e.g. “Gigabyte” instead of “Megabyte”) to avoid incorrect calculations.

tebio provides specialized endpoints for the transmission of consumption. The detailed documentation and integration workflow will be provided to you as part of the joint project.

Typical API operations in this context include:

  • Authenticate and assign consumption to a unique subscription ID.
  • Transmission of batches, i.e. collected consumption data, or individual events.