The Cleverbridge platform supports usage-based billing and ensures that all usage-based bills are synced with client-hosted applications that calculate usage. The components of the Cleverbridge platform that support usage-based billing, along with the usage-based-billing use cases that they support, are identified below. The requirements for your system are also specified.
Your System
Track a customer
An individual or business purchasing your product or service by placing an order through Cleverbridge. The customer is the end user of this product, as they are not allowed to resell the purchased products or services.
A customer is unique per client. If a customer purchases products or services from two different clients, there are 2 separate records of said customer.'s usage. Your system must track usage, determine the billable amount of this usage, and pass the billable quantity to cleverbridge, where the quantity will be billed using the per-unit price for the subscription item A subscription item is component of a subscription with its own set of attributes including price, description and feature set..
Subscription API
Note
By definition, usage-based billing requires that the customer be billed for usage after the billing interval.For more information on how to bill customers for usage with our Subscription API, see the following Use Cases for Billing Subscription Customers for Usage:
- Bill customer for usage,
- Bill a customer for excess usage (overage),
- Apply a negotiated or custom price to all future usage by a customer (bill usage at a custom price), or
- Use a tiered or volume pricing approach to bill a customer for usage (bill usage with quantity-based pricing).
Process Cart API
Note
If the ProcessCart API is used, then the usage is not tied to the subscription, and a one-time purchase An order made by a customer and the records associated with it. is created.