# March 2026

Chargebee product updates released in March 2026.

Source: https://release-notes.chargebee.com/march-2026

<Update tags={["NEW FEATURE"]} topics={["Usage-Based Billing"]}>
  ## Give customers better visibility into usage with new APIs

  You can now use Chargebees Usage APIs to bring usage visibility directly into your portal and product experiences. The new [Usage Summary API](https://apidocs.chargebee.com/docs/api/usage_summaries/retrieve-usage-summary-for-a-subscription) helps you show how usage changes over time with aggregated views across minute, hour, day, week, or month. The new [Usage Charges API](https://apidocs.chargebee.com/docs/api/usage_charges/retrieve-usage-charges-for-a-subscription) helps you show where a subscription stands in the current cycle, including total usage, included usage, overage exposure, and current unbilled charges. The enhanced [Upcoming Invoice Estimate API](https://apidocs.chargebee.com/docs/api/estimates/upcoming-invoices-estimate#include_usage_charges) can now include usage-based line items.

  ### **Why is this important?**

  This helps you give customers better clarity before an invoice is generated. Instead of waiting until invoicing is complete, you can show historical usage trends, current-cycle usage and overages, and expected invoice impact in one experience. That can reduce invoice surprise, improve billing transparency, and make it easier for customers to understand how their usage is translating into charges.

  ### **How can you use it?**

  You can use these APIs together to build customer-facing dashboards, portal views, in-app usage cards, support workflows, and pre-renewal billing previews. Use the Usage Summary API for trend charts and reporting views, the Usage Charges API for current-cycle visibility into included versus consumed usage and chargeable overages, and the Upcoming Invoice Estimate API to show projected recurring and usage-based charges side-by-side before billing.
</Update>

<Update tags={["NEW FEATURE"]} topics={["Hosted Pages"]}>
  ## Simplify multi-product purchases in Checkout

  You can now create subscriptions with [multiple plans](https://www.chargebee.com/docs/billing/2.0/subscriptions/multi-plans-subscriptions) in a single [Checkout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout) session as long as they share the same billing frequency. This removes the earlier limitation of one [plan](https://www.chargebee.com/docs/billing/2.0/product-catalog/plans) per subscription and lets you sell multiple independent products together. The plans can be across different product families.

  ### **Why is this important?**

  If you sell multiple standalone products, you no longer need to create separate subscriptions or rely on workarounds like zero-currency plans and [addons](https://www.chargebee.com/docs/billing/2.0/product-catalog/addons). Instead, you can consolidate purchases into a single checkout, subscription, and invoice, as long as all selected plans share the same billing frequency. It also reduces catalog setup effort and better reflects how you package and sell your offerings.

  ### **How can you use it?**

  [Contact Chargebee Support](https://www.chargebee.com/docs/billing/2.0/kb/getting-started/how-to-contact-chargebees-support-team?utm_source=docs_rn&utm_medium=content&utm_campaign=support) to enable the following:
  1. Multi-Plan Subscriptions (MPS).
  2. Support for the MPS feature in Checkout.
  <TrainnVideo id="3IIxXO9xU8UxFY5QGTXe4A" />
</Update>

<Update tags={["NEW FEATURE", "BETA"]} topics={["Payments"]}>
  ## Twikey support for SEPA Direct Debit payments

  Chargebee now supports **Twikey** as a payment gateway, allowing you to accept **SEPA Direct Debit payments** across Europe.

  ### **Why is this important?**

  Twikey is designed for recurring payments and direct debit workflows, making it well-suited for businesses operating in the EU and SEPA region. It helps you manage mandates efficiently and improves payment success rates for subscription billing.
  \- Collect payments directly from customer bank accounts at lower transaction costs.
  \- Increase payment success rates compared to card payments.
  \- Reduce churn by offering a widely preferred payment method across Europe.

  ### **How can you use it?**

  Configure Twikey as a payment gateway in Chargebee and enable SEPA Direct Debit to start collecting bank payments from your customers.

  Learn more about Twikey: [Twikey configuration](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/twikey-overview)
  Learn more about configuring SEPA via Twikey: [SEPA Direct Debit](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/twikey-sepa)

  <Image src="/screenshots/march_2026/twikey-sepa.png" alt="" />
</Update>

<Update tags={["NEW FEATURE"]} topics={["Payments"]}>
  ## Chargebee now supports Level 2 and Level 3 data for BlueSnap and Braintree

  Chargebee now supports [Level 2 and Level 3 data](https://www.chargebee.com/docs/payments/2.0/level-2-3-data-support/level2-3-data-support) for Bluesnap and Braintree, enabling you to send enhanced transaction details for B2B and B2G credit card payments.

  ### **Why is this important?**

  Level 2 and Level 3 data allow you to include additional transaction details such as tax, customer, and line-item information during payment processing. This helps reduce interchange fees, improve authorization rates, and provide better visibility into transaction data.

  ### **How can you use it?**

  When using BlueSnap or Braintree as your payment gateway in Chargebee, you can enable this feature by selecting the **Level 2** option while following the [common configuration steps](https://www.chargebee.com/docs/payments/2.0/level-2-3-data-support/level2-3-data-support#common-configuration-steps). For sending **Level 3** data, follow the steps outlined in [this section.](https://www.chargebee.com/docs/payments/2.0/level-2-3-data-support/level2-3-data-support#steps-to-configure-level-3-data)

  Learn more about [Level 2/ 3 data support in BlueSnap](https://www.chargebee.com/docs/payments/2.0/level-2-3-data-support/level2-3-data-support#bluesnap).
  Learn more about [Level 2/3 data support in Braintree](https://www.chargebee.com/docs/payments/2.0/level-2-3-data-support/level2-3-data-support#braintree).

  <Image src="/screenshots/march_2026/level2-3 data.png" alt="" />
</Update>

<Update tags={["ENHANCEMENT"]} topics={["Subscriptions"]}>
  ## Make the billing address mandatory for accurate tax handling

  You can now make billing address fields [mandatory](https://www.chargebee.com/docs/billing/2.0/site-configuration/mandatory-fields#configuring-mandatory-fields) while creating or updating customer records.

  ### **Why is this important?**

  Missing billing address information can lead to incorrect tax calculation and compliance issues. By capturing this detail upfront, you reduce the risk of tax errors and ensure that every customer record is complete and reliable for downstream billing and reporting.

  ### **How can you use it?**

  1. Navigate to **Settings** > **Configure Chargebee** > **Advanced** > **Mandatory Fields**.
  2. On the **Mandatory Fields** page, navigate to the **Billing Address** section, and use the toggle to mark required fields as mandatory.
  3. Click **Apply** > **Confirm**.

  Once enabled, this information must be provided when creating or updating a customer record, helping maintain consistent data quality across all customer profiles.

  <Image src="/screenshots/march_2026/billing-address-mand.gif" alt="" />
</Update>

<Update tags={["ENHANCEMENT"]} topics={["CPQ"]}>
  ## Unlock upfront billing clarity in your CPQ quotes

  [Quote Form Builder](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-quote-form-builder) in Chargebee CPQ now supports generating invoices upfront. Earlier, you could only generate invoices at the time of renewal through billing cycles. This made it challenging to plan your cash flow, share a clear billing schedule upfront so your customers can anticipate upcoming charges and avoid surprises, or ensure your invoices match agreed contract terms, especially for longer commitments.

  ### **Why is this important?**

  Upfront visibility reduces miscommunication and gives your customers a clear view of upcoming charges and timelines before they commit, building trust. For you, this means better cash flow planning with predictable invoicing and reduced operational effort by eliminating the need to review, adjust, or trigger invoices at each renewal.

  ### **How can you use it?**

  You can choose to enable this option for all customer quotes or for individual customers.

  **For all customers:**
  1. Navigate to **Settings** > **Configure Chargebee** > **Chargebee CPQ**
  2. Click **Quote Form Builder**.
  3. Navigate to **Billing and Terms** > **Generate Advance Invoice**.

  **For individual customers**:
  Select the **Generate Advance Invoices** option while creating a quote or from the **Edit Quote** page.

  <Image src="/screenshots/march_2026/advance_invoices.png" alt="" />
</Update>

<Update tags={["UI ENHANCEMENT"]} topics={["Product Catalog"]}>
  ## Added an Item search bar in UI

  You can now search attached addons and charges directly within the UI using a dedicated search bar that filters items by Item name and Item ID.

  ### **Why is this important?**

  As your list of attached items grows, manually scanning through them can take time and increase the likelihood of selecting the wrong item. This update helps you quickly narrow down results, improving accuracy and reducing effort when working with large catalogs.

  ### **How can you use it?**

  Navigate to the section with attached add-ons and charges, and use the search bar at the top to enter a name or ID. The list updates instantly, allowing you to identify and select the required item with ease.

  <Image src="/screenshots/march_2026/item_search_bar.png" alt="" />
</Update>

<Update tags={["BUG FIX"]} topics={["Payments"]}>
  ## Fix for Apple Pay transaction descriptors with Stripe

  We've fixed an issue where transaction descriptors for Apple Pay payments processed via Stripe did not correctly apply the `statement_descriptor_suffix` for non-card transactions. As a result, charge descriptions could appear incomplete or inconsistent on customer statements. With this fix, the descriptor suffix is now passed and displayed as expected, ensuring your transaction descriptors remain accurate and recognizable and reducing customer confusion and related support requests.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Quote name fix and discount behavior clarification

  We fixed an issue in [Quotes](https://www.chargebee.com/docs/billing/2.0/invoices-credit-notes-and-quotes/quotes) where edited quote names were not reflected after updates, so your changes now display correctly. We would also like to clarify why one-time discounts can appear twice in renewal quote PDFs. This happens when a discount is added during a non-prorated subscription change and again in a renewal quote, as both are applied at renewal. This is an expected behavior, and the quote accurately reflects all applicable discounts for the renewal.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Resolved duplication of custom quote notes

  Previously, when you edited and saved a quote, the generated PDF displayed custom notes twice because site level notes were added again to the quote during edit and rendered along with existing quote level notes. With this fix, notes are now handled correctly and appear only once in the PDF, ensuring your quotes remain clear and accurate for customers.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Hosted Checkout now shows accurate quote items

  An issue where removed charges continued to appear in the Hosted Checkout for [CPQ quotes](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq) has now been resolved. Earlier, even if you removed an [Addon](https://www.chargebee.com/docs/billing/2.0/product-catalog/addons) while creating or updating a quote, it could still show up on the checkout page because it was originally tied to the plan. This created a mismatch between the quote, its PDF, and the checkout page, which could confuse customers, block them from completing the purchase, or lead to unintended extra charges. With this fix, the checkout now reflects only the items currently included in the quote, so your customers see the correct total and can proceed with confidence.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Invoices now include PO number after hosted checkout

  When a customer accepted a quote via hosted checkout, the PO number was not carried over to the invoice, resulting in invoices without the required purchase order reference. This could make it harder for you and your customer to identify and approve the invoice, potentially delaying payment. With this fix, the PO number is now passed correctly during checkout, ensuring that invoices generated from accepted quotes include the expected PO number and match your records.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Proceed to Pay button now visible on mobile for quote-based checkouts

  Earlier, the **Proceed to Pay** button was not visible on mobile devices for Accept Quote hosted pages created via CPQ when the enhanced payment components experience was enabled. While this was not an issue on desktop, customers accessing the same link on mobile could not complete the payment due to the missing call-to-action button. With this fix, you can confidently share accept quote links with your customers, knowing they can complete payments on both desktop and mobile devices without interruption.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Applicable addons and charges now shown correctly in CPQ quotes

  [Applicable Addons and Charges](https://www.chargebee.com/docs/billing/2.0/product-catalog/applicable-addons-charges) are now displayed correctly in CPQ quotes based on your plan configuration. Earlier, all Addons and Charges were listed regardless of plan applicability, which led to invalid selections and a generic error during save. With this fix, validation is enforced at the time of selection so you can add only the relevant addons and charges for the plan, and improved error messaging provides clearer guidance when an issue occurs. This helps you avoid incorrect configurations and create quotes with greater accuracy.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Fix for approval request failure in CPQ quotes

  We have fixed an issue in CPQ Quotes where requesting approval for [amendment quotes](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-amendment-quote) failed when quote approval rules were configured, due to headline length validation. When the generated approval headline exceeded the allowed limit, the request was blocked with an error. With this fix, headline generation now adheres to length constraints so you can submit approval requests without interruption.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Amendment quotes with scheduled changes now editable

  You can now edit and save [amendment quotes](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-amendment-quote) that include contract terms with future-scheduled changes without errors. Previously, such updates triggered a CPQ validation error, preventing you from making changes in Chargebee or the Salesforce Quote Editor. This fix lets you manage amendment quotes without interruptions.
</Update>

<Update tags={["BUG FIX"]} topics={["CPQ"]}>
  ## Resolved - Quote creation error when override is disabled

  You can now create CPQ quotes from Salesforce even when price override is disabled. Previously, quote creation failed if the unit price parameter was included in the request, even when it matched the catalog price, as the system treated it as a price override. This fix ensures that quotes using catalog pricing are processed successfully without requiring the price override setting to be enabled, reducing unnecessary errors and allowing you to proceed with standard pricing workflows.
</Update>