Zum Inhalt springen

Chargebee Release Notes

1.904 Einträge aus 1 Quelle. Zuletzt aktualisiert:

Folge Chargebee, um die Release Notes in deinen Feed zu holen.

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Neue Usage APIs für mehr Transparenz bei der Nutzung

Die neuen Usage Summary und Usage Charges APIs zeigen aggregierte Nutzung sowie Stand, Overage und unberechnete Kosten im aktuellen Zyklus, und die Upcoming Invoice Estimate API kann nun usage-basierte Line Items enthalten.

You can now use Chargebees Usage APIs to bring usage visibility directly into your portal and product experiences. The new Usage Summary API helps you show how usage changes over time with aggregated views across minute, hour, day, week, or month. The new Usage Charges API 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 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? …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Multi-Plan-Subscriptions im Checkout

Im Checkout lassen sich nun Subscriptions mit mehreren Plänen in einer Session erstellen, sofern sie dieselbe Abrechnungsfrequenz haben; die Aktivierung von Multi-Plan Subscriptions und der Checkout-Unterstützung erfolgt über den Chargebee Support.

You can now create subscriptions with multiple plans in a single Checkout session as long as they share the same billing frequency. This removes the earlier limitation of one plan 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. 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 to enable the following:

  1. Multi-Plan Subscriptions (MPS).
  2. Support for the MPS feature in Checkout.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Twikey als Payment Gateway für SEPA-Lastschrift

Chargebee unterstützt jetzt Twikey als Payment Gateway, um SEPA-Lastschriftzahlungen in Europa zu akzeptieren.

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 Learn more about configuring SEPA via Twikey: SEPA Direct Debit

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Level-2- und Level-3-Daten für BlueSnap und Braintree

Chargebee unterstützt nun Level-2- und Level-3-Daten für BlueSnap und Braintree, um bei B2B- und B2G-Kreditkartenzahlungen erweiterte Transaktionsdetails zu übermitteln.

Chargebee now supports Level 2 and Level 3 data 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. For sending Level 3 data, follow the steps outlined in this section.

Learn more about Level 2/ 3 data support in BlueSnap. Learn more about Level 2/3 data support in Braintree.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Rechnungsadresse als Pflichtfeld für Kunden festlegbar

Felder der Rechnungsadresse können nun beim Anlegen oder Aktualisieren von Kundendatensätzen als Pflichtfelder festgelegt werden, um Steuerfehler zu vermeiden.

You can now make billing address fields mandatory 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Vorab-Rechnungen in Chargebee CPQ Quotes

Der Quote Form Builder in Chargebee CPQ unterstützt jetzt die Erstellung von Rechnungen im Voraus, aktivierbar für alle Kunden oder einzeln pro Quote, statt wie bisher nur zum Verlängerungszeitpunkt.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Suchleiste für zugeordnete Items in der Chargebee-Oberfläche

Zugeordnete Addons und Charges lassen sich in der Oberfläche jetzt über eine Suchleiste nach Item-Name und Item-ID filtern.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix für Apple Pay Transaction Descriptors mit Stripe

Ein Fehler wurde behoben, durch den der Descriptor-Suffix bei über Stripe verarbeiteten Apple-Pay-Zahlungen nicht korrekt angewendet wurde, sodass er nun auf Kundenabrechnungen angezeigt wird.

We've fixed an issue where transaction descriptors for Apple Pay payments processed via Stripe did not correctly apply the 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Quote-Namen-Fix und Klarstellung zu Rabatten

Bearbeitete Quote-Namen werden nach Updates jetzt korrekt angezeigt, außerdem wird erklärt, dass einmalige Rabatte in Verlängerungs-Quote-PDFs erwartungsgemäß doppelt erscheinen können, wenn sie bei einer nicht anteilig berechneten Änderung und erneut in der Verlängerungs-Quote hinzugefügt wurden.

We fixed an issue in 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Doppelte benutzerdefinierte Quote-Notizen behoben

Benutzerdefinierte Notizen erscheinen nach dem Bearbeiten und Speichern einer Quote im PDF nicht mehr doppelt, sondern nur noch einmal.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Hosted Checkout zeigt korrekte Quote-Positionen

Im Hosted Checkout für CPQ Quotes erscheinen entfernte Charges oder Addons nicht mehr, sodass der Checkout nur die aktuell in der Quote enthaltenen Positionen und den korrekten Gesamtbetrag zeigt.

An issue where removed charges continued to appear in the Hosted Checkout for CPQ quotes has now been resolved. Earlier, even if you removed an Addon 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

PO-Nummer wird nach Hosted Checkout auf Rechnungen übernommen

Bei Annahme einer Quote über den Hosted Checkout wird die PO-Nummer jetzt korrekt an die Rechnung übergeben.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Button „Proceed to Pay“ auf Mobilgeräten wieder sichtbar

Auf Accept-Quote-Hosted-Pages, die über CPQ erstellt wurden, ist der Button „Proceed to Pay“ bei aktivierten enhanced payment components jetzt auch auf Mobilgeräten sichtbar.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Anwendbare Addons und Charges in CPQ Quotes korrekt angezeigt

In CPQ Quotes werden Applicable Addons and Charges jetzt entsprechend der Plan-Konfiguration angezeigt, die Validierung erfolgt bei der Auswahl und Fehlermeldungen sind aussagekräftiger.

Applicable Addons and 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Fix für fehlgeschlagene Freigabeanfragen bei CPQ-Quotes

Freigabeanfragen für Amendment Quotes scheitern bei konfigurierten Approval-Regeln nicht mehr an zu langen Headlines, da die Headline-Erzeugung die Längenbegrenzung nun einhält.

We have fixed an issue in CPQ Quotes where requesting approval for amendment quotes 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Amendment Quotes mit geplanten Änderungen bearbeitbar

Amendment Quotes mit Vertragslaufzeiten, die zukünftig geplante Änderungen enthalten, lassen sich jetzt ohne CPQ-Validierungsfehler in Chargebee und im Salesforce Quote Editor bearbeiten und speichern.

You can now edit and save amendment quotes 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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Quote-Erstellung bei deaktiviertem Price Override behoben

CPQ-Quotes können aus Salesforce nun auch bei deaktiviertem Price Override erstellt werden, wenn der übermittelte Unit Price dem Katalogpreis entspricht.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Paystack und ACH über Checkout.com allgemein verfügbar

Das Payment Gateway Paystack und ACH-Zahlungen über Checkout.com sind in Chargebee jetzt allgemein verfügbar und lassen sich unter Payment Gateways konfigurieren.

The Paystack payment gateway and ACH payments via Checkout.com are now generally available in Chargebee. These additions expand your payment capabilities by supporting region-specific payment methods and bank-based transactions.

Why is this important?

Adding Paystack and ACH through Checkout.com helps you support local payment preferences and improve payment success rates across different regions. - Paystack is widely used across Africa, especially in markets such as Nigeria and Ghana where local cards and bank transfers are common. - ACH payments via Checkout.com allow direct bank payments in the US, offering a cost-effective alternative to card transactions. - Supporting these payment methods helps you reach new customer segments and optimize transaction costs in key markets.

How can you use it?

Follow these steps in your Chargebee site to configure these payment gateways and payment methods:

  1. Log in to your Chargebee Billing site.
  2. Go to Settings > Configure Chargebee > Payment Gateways.
  3. Add Paystack as a new payment gateway or enable ACH under your configured Checkout.com gateway.
  4. Enter the required credentials and save your changes.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Migration von UPI Collect zu UPI Intent bei Razorpay

Aufgrund neuer NPCI-Vorgaben wird der Razorpay-Flow UPI Collect eingestellt, weshalb Nutzer auf UPI Intent migrieren müssen und dazu bei handlePayment() den vpa-Parameter nicht mehr übergeben sollen.

Chargebee requires you to migrate from Razorpay's UPI Collect flow to the UPI Intent flow due to recent compliance updates from the National Payments Corporation of India (NPCI). The UPI Collect flow, which supports payments through UPI ID or VPA (Virtual Payment Address) entry, is being sunset and will no longer be supported for one-time or recurring payments.

Why is this important?

If UPI Collect remains enabled, transactions may fail once the flow is deprecated. Migrating to UPI Intent keeps your checkout compliant and ensures uninterrupted payments. - UPI Intent automatically opens a customer's preferred UPI app instead of requiring manual VPA entry. - This reduces payment failures caused by deprecated flows. - The experience is faster and better aligned with current NPCI guidelines.

How can you use it?

Follow this tutorial to set up the UPI Intent flow for Razorpay. When calling handlePayment(), do not pass the vpa parameter. This triggers the default payment flow for both desktop and mobile web automatically. For additional control, you can also use the **** function to retrieve the list of supported UPI apps.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Chargebee

Löschen der letzten gespeicherten Zahlungsmethode verhindern

Chargebee Billing kann nun das Löschen der letzten gültigen Zahlungsmethode eines Kunden in App, Self-serve Portal und API blockieren, aktivierbar in den Payment Preferences.

Chargebee Billing now lets you block the deletion of a customer's last saved payment method. When enabled, Chargebee prevents a payment method from being removed if it is the only valid payment method on the customer's profile. This rule is enforced across the Chargebee app, Self-serve Portal, and API endpoints to ensure consistent behavior across all interfaces.

Why is this important?

Deleting the only valid payment method on a customer's profile can cause subscription renewals to fail and interrupt billing cycles. - Ensures at least one valid payment method is always available for upcoming renewals. - Reduces the risk of payment failures and revenue loss. - Maintains billing continuity across the app, portal, and APIs.

How can you use it?

Follow these steps in your Chargebee site:

  1. Log in to your Chargebee Billing site.
  2. Go to Settings > Configure Chargebee > Payment Gateways.
  3. Click Manage Settings in the Payment Preferences section.
  4. Under Common Settings, enable the Block Deletion of the Last Saved Payment Method option.

Once enabled, Chargebee automatically restricts attempts to remove a customer's only valid payment method across the app, self-serve portal, and API endpoints.

Originalquelle(öffnet in neuem Tab)Problem melden