Our Product Team has made some exciting new changes to Chargify's User Interface (UI) after collecting some feedback from our customer base! Although these changes are minor, the enhancements we made to the Product Catalog layout will look different than what you have been used to.
We have now added pagination to the top of the Product Catalog to make it easier for you to navigate your product catalog across multiple pages, allowing you to scroll to the right page in your catalog. We have also added a 'Back' link to the Product, Component, and Coupon Details views such that after working with a particular product item, you are taken back to the same page in the catalog.
This will make it easier to make several edits to products, components, and coupons in the same product family. For more information on managing products in Chargify, see our documentation here>
Having the continuity with your historical data for your customers in a single system makes your life easier by providing "the big picture" on your subscriber base. Because of this, we are excited to announce that we have hit another milestone on our product roadmap to import your historical data into Chargify.
You now have the ability to import cancelled subscriptions. Importing cancelled subscriptions can be done either through the UI with a CSV or via the API. Once imported, you will be able to see all of the historic cancelled subscriptions on the Subscriptions Page (Billing > Subscriptions).
For more information on the minimum requirements for creating cancelled subscriptions, see our documentation here>
For our API documentation on importing cancelled subscription, please click here>
Event-driven architectures are crucial for enabling real-time, personalized product experiences and we believe they are the future of modern B2B SaaS applications. For organizations that are already events-based, we’ve introduced a simpler method to send data to Chargify via our Kafka Inbound Cluster. From there, you can use this data to build complex, value-based pricing models which charge your customers for exactly what they use—linking the value you provide to the invoice they receive.
For more information on streaming data from Kafka-based event pipelines to Chargify for Events-Based Billing, see our documentation here>
Charging based on value is something we believe strongly in and are excited to announce that you can get even more granular with how you price and bill based on events. Previously, it was possible to bill on events and then vary the price based on 2 additional pieces of data (or attributes). This has now been updated to 4.
For example, if you were billing based on messages sent through your platform, you could track "origin", "destination", "message type", and "data size" in addition to configuring different rates for every permutation of those attributes.
Try Events-Based Billing today and see for yourself the sophisticated granularity you can achieve with it. For more information on Events-Based Billing, see our documentation here>
We are excited to continually provide you new API endpoints that surface our core functionality outside of our UI, allowing for full flexibility of how you bill your customers. Our latest API endpoint is creating ad-hoc invoices for one-off services or products, separate from your recurring charges. With these one-off invoices you can directly feed in everything that will be charged including the price, description and item being sold and you can set these invoices to be paid either by remittance or automatic payment collections. They can have multiple line items, a custom memo, and all other basic attributes you get when you create the one-time invoice in the UI.
For more information on how to create a one-off invoice via the API, see our documentation here>
As customers upgrade or change their subscriptions with you, providing a preview of their updated charges is a great way to mitigate surprises and keep customers happy! Chargify's latest API enhancement enables you to do just that. The 'Preview Migration' API call allows you to pull the prorated new charge amount based on a specified date (within the current billing period). Simply pass in the future date and get the corresponding prorated adjustment, charge, payment and credit applied values.
For more information on product migrations via the API, see our API documentation here>
