- Quantity
- Unit Price
- Total Charges
For more information on our Events-Based Billing, see our documentation here>
For more information on our Events-Based Billing, see our documentation here>
As Chargify continues to evolve the way you can manage subscription groups, new API endpoints have been added that give you the option to easily navigate and view:
Cancellation and reactivation of the entire group can happen through a single API call. In addition, groups can now have their own service credits and prepayments, apart from individual member subscriptions.
For more information on our API endpoints supporting subscription groups, see our documentation here >
As the Chargify product continues to evolve, additional data has also been added to our API Endpoints to ensure all data is accessible when and how you need. Several recent updates to our API include:
Components API
Products API
Coupons API
Events API
Offers API
For more information on our API, please see our documentation here >
In a global economy it is more important than ever to price and sell your products and services in ways your customers want to buy. To support you in this effort, we have introduced enhanced multi-currency support for our Events-Based Billing. This means you can now define your multi-attribute pricing in any currency. An example of this for a Marketing SMS Company is charging $0.10 for a US based customer sending messages to the UK and £0.046 for a UK based company sending the same messages.
To learn more about Multi-Currency support, see our documentation >
It is now possible to hide service dates from line item presentment on Chargify invoices. This update does not charge the billing functionality in any way, but simply impacts what is displayed on your customers invoice. With this update, invoices become easier to understand if you are running an offset billing cycle for your customer base.
Also, It is now possible to label your API keys directly in the Chargify UI allowing admins to know exactly what that API key is being used for.
For more information on invoice dates, see our service date documentation here and for additional information on API key labeling, see our API documentation here.
MRR data is now available via the Chargify API. This rich MRR data, driven by subscription creation, changes, or cancellations, is already surfaced in Chargify’s out-of-the-box MRR report. With the MRR API endpoints, you can now pull this data directly out of Chargify for inclusion in external reporting tools or integrations into other back office systems.
Learn more in our documentation >
It is now easier to know when your customers are about to churn with the introduction of the Pending Cancellation Webhook within our API. This additional webhook will trigger when a customers’ subscription is updated to cancel in the future (ie. at the end of the period). This update will allow you a better understanding of your upcoming customer cancellations. With this you are now able to:
For more information on how to structure your Pending Cancellation Webhook, see our documentation >
It is now possible to bill for consumption of your service at different rates based on the attributes in your events data. Multi-Attribute Rating allows you to dynamically create segments from your events and define targeted pricing for each segment, leading to increased price flexibility and invoice clarity while preventing catalog bloat.
Consumption-based services face unique pricing challenges around rating access to their service. Both the cost to the provider and the value to the consumer vary depending on many factors. Powerful compute servers cost more than standard ones. Text messages and phone calls to France cost more than ones to the United States. Historically, providers have needed to track these factors on their side and map them to a bloated pricing catalog on the billing system side. But now, with Chargify's Multi-Attribute Rating, providers simply tag their event data with these factors and define multiple rates — as many as needed — for their combinations of attributes. Chargify does the rest - we select the appropriate rate for every event and produce an invoice that is concise, accurate, and easy to read.
Imagine a ‘Cloud Server’ company that offers multiple sizes of servers to their customers. Each server is billed based on the hourly consumption, with higher rates for the larger servers. Previously, to charge for each size server at its own rate, Cloud Serve would need to create multiple components (one for each size) and report usage separately for each size. With Multi-Attribute Rating, Cloud Serve creates a single Events-Based Component, based on the ‘Server Hours’ data stream and metric, and varies the price based on the ‘Server Size’ attribute. Taking it a step further, Cloud Serve can even vary the price based on another attribute, such as location, time of day used, day of week used, etc. For example, a server in the EU may cost more than a server of the same size in the US. This is configured by simply adding a new rate for the attribute combination and not by creating a component for every size and location pair.
With Multi-Attribute Rating, your flexibility of rating based on the true value your product provides is even easier. You can now provide very specific pricing, varying on attributes, while maintaining a consistent and easy-to-manage product catalog.
With this very powerful pricing model, it is equally as important to ensure your customers understand their invoices. When Multi-Attribute Based charges are included on an invoice, the invoice template has been updated to clearly outline how your customers are being charged and the value you are providing. A new “Usage Details” section will appear at the bottom of the invoice, clearly detailing both the amount consumed and the unique price for each applied rate. Your customers will clearly see what they were charged and why, even in complex billing scenarios.
To learn how to start using Multi-Attribute based rating, please contact Chargify Support your your Customer Success Manager.
Learn more in our documentation >