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

Standortvalidierung mit Taxamo bei Karten- und Rechnungsdaten

Die APIs zum Hinzufügen und Aktualisieren von Karten sowie zum Aktualisieren der Billing-Informationen prüfen den Standort nun per Taxamo anhand aller verfügbaren Standortnachweise für eine genauere Steuerberechnung.

We've enhanced the API's for adding and updating cards, as well as updating billing information, by introducing location validation with Taxamo. This ensures accurate tax calculation by verifying all available location evidence, helping you stay compliant and improve the billing accuracy.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Neuer Filter für Abonnements mit Ramps

Auf der Subscriptions-Listenseite lassen sich Abonnements nun nach geplanten Ramps filtern, was Export, Massen-E-Mails und Berichte zu diesen Abonnements erleichtert.

We've introduced a new feature that allows you to filter subscriptions based on scheduled ramps directly from the Subscriptions list page. This enhancement enables you to efficiently manage and export subscriptions with ramps, making it easier to execute bulk emails and reports related to these specific subscriptions.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Pricing Table: dynamische Rabatte auf Item-Ebene per API

Über die Chargebee-API lassen sich in Pricing Tables dynamische Rabatte als Festbetrag oder Prozentsatz auf Item-Price-Ebene anwenden und mit eigenen Rabatthinweisen anzeigen, auch aus externen Offer Engines.

You can now enhance your pricing tables by applying dynamic discounts directly through the Chargebee API. This feature allows you to offer fixed amount or percentage-based discounts at the item price level, display custom discount messages, and tailor promotions to specific plans or your entire catalog. By integrating discounts generated within Chargebee or from external offer engines, you ensure a consistent experience for your customers—from browsing your pricing page to completing checkout and receiving invoices.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Adressvalidierung jetzt auf Entity-Ebene möglich

Die Funktion „Validate Existing Address“ kann für Drittanbieter-Steuerdienste nun auf Entity-Ebene statt nur für die gesamte Site ausgeführt werden.

You can now run the Validate Existing Address feature at the entity level for third-party tax providers. Previously, this feature was available only at the site level, which meant validating addresses for all entities at once. By allowing you to validate addresses within a specific entity, it ensures your subscriptions remain active without the risk of unnecessary costs due to address validation across unrelated entities.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

E-Invoicing-Daten im Checkout bei Neukunden erfassen

Der Full Page Checkout zeigt im Rechnungsadressbereich nun je nach Land des Kunden und E-Invoicing-Einstellungen ein Feld für den Entity Identifier, sodass Kennungen und USt-Nummern erfasst und der Customer ID zugeordnet werden.

You can effortlessly collect e-invoicing details from new customers during the checkout process. Our Full Page Checkout now includes the entity identifier field in the billing address section, displayed based on the customer's country and your e-invoicing settings. This means you can capture essential entity identifiers and VAT numbers independently, ensuring compliance with regional invoicing regulations. The collected information is mapped to the customer ID, streamlining your billing process and providing a smoother checkout experience for your customers.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Kunden-Onboarding auf bestimmte Regionen beschränken

Im Checkout lässt sich das Onboarding nun über Einschränkungen von Rechnungs- und Lieferadressen nach Land, Bundesstaat oder Postleitzahl auf bestimmte Regionen begrenzen.

Now, you can control where your customers come from by restricting onboarding to specific regions through Checkout. You can set limitations on billing and shipping addresses by country, state, or zip code. This means you only onboard customers from areas where you provide services, helping you avoid potential service issues, comply with regional policies, and focus on your target markets more effectively.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Adyen-API-Endpunkte auf Checkout API v69 aktualisiert

Chargebee nutzt für die Adyen-Abläufe Capture, Refund, Cancel und Void jetzt die Checkout API v69 statt der API-Version v52, was laut Text Leistung, Sicherheit und Kompatibilität verbessert.

We have upgraded the Adyen API endpoints for the Capture, Refund, Cancel, and Void flows, transitioning from the API version v52 to the latest Checkout API version v69. This update ensures improved performance, better security, and enhanced compatibility with Adyen's latest features, allowing you to process payments more efficiently.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Neuer Button „View Error Log“ auf der Sync Overview Page

Auf der Sync Overview Page gibt es einen neuen Button „View Error Log“, der nur Synchronisierungsfehler filtert und anzeigt.

We are excited to announce the introduction of a new View Error Log button on the Sync Overview Page. This feature filters and displays only sync errors. With this enhancement, you can streamline your troubleshooting efforts, improve efficiency, and ensure a smoother integration experience.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Unterstützung für neues Entity Mapping in Manage Entities

Im Bereich „Manage Entities“ lassen sich jetzt weitere Entitäten mit bestehenden Integrationen verbinden.

We are thrilled to introduce support for new entity mapping in the Manage Entities section of your Chargebee account. This enhancement allows you to seamlessly connect additional entities within your existing integrations, giving you greater flexibility and control over your billing processes. With this update, you can now ensure that all your entities are accurately represented and efficiently managed, streamlining your operations and improving your overall workflow.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Entitlements API validiert Pfadparameter

Für die Endpunkte der Entitlements API werden Pfadparameter jetzt vorab validiert, sodass Probleme früh erkannt werden und API-Aufrufe zuverlässiger funktionieren.

To help you prevent unexpected API call failures, we've added validations to the path parameters for the Entitlements API endpoints. This enhancement means any issues with your path parameters are caught upfront, making your API integration more reliable.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Rechnungsadress-Parameter für SEPA-Zahlungen via Stripe in Chargebee.js

Ein Fehler bei SEPA-Payment-Intents über Stripe in Chargebee.js, verursacht durch einen fehlenden Ländercode, wurde behoben, indem Rechnungsadress-Parameter nun übergeben werden können.

We have resolved an issue when creating SEPA payment intents via Stripe using Chargebee.js. Previously, a missing country code parameter caused errors during payment processing. To fix this, we have added support for passing billing address-related parameters in Chargebee.js. This update ensures smoother SEPA payment processing and reduces errors, allowing you to provide a more seamless checkout experience for your customers.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Unerwartete Abbuchungen bei zukünftigen Subscriptions behoben

Ein Fehler, durch den zukünftige Subscriptions nach der Umplanung einer Vorab-Rechnung wegen angesammelter Tage unerwartet belastet wurden, ist behoben; bei inaktiven Subscriptions wird nun die korrekte Referenz verwendet.

We've addressed an issue where future subscriptions were being charged unexpectedly due to the accumulation of days when an advance invoice was rescheduled. Now, if a subscription is inactive, the system will correctly reference the instead of the , ensuring accurate billing and preventing unexpected charges. This improvement helps you maintain better control over your billing cycles.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

E-Invoice-Fehler bei Prepaid-Beträgen in Gutschriften behoben

E-Invoices schlagen nicht mehr fehl, weil der Prepaid-Betrag in Gutschriften nun mit dem korrekten Vorzeichen gesendet wird, was Peppol-Standards entspricht.

We've fixed an issue that caused e-invoices failures due to incorrect handling of prepaid amounts in credit notes. Previously, the prepaid amount was sent with the wrong sign, leading to validation errors. Now, e-invoices process successfully with the correct prepaid amount, ensuring smooth transactions and compliance with Peppol standards.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

E-Invoice-Rundungsfehler behoben

E-Invoices schlagen nicht mehr wegen Rundungsfehlern bei der Berechnung von Artikelpreisen ohne MwSt. in steuerinklusiver Währung und Regionspreisen fehl.

We've fixed an issue where e-invoices were failing due to rounding errors when calculating item prices excluding VAT in tax-inclusive currency and region pricing. Now, your e-invoices will be processed smoothly, ensuring accurate pricing and compliance with tax requirements.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Klarere Sync-Logs für gelöschte Datensätze

Sync-Logs behandeln gelöschte Datensätze nun genauer: Ist ein Datensatz in Chargebee und im Drittsystem gelöscht, gilt das als Erfolg, ist er nur in Chargebee gelöscht, gilt es als Fehler mit Hinweis auf manuelle Bearbeitung.

We've improved the way Chargebee handles sync logs for deleted records, giving you clearer insights into any sync issues. Now, when a record is deleted in both Chargebee and a third party system, it is considered a success with the error message: 'Resource is deleted in Chargebee as well as in the third-party system.' If a record is deleted in Chargebee but not in a third party system, it is considered as failed with the error message: 'Resource is deleted at Chargebee, but not deleted in Third Party System. Please process it manually.' This update helps you quickly address any sync discrepancies and ensures more accurate data management across platforms.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Entitlements per API auf Kundenebene abrufbar

Entitlements lassen sich jetzt per API auch auf Kundenebene statt nur auf Subscription-Ebene abrufen, wobei die Aktivierung über den Chargebee Support erfolgt.

You can now retrieve entitlements at the customer level via our API. Previously, entitlements were only available at the subscription level. This update simplifies provisioning for customers with multiple subscriptions, enabling you to manage and track entitlements more efficiently across all subscriptions tied to a customer. This is especially beneficial for companies managing multiple products. To use this feature contact Chargebee Support.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Product Bundling (Early Access) in Chargebee Billing

Mit Product Bundling können Plans, Addons und Charges aus verschiedenen Product Families zu einem Bundle zusammengefasst werden, wobei Kunden nur die Bundle-Position sehen; die Funktion ist im Early Access und muss angefragt werden.

With Product Bundling in Chargebee Billing, you can now combine multiple items such as plans, addons, and charges from different product families - into a single, streamlined offering. This feature not only simplifies your invoicing and quoting process by displaying just the bundle line item to your customers but also helps you cross-sell products more effectively across various product families. By using bundles, you can boost sales, enhance revenue reporting accuracy, and optimize resource management, leading to more informed business decisions. Refer to product bundling API capabilities like bundle_items and bundle_configuration as well.

Note: Product Bundling is in early access. Submit a request to enable this feature.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Verwaltung von Dangling und Needs Attention Transactions

Neue Funktion zur Erkennung und Klärung von Transaktionsabweichungen, mit automatischem Abgleich und Hinweisen zu Transaktionen, die Aufmerksamkeit brauchen, damit Gateway-Zahlungen korrekt in Chargebee abgebildet werden.

We are excited to introduce the new Dangling and Needs Attention Transactions management feature in Chargebee. This offering streamlines the identification and resolution of transaction discrepancies, ensuring that payments processed by the gateway are accurately reflected in Chargebee. With automatic reconciliation and timely alerts for transactions needing attention, you can reduce manual intervention, improve billing accuracy, and enhance customer trust by providing a seamless payment experience. This feature helps ensure that your financial records are precise and up-to-date, benefiting both you and your customers.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Salesforce 1.62: Eigene Abrechnungsfrequenzen pro Position

Im Salesforce-Package 1.62 lassen sich für jede Position eigene Abrechnungsfrequenzen festlegen, sodass Chargebee entsprechend separate Rechnungen erzeugt.

Now, using Salesforce , you can set unique billing frequencies for each line item, allowing Chargebee to generate separate invoices based on these frequencies. This offers you greater flexibility in managing diverse billing schedules, ensuring that your invoicing aligns seamlessly with your customers' needs.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Salesforce 1.62: Flexiblere Trials und Kündigungen

In Salesforce 1.62 können Trials und Kündigungen rückdatiert oder für die Zukunft geplant werden, und „Apply Next Changes“ lässt sich über Access Controls steuern.

You can now backdate or schedule trials and cancellations for future dates in Salesforce, giving you greater control and precision in managing customer journeys. Additionally, the Apply Next Changes feature is now manageable through Access Controls, ensuring only authorized team members can make significant changes, improving your workflow efficiency and security.

Originalquelle(öffnet in neuem Tab)Problem melden