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

Refersion-Integration jetzt auf PC2.0-Sites unterstützt

Die Refersion-Integration steht nun für alle Chargebee-Billing-Sites mit Product Catalog 2.0 zur Verfügung, um Affiliate-Programme zu verwalten.

The Refersion integration is now supported for all Chargebee Billing sites on Product Catalog 2.0, allowing you to effortlessly connect Chargebee with Refersion to manage affiliate programs.

Why is this important?

With this integration, you can easily track and pay affiliate commissions without relying on manual processes. It reduces the risk of errors, improves accuracy, and helps you build stronger relationships with your affiliates.

How can you use it?

You must first set up your Refersion account for the integration, and then connect the account with your Chargebee Billing site.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Breaking Change: Neues Temporary-Token-Format für Stripe

Für Stripe SEPA, iDEAL und Bancontact werden in Temporary Tokens ab dem 31. März nur noch Payment-Method-Tokens akzeptiert, Source Tokens nicht mehr.

Chargebee has updated the temporary token format for Stripe SEPA, iDEAL, and Bancontact to comply with Stripe's deprecation of source tokens and the Charges API. Starting March 31, only payment method tokens will be supported in temporary tokens, and source tokens will no longer be accepted.

Why is this important?

This change aligns with Stripe's updated standards and ensures compatibility with their latest API requirements. It helps maintain the reliability and efficiency of your payment processing system.

How can you use it?

Ensure that your systems are updated to use payment method tokens instead of source tokens in temporary tokens before March 31 to avoid disruptions in payment processing. If you have any questions or need assistance, contact Chargebee Support.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Retry-Limit für Direct-Debit-Dunning einstellbar

In den Dunning-Einstellungen lässt sich über die Option 'Retry limit' die Anzahl der Wiederholungsversuche für Direct-Debit-Zahlungen zwischen 2 und 12 festlegen.

Merchants can now adjust the retry limit for Direct Debit dunning attempts using a user-friendly interface under the Dunning settings. This feature lets you set a retry limit between 2 and 12 attempts.

Why is this important?

Failed Direct Debit transactions can disrupt cash flow and impact revenue. The flexibility to configure retry attempts improves payment recovery chances, allowing you to manage payment collections more effectively while providing customers with additional opportunities to complete their payments.

How can you use it?

Enable the Retry limit option under your Dunning settings. Once activated, you can access the settings and configure the retry limit. Learn more

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Verbesserte Währungskursbehandlung in NetSuite

Die Einstellung Currency Exchange Rate in NetSuite funktioniert nun vollständig, da UI und Backend übereinstimmen und keine zusätzlichen Konfigurationen mehr nötig sind.

The Currency Exchange Rate setting in NetSuite is now fully functional, with UI and backend implementations aligned.

Why is this important?

Previously, mismatched UI and backend implementations required additional L2 configurations to handle currency exchange rates, leading to inefficiencies. This resolution ensures accurate currency handling and reduces manual intervention, providing a more reliable experience.

How can you use it?

With this fix, currency exchange rates in NetSuite are now handled accurately based on updated Advanced Sync Rules.This eliminates the need for additional configurations, ensuring a smooth and consistent process during synchronization.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Zahlungsbedingungen von Chargebee nach Intacct synchronisieren

Chargebee synchronisiert Zahlungsbedingungen nun direkt nach Intacct, indem es AR-Terms zwischenspeichert und bei Bedarf neue Terms im Format 'CB - Net' anlegt.

Chargebee now supports syncing payment terms directly to Intacct, improving the efficiency of handling due dates during invoice creation.

Why is this important?

This feature automates the process of managing payment terms in Intacct, reducing manual effort and ensuring accurate invoicing. By leveraging cached AR terms and dynamically creating new terms as needed, you can maintain consistency and avoid errors.

How can you use it?

When sync for due dates is enabled, Chargebee fetches all AR terms at the start of the sync and stores them in a cache. During Sales Order (SO) or AR invoice creation, Chargebee checks the cache for the applicable payment term. If found, the term is applied; if not, a new term in the format CB - Net is created, cached, and synced to Intacct. For invoices with 0 net term days, only the due date is synced as part of the regular flow.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Receivables Aging by Customer im Reports Explorer als Pivot-Ansicht

Im Reports Explorer lässt sich der Receivables-Aging-Bericht nach Kunde jetzt als Pivot-Ansicht mit Aufteilung nach Aging-Buckets herunterladen.

You can now download the Receivables Aging Report by Customer in a pivoted view. You can view the aging at a customer level, segregated by the aging buckets, clearly outlining the different aging buckets a customer has and how much is due in each bucket in the Reports Explorer.

Why is this important?

This enhancement groups aging information by customer and aging buckets, making it easier to track the amount due for each customer. Financial controllers can now access more detailed insights, saving time and improving the accuracy of their receivables tracking.

How can you use it?

Navigate to the Reports Explorer and you will now be able to download this pivoted view from the Receivables Aging by Customer (Pivoted) report.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Checkout: Full-page-Layout ist Standard für neue Sites

Für alle neuen Sites ist das Full-page-Layout mit einstufigem Checkout nun der Standard, wobei jederzeit zum In-app-Layout zurückgewechselt werden kann.

The full-page layout is now the default checkout experience for all new sites. Designed for flexibility and customization, this layout offers a single-step checkout process, making it easier for your customers to complete their purchases. If you prefer the in-app layout, you can switch back at any time.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Hinweis und hervorgehobener Regionswechsel-Link auf der Chargebee-Login-Seite

Wer sich in einer Region ohne eigene Sites anmeldet, sieht nun eine Meldung, und der Link zum Regionswechsel auf der Login-Seite wird hervorgehoben.

When a user attempts to log in to a Chargebee region that differs from the region where they originally signed up, and if they have no sites in the current region, the login will be restricted and the user will see a clear message informing them of the issue.

For example, if a user logs into the US region but has no sites in that region, they will see the message: No sites available in the US region. Please switch to a different region.

Additionally, the region switch link on the Chargebee login page will be prominently highlighted to guide the user to the correct region.

Why is this important?

This enhancement ensures users are informed when they try to log in to an incorrect region, preventing them from being directed to an empty Sites or Select page. Such situations often lead to confusion, as users may mistakenly believe that their site is inaccessible. By proactively guiding users to the correct region, we aim to improve the user experience and reduce unnecessary support requests.

How can you use it?

This feature will help when you have signed up for a Chargebee account by making it easier to navigate between regions and access your sites.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Fix: MasterCard-BIN-Fehler im Checkout behoben

MasterCard-Kreditkarten mit BIN 223444 werden auf der Checkout-Seite nicht mehr fälschlich als ungültig markiert.

We've resolved an issue where MasterCard credit cards starting with BINs 223444 were incorrectly flagged as invalid on the checkout page. With this fix, transactions using these BINs will no longer trigger the invalid credit card error, allowing for successful payments.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Fraud-Monitoring-E-Mails ohne Einschränkungen aktivierbar

Händler, die nur Adyen nutzen, können Fraud-Monitoring-E-Mails in den Chargebee-Notifications-Einstellungen nun aktivieren.

We've fixed a bug that prevented merchants using only Adyen from enabling fraud monitoring emails in Chargebee Notifications settings. You can now activate fraud monitoring emails without any issues, ensuring you stay informed about potential fraudulent activity.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Checkout: Korrekter Sitzungsstatus bei Redirects

Der state-Parameter in Checkout-Redirects zeigt beim Full-page-Layout nach abgeschlossener Sitzung nicht mehr fälschlich „requested“, sondern den korrekten Status.

We have fixed an issue where the state query parameter in Chargebee Checkout redirects sometimes displayed requested instead of successful after a completed checkout session using the full-page layout. With this update, you can now trust that the state parameter accurately reflects the session's status, enabling you to reliably process post-checkout workflows.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Customer Portal: Pläne in definierter Reihenfolge mit fetchAllowedPlanConfig()

Im Self-Serve Portal werden Pläne bei Verwendung von Custom Code nun in der mit fetchAllowedPlanConfig() festgelegten Reihenfolge statt zufällig angezeigt.

You now have more control over how plans are displayed in the Self-Serve Portal when using the custom code. Previously, the list of plans appeared in a random order, which could lead to confusion for your users. With this update, the plans will follow the precise order specified in .

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Fix: Reaktivierung gekündigter Subscriptions

Subscriptions lassen sich aus dem Status „Cancelled“ nun auch bei erforderlichem Backdating reaktivieren, und die Option „Reactivate“ ist für alle Sites sichtbar.

We've resolved an issue where reactivating a subscription from the 'Cancelled' state was failing due to a change date incompatibility with the plan terms. The issue was related to backdating, which wasn't working correctly when attempting to reactivate a subscription via the 'Edit Subscription' page. Additionally, the 'Reactivate' option was not visible for sites without multi-business entity enabled. With this fix, you can now reactivate subscriptions from the cancelled state without encountering issues, even when backdating is required, and the option will be available for all sites.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Fix: Tiers oberhalb von 101000 können angelegt werden

Beim gestaffelten Pricing lassen sich Tiers über dem Wert 101000 nun ohne Fehler und fehlende Tier-Informationen erstellen.

We've resolved an issue where tier information was missing when attempting to create tiers above the 101000 value range. This error occurred because the system was not accepting values beyond the specified range for tiered pricing. With this fix, you can now create tiers without encountering errors, ensuring that your tiered pricing setup functions as expected for higher-value ranges.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Checkout: Bank-Transfer-Beschreibung wird korrekt dargestellt

Die Beschreibung des Bank-Transfer-Labels im Checkout wird nicht mehr als roher HTML-Code angezeigt, sondern korrekt gerendert.

We've fixed an issue in the checkout experience where the Bank Transfer description label displayed raw HTML for some sites, instead of rendering it properly.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Indische Steuerregistrierung ohne Abhängigkeiten konfigurierbar

Eine indische Steuerregistrierungsnummer kann nun unabhängig von anderen Ländern mit CSV-Steuermodell hinzugefügt werden, sofern manuelle Steuern für Indien aktiviert sind.

Previously, configuring any country with the CSV tax model prevented you from adding an Indian tax registration number. This issue has now been resolved, ensuring that you can add Indian tax registration numbers without dependencies on other countries' configurations. The only requirement is that manual taxes must be enabled for India.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Quick Charge zeigt nur passende Steueranbieter

Bei Quick Charge werden Steueranbieter wie Vertex und Taxamo nur noch angezeigt, wenn sie im Account konfiguriert sind.

We've improved the Quick Charge experience by ensuring the tax provider options displayed align with your enabled integrations. Previously, tax providers like Vertex and Taxamo were visible by default, even without active integrations. This update eliminates confusion by showing these options only when they are configured in your account.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Überarbeitete Beschriftung bei Tax Providers

In den Third-Party Sync Invoice Preferences der Tax Providers heißt die Aktion im Dropdown nun „Commit“ statt „Sync“.

We've updated the copy changes in the Tax Providers > Third-Party Sync Invoice Preferences UI to enhance clarity. The actions previously labeled as Sync in the drop-down now correctly display as Commit, ensuring better alignment with its purpose.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Price-Type-Override-Feld mit Dropdown-Auswahl

Statt TAX_INCLUSIVE oder TAX_EXCLUSIVE manuell einzutippen, wählt man den Preistyp im Override-Feld für Kunden nun per Dropdown aus.

You no longer need to manually type TAX_INCLUSIVE or TAX_EXCLUSIVE into the price type override field for customers. We've replaced the text box with a dropdown menu, letting you select the desired price type with just a click.

Originalquelle(öffnet in neuem Tab)Problem melden

Chargebee

Fix: Custom-Field-Werte bei Price-Type-Override wieder vorhanden

Beim Anlegen von Kunden über die Oberfläche fehlen bei aktiviertem Price-Type-Override die Custom Fields für SPI-basierte Tax Provider nicht mehr.

We've resolved an issue occurring during the customer creation process via the user interface (UI) where enabling the price type override prevented custom fields for tax providers. The issue only impacted workflows relying on UI interactions when using SPI-based tax providers.

Originalquelle(öffnet in neuem Tab)Problem melden