October 2025

Update to column order in subscriptions export

We have adjusted the column order in the subscriptions.csv export by moving the following plan-specific fields to the end of the file:

• subscriptions.plan_id
• subscriptions.plan_quantity
• subscriptions.plan_unit_price
• subscriptions.plan_amount
• subscriptions.plan_quantity_in_decimal
• subscriptions.plan_unit_price_in_decimal
• subscriptions.plan_amount_in_decimal

Why is this important?

This update helps prepare the subscriptions.csv export for upcoming improvements related to plans and ensures a more consistent structure across exports.

How can you use it?

If your internal reports or downstream workflows reference columns by their position, be sure to update your parsing logic to reflect the new column positions. This will help you avoid any disruptions or misaligned data.

New recurring payment options for Bancontact via Mollie

Previously, recurring payments for Bancontact transactions via Mollie were only supported through SEPA Direct Debit. You can now choose to process recurring payments using Bancontact Wallet Initiated Payment (WIP) as well. This enhancement offers two configuration options for handling Bancontact renewals, either via SEPA or WIP, tailored to your business and customer needs.

Why is this important?

This update expands your flexibility in managing recurring Bancontact payments. Bancontact Wallet Initiated Payment (WIP) offers instant payment confirmation, unlike SEPA, which takes 2 to 3 days. This provides you with more flexibility to deliver a faster, consistent Bancontact experience.

How can you use it?

In your Chargebee Billing site, go to Settings > Configure Chargebee > Payment Gateway, select Mollie, and under Recurring Payment Method, choose one of the following:

- Recurring via SEPA Direct Debit: First payment via Bancontact, renewals via SEPA. (Ensure SEPA is enabled in both Mollie and Chargebee). - Recurring via Bancontact (WIP): First payment via Bancontact, renewals via Wallet Initiated Payment. (No SEPA setup required.)

Error handling now configurable under Billing LogIQ

Error Settings for payment failures is now available under Billing LogIQ.

Why is this important?

This change consolidates all payment error handling controls into a single, centralized section, making configuration easier and more consistent.

How can you use it?

In your Chargebee Billing site, go to Configure Chargebee > Billing LogIQ > Payments > Error Settings to define how the system should behave when specific payment errors occur, such as during retries. Future payment-related configurations will also be added here, so you can manage everything in one place.

Efficient creation of Stripe VBAs in Full Page Checkout

We fixed an issue where enabling Chargebee Full Page Checkout from the Checkout settings page caused GoCardless Direct Debit payments to fail with a "Gateway not supported" error. This happened because certain backend configurations were not applied automatically. With this update, the required configurations are now set up when you enable Chargebee Full Page Checkout through the Chargebee UI, ensuring GoCardless transactions are processed successfully without requiring manual setup.

Resolved unintended Stripe VBA creation in MBE Setup

We fixed an issue in Multi-Business Entity setups where Virtual Bank Accounts (VBAs) were still being created for new customers, even after ACH and SEPA Credit Transfer were disabled for Stripe via Smart Routing. This occurred because entity-level overrides were not being cleared properly when Smart Routing rules were removed. The fix ensures that both Smart Routing rules and associated entity-level configurations are cleaned up correctly, preventing unintended VBA creation.

Fix for submit button spinner issue in Checkout

We resolved an issue where the spinner on Chargebee Checkout's submit button on the full-page layout sometimes failed to appear during form submission. The fix ensures that the button now correctly shows the loading spinner and remains disabled while the customer's order is being processed.

Localization fix for payment method redirect text on Checkout

When customers completed checkout in a non-English locale, the redirect message shown for certain payment methods (like PayPal and 3D Secure cards) was displayed only in English. This issue has been fixed. Now, the message correctly appears in the customer's selected language.

Fix for payment failure in Pay Now when adding a new card

For Pay Now, when adding a new card for payment, we fixed an issue that caused payments to sometimes fail with an "invalid_request payment_source_id" error even though the card was authorized.

Address auto-fill formatting issue fixed in Checkout

We fixed an issue where shipping and billing addresses were sometimes being displayed in the wrong order on Checkout when populated from Google's address suggestions. Chargebee now recognizes both long and short address formats and correctly arranges them in the USPS-style order (for example, "8250 Meadow Rd, Dallas, TX, USA"). This ensures that address details appear correctly for your customers during checkout, reducing friction, and preventing fulfillment or CRM mismatches for your team.

VAT field validation issue fixed in Checkout

We've fixed an issue that prevented customers from completing checkout when e-invoicing was enabled for a country. Previously, even though the VAT number field was set to optional, the error caused Chargebee to treat it as mandatory. This resulted in failed payments for customers who didn't enter a VAT number.

Fixed addon deselection issue in Checkout

Previously, when you deselect an addon during a full-page Checkout session to update a subscription, the addon still appeared in the subscription. This issue has been fixed so that removing an addon during checkout now correctly updates the subscription and billing details.

Excess payments display issue fixed for full-page Checkout

Previously, credits from excess payments were not displayed correctly on full-page Checkout, showing as zero, though the subtotal was displayed correctly. This has been fixed.

Fixed incorrect "Credits applied" field in checkout

A zero-value "Credits Applied" line appeared in some full-page Checkout sessions even when no credits were applied. This issue has been fixed.

Improved reliability when changing plans across families

You can now edit subscriptions with multiple plans, without encountering API errors. Previously, switching a plan to a different item family through the Change Plan option caused the UI to mismanage form fields, leading to blocked edits. With this fix, form fields are now generated and maintained correctly when you change plans across families, ensuring uninterrupted updates and a more reliable editing experience.

Improved stability for subscriptions created before enabling Multi-frequency Billing

You'll no longer encounter errors when resuming subscriptions that were created before Multi-frequency Billing was enabled. Earlier, such resumptions could cause exceptions due to missing term information for addons. With this fix, subscriptions created before enabling Multi-frequency Billing now behave as expected until their next renewal, ensuring consistent performance and uninterrupted subscription management.