Zum Inhalt springen

Chargebee Release Notes

Einträge
1.910
Quellen
1
Zuletzt aktualisiert

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

Chargebee

Korrekte Abrechnungszyklen bei rückdatierten Abos mit Multi-frequency billing

Beim Anlegen rückdatierter Abonnements in Multi-frequency billing werden die Abrechnungszyklen eines Addons automatisch um den Rückdatierungszeitraum reduziert, sofern dessen Gesamtlaufzeit mindestens so lang ist, andernfalls wird die Erstellung mit einem Fehler verhindert.

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? …

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Gift Subscriptions mit Multi Business Entity nutzbar

Gift Subscriptions werden jetzt auf Sites mit Multi-Business-Entity-Konfiguration unterstützt, sodass Rechnungsstellung, Verlängerungen und Verwaltung der Geschenk-Abos der jeweiligen Entität zugeordnet werden.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Chargebee aktualisiert Braintree SDK auf Version 3.41.0

Chargebee hat sein Braintree Java SDK von 3.25.0 auf 3.41.0 aktualisiert, damit Transaktionen nach der Braintree-Zertifikatsumstellung am 30. Juni 2025 nicht blockiert werden; bei nativer Integration ist keine Aktion nötig.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Payment Verification jetzt in Chargebee.js verfügbar

Chargebees Payment-Verification-Regeln lassen sich nun auch auf Kartenkomponenten über Chargebee.js anwenden, nachdem die Domain zur Allowlist hinzugefügt wurde.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Apple- und Google-Produkte auf Chargebee-Pläne mappen (EAP)

Produkte aus dem Apple App Store und Google Play Store können nun mit Chargebee-Billing-Plänen verknüpft werden, um Entitlements zentral zu verwalten; die Funktion ist im Early Access und muss angefragt werden.

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:

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

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Legal Agreements berücksichtigen vollständige Locale-Codes

Legal Agreements wurden bei Checkout-Sitzungen mit Sprach- und Regionscode im Locale-Parameter immer auf Englisch angezeigt, was nun behoben ist.

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

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Renewal-Zeitplan nach Entfernen eines Addons korrekt neu ausgerichtet

Mit aktivierter Multi-frequency billing wird der Renewal-Zeitplan nach dem Entfernen eines Addons nun korrekt aktualisiert, sodass die übrigen Items einer Subscription mit quartalsweisen oder jährlichen Positionen ohne Rechnungslücken weiter erneuert werden.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Free period jetzt im Abrechnungszeitraum von Advance Invoices enthalten

Bei Advance Invoices für zukünftige Subscriptions mit Free period umfasst der Abrechnungszeitraum nun auch die kostenlose Phase statt nur den bezahlten Zyklus.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Rabatte erscheinen zuverlässig in der Bestellübersicht

Im Full-page layout von Checkout verschwinden Rabatte auf Line-Item-Ebene nicht mehr gelegentlich aus der Bestellübersicht, sodass die angezeigte Gesamtsumme stimmt.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Payment Instructions im Entwurfsstatus erscheinen nicht mehr auf Rechnungen

Auf Rechnungen werden nur noch aktive und relevante Payment Instructions angezeigt, sodass keine Bankdaten im Entwurfsstatus, etwa JPY-Angaben von HSBC auf EUR-Rechnungen, mehr auftauchen.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

PO-Nummer erscheint im In-app layout wieder auf der Rechnung

Bei deaktiviertem PO-number-Feld im In-app layout wird eine per API bei der Session-Erstellung übergebene PO-Nummer nun korrekt auf der Rechnung angezeigt.

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 parameter is passed through the API during session creation, it doesn't appear on the invoice. This issue has now been resolved.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Custom Fields in Rechnungslisten (Payment Instructions im Entwurf)

Der Text beschreibt die Korrektur, dass Payment Instructions im Entwurfsstatus nicht mehr fälschlich auf Rechnungen erscheinen und nur noch aktive, relevante Anweisungen angezeigt werden, obwohl der Titel von Custom Fields in Rechnungslisten spricht.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Fehler mit Checkout.com im Full-page Checkout behoben

Bei Checkout.com als Gateway, Full-page layout und ausgeblendetem E-Mail-Feld tritt bei der 3D-Secure-Authentifizierung nicht mehr der Fehler "Customer not returned from Checkout.com" auf, wenn die E-Mail des Kunden bereits in Chargebee vorhanden ist.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Ablaufjahr-Feld im In-app layout akzeptiert nur zwei Ziffern

Im In-app layout von Checkout akzeptiert das Kreditkartenfeld Expiry nur noch zweistellige Jahresangaben, damit Kunden bei vierstelliger Eingabe nicht im nächsten Schritt auf Fehler stoßen.

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.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Addons jetzt in Pricing Tables unterstützt

Pricing Tables unterstützen nun Addons aus Billing, einschließlich vorausgewählter Mandatory addons, auswählbarer Recommended addons, Differential pricing und Price variants sowie detaillierterer Layout-Anpassung.

Pricing Tables now support addons from Billing. With this update you can: - Ensure all the applicable addons are displayed with your plans on pricing tables. - Customize the layout and elements of pricing tables in more detail.

Why is this important?

- Mandatory addons are pre-selected with the plan in the pricing table, ensuring customers understand the full cost from the start, preventing unexpected charges at checkout. - Recommended addons are available for your customers to select, offering them more ways to customize their subscriptions. - Differential pricing for addons is supported, and price variants are considered, ensuring pricing accuracy. - Existing subscribers can see their current plan and ad…

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Dunning per API pausieren und fortsetzen

Neue API-Endpunkte erlauben es, Dunning zu pausieren, optional mit expected_payment_date für eine automatische Wiederaufnahme, und es jederzeit direkt wieder fortzusetzen.

We're introducing new API endpoints that allow you to pause and resume dunning for your subscriptions. With the pause dunning API, you can halt dunning for a subscription and optionally specify an expected payment date, which will automatically schedule its resumption. The resume dunning API provides a direct way to restart dunning at any time.

Why is this important?

You can now programmatically manage when dunning is active, which is particularly useful for handling customer requests for payment extensions, temporary payment issues, or specific customer service scenarios.

How can you use it?

You can access these new functionalities through our API. For the Pause Dunning API, use the specified endpoint and include the expected_payment_date parameter if you wish to set an automatic resumption time. For immediate resumption, use the Resume Dunning API endpoint.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Analyse von Nutzungsmustern bei Metered Features

Die neue Usage-Pattern-Analyse visualisiert den Verbrauch von Metered Features pro Kunde, etwa zugewiesene, genutzte und überschrittene Mengen auf Subscription-Ebene, um Spitzen, Einbrüche und Upsell-Chancen zu erkennen.

Track how your customers are using your metered features with the new usage pattern analysis feature. This feature lets you visualize customer consumption trends, helping you detect unusual spikes or drop-offs, identify potential upsell opportunities, and better understand how value is delivered across different segments. This is designed to help you quickly diagnose issues and monitor usage activity during spikes.

Why is this important?

By analyzing how individual customers use specific metered features over time, you gain critical insights into the actual value they derive from your product. This data can directly influence key business strategies. Example Imagine you have a customer on a usage-based plan where they are allocated 1,000 API calls per month. When the support team receives a query about unexpected overage charges, they can go to Customers > Customer Details > Subscriptions and immediately see: - Allocated usage: 1,000 API calls. - Consumed usage: 1,350 API calls. - Overage: 350 API calls. This breakdown at the subscription level helps the team quickly confirm that the customer indeed exceeded their limit and by how much. It also lets them check if similar overages are happening across other subscriptions for the same customer. This insight allows for a faster support resolution with precise usage data. It enables CSMs to proactively suggest plan upgrades if consistent overages are observed and finance teams to validate overage billing without…

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Erweiterte Legal-Agreement-Funktionen im Checkout

Chargebee Checkout unterstützt jetzt mehrere Legal Agreements mit Rich-Text-Formatierung, Anzeige je nach Kundensprache, zeitgestempeltem Einwilligungsnachweis, Audit Trail, Versionierung und einer anpassbaren Notiz vor dem Absenden.

Chargebee Checkout now offers enhanced support for presenting legal agreements during the purchase process, allowing you to add and manage multiple policies. Agreements now support rich text formatting, and are displayed in the language based on customer locale. Moreover, Chargebee records timestamped proof of consent and maintains an audit trail of changes.

Why is this important?

- Multiple agreements: Present all necessary legal agreements—like Terms of Service and Privacy Policy—each with its own consent checkbox, giving customers full visibility and ensuring explicit consent for each one. - Custom styling: Tailor the appearance of your agreements. Highlight key text, format content for readability, and include links to supporting documents. - Localization support: Show agreements in the language based on customer locale. - Consent capture & audit trail: Access timestamped logs for each customer's consent to every agreement, providing a reliable audit trail. - Agreement versioning: View a complete history of changes to each agreement, with the option to restore previous versions. - Custom notes: Share important reminders or information right before purchase with a customizable note above the submit button. - **Seamless migratio…

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Zahlungs-Gateways und -Methoden jetzt allgemein verfügbar

Mehrere Payment Gateways und Zahlungsmethoden, darunter ACH via Adyen, Checkout und BlueSnap, Klarna PayNow via Adyen, Venmo via Braintree, SEPA via BlueSnap, QuickBooks Payments und Global Payments, sind von Beta auf General Availability gewechselt und lassen sich ohne Support direkt in der App aktivieren.

We have moved several payment gateways and payment methods from Beta to General Availability (GA), allowing you to enable them directly from your Chargebee app without contacting support.

Payment methods now GA
Payment gateways now GA

Originalquelle(öffnet in neuem Tab)Problem melden