Chargebee Release Notes

Previously, for our One-time purchase API, there was a limit of 70 characters for and 20 for as the was appended to the product[name]product[type]product[id]product[name]product[id]product[name] 46 characters.

When the next billing date was changed for a subscription with metered items, the subscription renewal was found to fail. This is now fixed!

Previously, Play Store one-time purchases required acknowledgment within three days to prevent automatic refunds and purchase revocation. Acknowledgment was SDK-based, potentially causing issues for non-SDK users. We've improved the system to automatically acknowledge one-time purchases through Google's APIs, if not already acknowledged.

In previous versions, when Google's APIs returned a 410 error, it was not handled appropriately, causing a 500 error to be thrown instead. In this release, we have resolved the issue by ensuring that when a 410 error is received, the error is now properly represented with the correct error details, rather than throwing it as a 500 error. This ensures more accurate error handling in our application.

We are pleased to announce an enhancement to the MRR History Builder. In the current version, the tool may generate inaccurate subscription histories when line items end at non-standard intervals, such as random hours that do not align with the typical 24-hour cycle.

In this release, we have addressed this issue. The MRR History Builder will now take into account those additional hours in line items, ensuring the accurate generation of subscription histories. This improvement will contribute to better data accuracy and reporting for your subscription-based services.

With this resolution, customers can expect credit note refund transactions to be correctly synchronized with Xero, ensuring accurate financial records and accounting integrity.

The Tax Registration Number Field was not displayed in the customer creation page even though the option to 'Collect Tax Registration Number from customers for countries not configured for tax'(under Configure Taxes) was enabled, until atleast any one country tax is configured. This is now fixed!

Pricing Tables now support volume, tiered, and stairstep pricing models, giving you greater flexibility to showcase your pricing strategies. Plus, with the new 'quantity slider' feature, your visitors can easily select their desired quantity right from the pricing page. This selection is automatically transferred to Chargebee Checkout, simplifying the purchase journey.

You can now modify or remove a scheduled cancellation directly from Salesforce.

function is introduced in all our in-app purchase SDKs to validate the receipts for one-time purchases.

You can now use your custom domain for Chargebee Checkout directly with Pricing Tables—no extra setup required! Navigate to Settings → Revalidate Domain to pull in your custom domain settings instantly.

In this release, we have resolved the initial sync issue in our HubSpot Q2C (Quote to Cash) Integration. This update ensures a smoother and more reliable experience for users who have been facing challenges during the initial synchronization process.

The Subscription Index Page lacked visibility of the customer details. We have added the 'Customer ID' column to the Subscription Index Page, enhancing data accessibility for users.

You can now configure to collect reverse charges from customers in specific countries. When a subscription is created for a customer from a different country than your organization address for which you have configured to collect reverse charge, tax is not applied on the invoice, and the Reverse Charge note that you add gets displayed.

We found the Card Expiring alert in Leap UI less noticeable compared to the Classic UI, affecting proactive customer support. To fix this issue, we revamped the alert in Leap UI, making it more noticeable on both customer details and subscription details pages.

The warning message in Shipstation consistently displayed 51 failed records, despite the actual number being more. We have adjusted the fetching limit from the third-party entity mapping table to reflect the accurate count of failed records.