June 2025

ACH now supported through Worldpay US eCom

Chargebee now supports ACH (Direct Debit) payments through Worldpay US eCom (formerly Vantiv Litle), allowing you to collect both one-time and recurring bank-based payments from customers in the United States.

Why is this important?

ACH provides a cost-effective alternative to card payments and offers added convenience for customers making bank-based payments. Supporting ACH can help reduce payment processing costs and improve retention for subscription-based billing.

How can you use it?

To start accepting ACH payments, configure Worldpay US eCom as a gateway in your Chargebee site and then set up and enable ACH as a payment method.

Payment Preferences now available in Chargebee

Chargebee introduces Payment Preferences, a centralized feature that lets you configure key payment gateway settings, such as UPI and Net Banking transaction limits, and control customer profile retention during payment method removal.

Why is this important?

These settings are now accessible directly in the Chargebee UI, eliminating the need for Support intervention and giving you full control over gateway behavior.

How can you use it?

Log in to your Chargebee Billing site, go to Settings > Configure Chargebee > Payment Gateways, and open the Payment Preferences section. Each setting has a default value, which you can adjust as needed. Your changes will apply to all instances of that gateway on your site.

Automatically ingest usage data from Amazon S3 (EAP)

You can now ingest usage data directly from your Amazon S3 bucket into Chargebee Billing. This integration automatically fetches and processes usage files from your S3 bucket, removing the need for manual uploads and ensuring Chargebee always uses the latest usage data for billing.

Why is this important?

Automating usage data ingestion from Amazon S3 significantly enhances billing accuracy and operational efficiency for businesses handling large volumes of usage metrics. This is particularly valuable for IoT companies, SaaS providers, API-based platforms where real-time usage tracking ensures customers are billed appropriately. By eliminating manual uploads, this integration minimizes the risk of human error, reduces invoice delays, and ensures billing reflects the most up-to-date usage data.

How can you use it?

To get started, configure your Amazon S3 bucket by navigating to Apps > Amazon S3 Bucket in your Chargebee Billing site. Follow the setup instructions in the user documentation. Once set up, Chargebee will automatically pull and process usage data at defined intervals.

Note: Usage-Based Billing feature and Amazon S3 integration are in Early Access. Submit a request to enable this feature.

Auto-populate your test site data from your pricing page during sign-up

Chargebee now lets you auto-populate your Test site data during sign-up by parsing your business website's pricing page. This AI-powered setup automatically creates a ready-to-explore Test site with product families, plans, addons, price points, features, and branding instantly tailored to reflect your actual offerings. You can also check the history of the auto-populated data changes on your Test sites.

Why is this important?

This saves you the hassle of manual data entry and helps you quickly understand how your pricing model can be implemented in Chargebee. It shortens the time between sign-up and value, giving you a hands-on, contextual demo experience from the start.

How can you use it?

Follow these steps to auto-populate your Test site during sign-up.

Repopulate your test site data based on the pricing page of your business website

You can now repopulate your Chargebee Billing Test site with AI-powered sample data directly from your pricing page any time you need a fresh start. This lets you regenerate product families, plans, addons, price points, features, and brand settings based on your current pricing structure, helping you explore different billing scenarios with data that mirrors your real-world offerings. You can also check the history of the repopulated data events on your Test sites.

Why is this important?

It gives you the flexibility to reset your Test site data and reflect pricing changes or test alternate configurations, without the manual setup. This ensures your Test site stays relevant and useful as your pricing evolves.

How can you use it?

Log in to your Chargebee Billing Test site and follow the steps to refresh your site data using your current or new pricing page. This action will replace your existing Test site data.

New reports for insights into on-demand revenue

Easily track how much revenue your business earns from on-demand purchases. These four focused reports help you monitor performance, understand trends, and identify the top-performing add-ons.

- On-Demand Revenue KPI:The dashboard displays the total on-demand revenue earned in the last 30 and 60 days.

- On-Demand Revenue Trends:View revenue patterns over time, based on the selected time period.

- Addon-Level Breakdown:View how each addon contributes to your on-demand revenue.

- Top 20 Addons:Find out which 20 addons generate the most on-demand revenue.

Why is this important?

These reports offer deeper visibility into how on-demand purchases perform and how usage evolves over time. By segmenting usage and revenue views, you can analyze each area independently, prioritize the right addons, and make smarter data-driven decisions.

How can you use it?

In your Chargebee site, navigate to Usages > Metered Features > Usage Trend> View Details> Revenue Analytics.

Reduce chargebacks with clearer PayPal transaction info

Chargebee now includes product name and ID in PayPal transactions via the Braintree payment gateway, to help reduce chargebacks and disputes.

Why is this important?

By making transaction details clearer in PayPal, you reduce the likelihood of customer confusion and improve their understanding of the purchase, helping to minimize chargebacks and disputes.

How can you use it?

To enable this feature for PayPal via Braintree, contact Chargebee Support.

Accurate billing cycles for backdated subscriptions with Multi-frequency billing

Chargebee Billing now automatically adjusts an addon's billing cycles to account for the backdated period when creating backdated subscriptions in Multi-frequency billing, provided that the addon's total billing cycle duration is greater than or equal to the backdating period.

For example, consider a yearly plan with a monthly addon configured for 12 billing cycles, and you backdate the subscription by 3 months. Chargebee will now automatically reduce the addon's billing cycles by 3, so it will be active for the remaining 9 months of the subscription, keeping the billing aligned with the effective start date.

However, if you attach an addon with only 3 billing cycles and try to backdate the subscription by more than 3 months, the subscription creation will be prevented with an error, since the addon's cycle cannot cover the backdated duration.

Why is this important?

This enhancement ensures that the addon's billing schedule always remains consistent with the subscription's backdated start, by automatically trimming or validating cycles where appropriate. It prevents scenarios where an addon would be billed beyond its intended duration or outside the actual subscription period.

How can you use it?

While creating a backdated subscription in Multi-frequency billing with a fixed billing cycle addon, Chargebee will now automatically adjust the addon's cycle against the backdated duration.

Entity-specific handling now available for gift subscriptions

Gift subscriptions feature in Chargebee Billing is now supported on sites with Multi business enitity configurations. This means you can offer and manage gift subscriptions across multiple business entities within your Chargebee setup, ensuring entity-specific billing, reporting, and operational alignment.

Why is this important?

If you operate in multiple regions or brands with distinct legal entities, this update allows you to enable gift subscriptions feature to create gift plans and manage gift subscriptions across entities. It ensures that gifting logic, invoicing, and subscription fulfillment are correctly handled within the relevant entity's context.

How can you use it?

Log in to your Chargebee Billing site, navigate to Settings > Configure Chargebee > Billing LogIQ > Gift Subscriptions, and enable the Gift Subscriptions feature. Once you create gift plans, all related actions from invoice generation to renewals for the gift plans will be handled under the respective entity, maintaining compliance and operational clarity.

Chargebee upgrades Braintree SDK to v3.41.0

Chargebee has upgraded its Braintree Java SDK from version 3.25.0 to 3.41.0 to meet upcoming compliance requirements.

Why is this important?

Braintree plans to update its root SSL certificate for API traffic on June 30, 2025. After this date, any integration running on a legacy SDK version, including Chargebee's previously used Java SDK 3.25.0, will be blocked from processing transactions. This upgrade ensures continued access to Braintree's payment services and helps you avoid service disruptions.

How can you use it?

If you're using Chargebee's native Braintree integration, you need not take any action. The upgraded SDK ensures secure, uninterrupted payment processing in both production and Sandbox environments. If you're using a custom integration or third-party plugin, make sure it supports the minimum SDK requirements outlined by Braintree.

Payment Verification now available in Chargebee.js

Chargebee now supports Payment Verification controls in Chargebee.js, extending the coverage beyond the in-app layout for Chargebee Checkout.

Why is this important?

With this enhancement, you can apply Chargebee's Payment Verification rules to card components via Chargebee.js, the same support offered in Chargebee's hosted pages. This helps optimise revenue by reducing transaction failures, minimizing processing costs, and improving payment efficiency.

How can you use it?

To enable Payment Verification in Chargebee.js, add your domain to the allowlist. Once done, the verification settings configured in your Chargebee Billing site will automatically apply.

Map Apple and Google products to plans in Chargebee Billing (EAP)

You can now link Apple App Store and Google Play Store products to Chargebee Billing plans, allowing you to centrally manage entitlements and automatically control customer access based on subscription status across mobile and web platforms.

Why is this important?

This eliminates the need for custom backend development to manage in-app entitlements. It gives your revenue and growth teams more control to experiment with entitlements across channels.

How can you use it?

To map your store products to Chargebee Billing plans, follow these steps:

• 1. Map Apple and Google products
• 2. Retrieve entitlements for a linked product in Chargebee
• 3. Unlink Google Play Store or Apple App Store products

Note: Mobile Subscription features are in Early Access. Submit a request to enable this feature.

Legal agreements now respect full locale codes

When creating a Checkout session setting the customer[locale] parameter with both a language and region code (like fr-FR), you may have noticed that legal agreements always appeared in English. This didn't happen when only the language code was used (like fr). We've fixed this inconsistency.

Renewal schedules now re-align after addon removal

We've fixed an issue where with Multi-frequency billing enabled, removing an addon from a subscription that also includes quarterly or yearly items, prevented remaining items from renewing as expected. The renewal job didn't re-align correctly after such changes, causing gaps in invoicing for other active addons. With this fix, the renewal schedule now updates properly whenever you modify subscription items, ensuring all applicable items continue to renew without interruption.

Free period now included in advance invoice billing range

When creating future-dated subscriptions with a free period, you may have noticed that advance invoices failed to include the free period in the billing duration, showing only the paid cycle instead. This could lead to confusion when previewing invoices or reviewing the next billing date, as it did not reflect the complete subscription term. We've fixed this. Now, when you generate an advance invoice for a subscription in the future state, the billing period will accurately include the free period.

Discounts now appear reliably in the order summary

If you use the full-page layout in Checkout, the line-item level discounts occasionally disappeared from the order summary page, causing unexpected changes to the final total displayed to your customer. This issue has now been fixed.

Typo fix for dropdown labels on Checkout

We've fixed a small but noticeable typo in the full-page layout of Checkout that showed Pick a option instead of the correct Pick an option for dropdown custom fields.

Payment instructions in draft state no longer appear on invoices

We've fixed an issue where payment instructions in a draft state were sometime incorrectly included on invoices. This caused unintended bank account details—such as JPY-based instructions from HSBC—to appear on invoices issued in other currencies like EUR. With this update, only active and relevant payment instructions are displayed on invoices, helping you avoid sending conflicting or incorrect bank details to your customers.

Fix for missing PO number on invoice in in-app layout

If you're using an in-app layout and have the PO number field disabled in your checkout configuration, you may have noticed that even when the invoice[po_number] parameter is passed through the API during session creation, it doesn't appear on the invoice. This issue has now been resolved.

Custom fields now appear correctly in invoice lists

We've fixed an issue where payment instructions in a draft state were sometime incorrectly included on invoices. This caused unintended bank account details—such as JPY-based instructions from HSBC—to appear on invoices issued in other currencies like EUR. With this update, only active and relevant payment instructions are displayed on invoices, helping you avoid sending conflicting or incorrect bank details to your customers.

Error with Checkout.com on full-page Checkout resolved

If you use Checkout.com as your payment gateway, full-page layout for Chargebee Checkout, and have hidden the email field, while already having the customer's email in Chargebee, your customers may have encountered an error message "Customer not returned from Checkout.com", during 3D Secure authentication. This issue has now been fixed.

Avoid customer drop-offs with better expiry year validation

We've updated the in-app layout for Checkout to accept only two digits as the input for the credit card Expiry field. Previously, customers could enter a four-digit year, only to face errors on the next step, leading to friction or abandonment.