Release Notes
Updates, changes, and improvements at Chargebee
Release Notes
Updates, changes, and improvements at Chargebee
With the new setVisitor() function in Chargebee Pricing Tables, you can now pass essential checkout fields like First Name, Last Name, and Email directly into the checkout flow, reducing friction at the point of purchase.
Pricing tables in Chargebee Billing now support plans with per-unit pricing, alongside the existing flat-fee plans. For ease of checkout, quantities default to 1 but they can be adjusted by end users during checkout.
Now, creating a pricing table in Chargebee Billing is easier than ever, even if you don't have API keys handy. You can generate a demo site to explore the setup and configuration of your pricing tables before going live. To help distinguish between your test, live, and demo environments, Chargebee now shows indicators based on your site domain.
Customize your pricing tables further by adjusting the orientation of plan frequencies, adding suffixes to prices, and setting custom price labels like "Contact Us" for enterprise plans or "FREE" for free plans.
You can now set a default height for the iframe in pricify.js. By initializing the iframe with a height close to the final display, you ensure a consistent viewing experience that keeps your page layout steady.
In this update, we are implementing a change to the ID format for Charge or non-recurring Addon records for the one-time purchase that are synced to Chargebee. The one-time purchase type is removed from the charge ID to make sure that you can use all the 50 characters available for creating a charge name/charge ID. To identify the purchase type of one-time purchase, in the Invoice Index page, you can apply the filter on the Invoice Number with the value consumable, non-consumable, or non_renewing.
Now our one-time purchase API supports Google Play Store to sync consumable, non-consumable, and non-renewing product payments in Chargebee. Learn more.
When using the LeapUI for the Events Index Page, we were not able to retrieve records for customers using their customer IDs, names, or emails, even though the same filters worked correctly in the Classic UI. This issue has been resolved, and records can now be retrieved successfully using the mentioned identifiers.
The input parameter name,Type for the event notification API has been changed to event_name to prevent conflicts in SDKs..
We are excited to introduce a new feature that addresses the issue of duplicate records in one of our reports. With this release, you will no longer encounter duplicate entries in the following report, ensuring cleaner and more accurate data analysis.
With this release, you can seamlessly utilize your custom fields when building reports without encountering any errors.
We are pleased to announce that our Flutter SDK now includes a new method called Restore Purchases. The restorePurchases() method helps to recover your app user's previous purchases without making them pay again. Sometimes, your app user may want to restore their previous purchases after switching to a new device or reinstalling your app. You can use the restorePurchases() method to allow your app user to easily restore their previous purchases. Learn more.
In this update, we have made significant improvements to the subscription trial management settings by moving it from the Configure Chargebee section to the Billing LogIQ section in Leap UI. Additionally, we have introduced a new environment property that enables the system to throw an error for unhandled site settings, ensuring better error handling and increased stability.
Fixed a bug due to which the business entity records were also transferred during organization address transfer. With the latest update, the site transfer process will no longer fetch any business entity information, ensuring accurate and streamlined data migration. This resolves the issue encountered during transfer config validation when multiple business entities with an organization address were present on a site.
We have identified and made the following fixes with this release:
Exclusion of Backdated Payments:Invoices settled with backdated payments will no longer appear in the historical aging report.
A/R aging reports were. fixed to pick up the period end date.
The report names were fixed in the alerts.
We have identified an issue in Netsuite where users encounter an ambiguous error message. This error occurs when required subsidiary information is missing or not properly provided. To address this issue, we have implemented a fix that enhances error handling and provides clearer instructions for resolving the error.
With this release, Chargebee will automate the Chargeback management flow for Mollie. This will include listening to dispute-related webhooks from Mollie, creating a credit note for the invoice based on the Chargeback settings, canceling or pausing a subscription when a Chargeback is initiated, and more. This will save the merchant from managing the flow manually and also prevent errors and loopholes in the process.
The following issues were fixed with this release:
While creating subscriptions with contract term, if the contract term billing cycle on renewal is left blank, the error message was not not getting displayed as expected on the Leap UI, and the subscriptions were created.
When the subscriptions are created, for active subscriptions, the contract term end date and billing cycles are populating correctly. But for Trial subscriptions, it was found to take an additional billing cycle and the end date was also populated wrongly.
Inability to update the subscription plan via API.
Inability to add a fixed manual discount via Chargebee interface due to an unexpected error.
Inability to reactivate a subscription for a customer record, due to an error message.
An error message "discounts[item_price_id][0] cannot be blank" was displayed while attempting to update a subscription from a quote.
When future subscriptions are created with unbilled charges, the contract value was displayed incorrectly as per discount.
Previously, recurring items and details such as Plans add-ons and coupons that were visible on hovering in the Classic UI subscription index page were missing on index pages in Leap UI. With this update on Leap UI, the Index page > Subscription Info > +1 option is now displaying all necessary subscription information on hovering such as Plans, Addons, Coupons, and more.
We have updated the Leap UI to improve user experience by placing the card expired notification next to the card number in the Customer Index Page > Payment method column. Also, if you have more than one card added as your payment method you can use the +1 card option to see all your card details and status. This change will allow users to quickly identify if their card has expired and avoid any inconvenience when trying to make a payment.
With this release, we have added a new column called Subscription Cancellation Date to the Customer and Invoice views. This column provides visibility of canceled subscriptions to the merchants. It is available under both Column Chooser and Filters.
With this release, merchants can now apply parent-level grouping and can have a single view for outstanding. If a merchant groups on the Parent Name in the Invoice view, they will be able to see the combined outstanding-related data for a customer with and without hierarchy and can drill down to individual child customers.
With this release, while setting up their custom SMTP Email Engine, merchants can test their connection and also send a test email to check if the configuration is successful. To perform these operations, a button - Check Connection and Test Email has been added under Settings > Configuration > Email Setup.
The following issues were fixed with this release:
Inability to remove coupon for a subscription from the Edit Subscription page due to a bug.
For a subscription with contract term, when the subscription is edited to update the "on contract term end" value to Contract and Subscription end, the update was not getting captured.
The alert message or info popup was found not to load for subscriptions with contracts.
The following issues were fixed with this release:
Inability to reset invoice number to a different month due to a User Interface(UI) bug.
The Void Credit Note option was found to not work the second time.
VAT was found to be added twice for an invoice of a subscription that got reactivated.
The 'Use Default' site setting was not getting selected by default while changing the country from the Update billing address page.
We are pleased to announce that our Android SDK now includes a new method called Restore Purchases. The restorePurchases() method helps to recover your app user's previous purchases without making them pay again. Sometimes, your app user may want to restore their previous purchases after switching to a new device or reinstalling your app. You can use the restorePurchases() method to allow your app user to easily restore their previous purchases. Learn more.
A new major version of React Native SDK is released that supports in-app purchases with more robust error handling. Learn more.
We have released an update to our Netsuite integration with Multi-Entity support to meet the evolving needs of our customers. We have enhanced the integration to enable separate account mapping for each site, which can improve the accuracy and efficiency of financial operations. With this update, you can now map each site to a unique account in Netsuite, allowing you to easily track and manage financial data for each entity or business unit.
We are pleased to announce the release of Time Machine, which now includes enhanced compatibility with PC 2.0. In the initial launch of Time Machine, this valuable capability was not supported in PC 2.0 due to internal challenges. However, we have addressed these issues and incorporated all the test scenarios from PC 1.0, ensuring a seamless transition for our users. By reusing the same design and converting the required test data to the PC 2.0 format, this update immediately adds value to our customers and greatly improves adoption.
We are pleased to announce the enhancements done to our transfer configuration feature:
We have introduced an asynchronous job for the Validation step. By implementing this change, the framework now has the capability to perform the validation step for an extended duration, allowing for more comprehensive validation processes. Additionally, the validation state is now stored, enabling users to conveniently check the status at their convenience in an asynchronous manner. This improvement greatly enhances the user experience and overall efficiency of the framework.
We have addressed an issue in the existing Framework where server quits would lead to stale data and necessitate the use of DML for customers to initiate new transfers in the application. This update implements a solution to handle server quits effectively within the framework, ensuring data integrity and streamlining the transfer process for improved customer experience.
We have addressed the issue of data and settings deletion prior to validation. During transferring configuration, you can choose to Retain or Delete the existing data if the destination is a TEST site. However, if the destination is a LIVE site, you cannot Delete the existing data.
We have made a small fix to our comment section of the details page(subscriptions, customers, quotes, and orders) to ensure consistency in displaying the time. Previously, when an attachment was added along with text in a comment, some timestamps appeared out of line with other timestamps. With this update, the timestamp will now appear in the same line regardless of whether an attachment is present or not. This change will help users better track and organize their discussions within our platform.