# December 2025
Chargebee product updates released in December 2025.
Source: https://release-notes.chargebee.com/december-2025
## Introducing Selling Rules: Smarter, Automated Quoting Logic!
Take full control of how quotes are built without risking revenue or relying on manual oversight, using [**Selling Rules in Chargebee CPQ**](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-selling-rules).
### **Why is this important?**
When quotes are created manually, your sales teams may apply discounts or configure deals that don't follow the pricing policies set by the RevOps teams, across geographies or contract types. While these may help capture deals, they can lead to compromised marginal revenue and compliance issues.
Selling Rules in Chargebee CPQ aim to help you prevent this leakage by embedding your pricing and packaging logic directly into CPQ, ensuring every quote set by the sales teams aligns with approved structures automatically.
### **How can you use it?**
[**Selling Rules in Chargebee CPQ**](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-selling-rules) is available upon request. Once you enable the feature, refer to [**how you can create a Selling Rule**](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-selling-rules#creating-a-selling-rule) using quote details, customer attributes, item-level data, or sales context.
## Introducing support for Amazon Pay via Stripe
You can now enable [**Amazon Pay via Stripe**](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/stripe-amazonpay) in Chargebee. This payment method is supported across all major checkout flows, including APIs and the [Self-Serve Portal](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/self-serve-portal).
### **Why is this important?**
You can now offer a fast, secure, and familiar checkout experience by letting customers pay with their Amazon account through the Stripe gateway. This expands your available payment options and can help improve conversion.
### **How can you use it?**
To enable and use Amazon Pay via Stripe in Chargebee, [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 feature for your site:
1. Go to **Settings > Configure Chargebee > Payment Gateway** and select **Stripe**.
2. Enable **Amazon Pay** in the Stripe configuration and click **Apply** to save.
For full setup instructions, refer to [this guide](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/stripe-amazonpay#configure-amazon-pay-via-stripe-in-chargebee).
## Accept Stablecoin payments via Stripe
Chargebee Billing now supports accepting [USDC and USDP](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/stripe-stablecoin#refunds) Stablecoin payments through Stripe. This feature is available in [In-app Checkout](https://www.chargebee.com/checkout-portal-docs/stablecoin-tutorial.html), [Full-page Checkout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout#full-page-layout), and [Chargebee.js](https://www.chargebee.com/checkout-portal-docs/stablecoin-tutorial.html).
### **Why is this important?**
You can now accept Stablecoin payments via Stripe, allowing customers to pay using crypto-backed digital currencies. This provides your business with added flexibility and helps meet the growing demand for alternative payment methods, particularly in regions with limited access to traditional banking.
### **How can you use it?**
To use this feature, you'll need a Stripe account with crypto payments enabled. Once [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) enables the feature for your site, you can:
1. Enable **Stablecoin** in your Stripe gateway settings in Chargebee.
2. Optionally, enable **Smart Routing** to automatically route USD payments to Stablecoins where applicable.
## Invoice API now provides dunning engine details
Identify the **retry engine** behind dunning via the [Invoice API](https://apidocs.chargebee.com/docs/api/invoices#invoice_dunning_attempts_retry_engine). Your systems and reporting tools can now retrieve the `retry_engine` field for each invoice to track which retry engine handled the dunning.
Use the following details to segment and analyze dunning outcomes by retry engine:
\- **Field**: `retry_engine`
\- **Description**: Indicates which retry engine handled the invoice's dunning
\- **Values**: `chargebee`, `flexpay`, `success+`
### **Why is this important?**
You can now see whether Chargebee, FlexPay, or Success+ handled dunning for each invoice. This provides clearer visibility into dunning performance, helps attribute recovered or failed payments accurately, and supports better decision-making when comparing retry strategies.
### **How can you use it?**
No additional setup is required. The `retry_engine` field is now available in the Invoice API and will be included in API responses automatically.
## Error Intelligence now supported in all Checkout flows
[**Error Intelligence**](https://www.chargebee.com/docs/payments/2.0/payment-errors/payment-errors) messages are now extended to [Full-page Checkout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout#full-page-layout) and [Payment Components](https://www.chargebee.com/checkout-portal-docs/payment-components.html). They were previously only supported in [In-app Checkout](https://www.chargebee.com/checkout-portal-docs/stablecoin-tutorial.html).
### **Why is this important?**
Error Intelligence messages were already available in other parts of the Chargebee interface, allowing you to customize and control the error messages displayed to customers. With this enhancement, the same support is now extended to Checkout flows, including [Full-page Checkout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout#full-page-layout) and [Payment Components](https://www.chargebee.com/checkout-portal-docs/payment-components.html). This ensures consistent error handling across all customer-facing touch points.
### **How can you use it?**
The enhancement is enabled by default. Your existing Error Intelligence configurations will now apply automatically to Full-page Checkout and Payment Components, in addition to In-app Checkout.
## Support for BGN to EUR currency migration
Support for [**Bulgarian Lev (BGN) to Euro (EUR) currency migration**](https://www.chargebee.com/docs/billing/2.0/kb/site-configuration/transitioning-from-BGN-to-EUR) is now available in chargebacks and refunds.
### **Why is this important?**
With the deprecation of the BGN currency and migration to the EUR, Chargebee now supports workflows that involve chargeback and refund operations in both currencies. This ensures accurate processing even when the source transaction and refund currencies differ.
### **How can you use it?**
To stay compliant with Bulgaria's transition to the EUR from January 1, 2026, ensure you:
\- **Update your price points** by creating equivalent EUR price points for all your BGN-based products.
\- **Migrate active BGN subscriptions** to EUR using Chargebee's cancellation and re-subscription flow or via the API.
\- **Review open invoices and unbilled charges** in BGN and close or transition them before December 30, 2025.
\- **Handle any BGN credit notes** before the deadline, as they can't be applied after the switch.
Refer to the [BGN to EUR migration guide](https://www.chargebee.com/docs/billing/2.0/kb/site-configuration/transitioning-from-BGN-to-EUR) for detailed steps and timelines.
## Refined `payment_initiated` and `payment_failed` event behavior
Chargebee has updated the behavior of the `payment_initiated` and `payment_failed` events to provide clearer visibility into payment attempts. These changes ensure events reflect the actual state of a transaction and include relevant context:
\- **`payment_initiated`** is now triggered for all payment attempts, including those that enter a `needs_attention` state (e.g., timeouts, authorization issues).
\- **`payment_failed`** is triggered only when an attempt fails or moves to `needs_attention`, and is not triggered for successful or in-progress attempts.
\- Event payloads now include the **invoice entity** if linked to the payment; otherwise, the event is still triggered without it.
### **Why is this important?**
This enhancement provides more accurate, real-time insights into payment behavior. It helps your team identify failed or stalled payment attempts sooner, enabling quicker follow-up and better tracking of the customer payment journey.
### **How can you use it?**
No action is needed on your part. These updated events will automatically reflect in your existing webhooks or event listeners.
## Apple Pay now requires shipping address in Checkout
Chargebee Checkout now collects shipping addresses for Apple Pay transactions in compliance with Apple's updated requirements. This ensures compatibility with Apple's latest processing policies.
### **Why is this important?**
To comply with Apple's updated policies, Apple Pay transactions now require the collection of the shipping address. Without this, transactions may fail or be rejected by Apple during checkout.
### **How can you use it?**
When a customer selects Apple Pay during Checkout, Chargebee will now automatically request their shipping address. No additional configuration is required on your end, ensuring your Apple Pay integration remains compliant and functional.
## Skip tax calculations for third-party providers
You can now skip exclusive tax calculations in the [Subscription Renewal Estimate API](https://apidocs.chargebee.com/docs/api/estimates?lang=curl#subscription_renewal_estimate_exclude_tax_type) when using third-party tax providers, by adding the **`exclude_tax_type`** parameter.
### **Why is this important?**
Previously, taxes were calculated by default in [Subscription Renewal Estimate](https://apidocs.chargebee.com/docs/api/estimates?lang=curl#subscription_renewal_estimate_exclude_tax_type) API responses. This contributed to additional charges from third-party tax providers. You can now manage and potentially reduce those external costs.
### **How can you use it?**
Pass the **`exclude_tax_type=exclusive parameter`** in [Subscription Renewal Estimate](https://apidocs.chargebee.com/docs/api/estimates?lang=curl#subscription_renewal_estimate_exclude_tax_type) API calls to skip exclusive tax calculations, but only when your tax configuration uses a third-party provider. If no value or **`none`** is passed, taxes are calculated as usual. This feature is limited to exclusive tax types and will be ignored for inclusive tax setups or non-third-party providers.
## Notify customers on subscription cancellation and reversal
You can now automatically send email notifications when a subscription cancellation is scheduled and when a previously scheduled cancellation is removed, ensuring customers are informed at key moments in the subscription lifecycle.
### **Why is this important?**
This helps you meet regulatory requirements such as the [UK Digital Markets, Competition and Consumers Act 2024](https://www.legislation.gov.uk/ukpga/2024/13/contents), by providing clear acknowledgment of cancellation requests. Customers receive confirmation that includes the effective cancellation date and any applicable refund details, which reduces ambiguity and builds trust while supporting your compliance and audit needs.
### **How can you use it?**
Follow these steps to configure the email notifications in your Chargebee Billing site:
1. Navigate to **Settings** > **Configure Chargebee** > **Email Notifications** > **Customer Retention** > **Subscription Cancellation**.
2. [Enable the email notifications](https://www.chargebee.com/docs/billing/2.0/customers/email-notifications-list#customer-retention) **On cancellation scheduled** and **On scheduled cancellation removed**.
When enabled, Chargebee sends automatic emails acknowledging cancellation requests with the effective date and refund information. If the customer later decides to continue the subscription, a follow-up email confirms that the scheduled cancellation has been successfully removed.
## Backdate subscription changes beyond the current term
You can now generate an estimate and [backdate a subscription change](https://www.chargebee.com/docs/billing/2.0/subscriptions/subscriptions-actions-backdating) beyond the current term in the past. For instance, you can upgrade a subscription beyond the current term, allowing you to move the subscription to a new plan starting from the original subscription start date, even if multiple renewal cycles have already been billed.
### **Why is this important?**
If your business follows a sales-led growth model, contract negotiations often take place over several months while the customer continues on an existing monthly plan. During this time, the subscription may renew multiple times at the old price before the new terms are finalized, making it challenging to apply the agreed changes correctly.
For example, a customer starts on a monthly plan in January. In February, discussions begin to upgrade them to a higher plan with revised pricing, effective from the original subscription start date. However, the negotiations conclude only in May, after several monthly renewals have already been billed. Without the ability to backdate changes beyond the current term, you would need to issue manual credits or adjustments to account for the difference.
### **How can you use it?**
To backdate a subscription change in your Chargebee Billing site, follow these steps:
1. Select the subscription record you want to change to open the details page.
2. Click **Edit Subscription** and make the necessary changes.
3. In the **Apply Changes** section, select **On a specific date** and choose a date from the past to specify when the changes should be applied. Click **Apply**.
## Fixed PayPal icon issue in dark mode
Fixed blurry PayPal icon display in dark mode.
The PayPal payment method icon now displays correctly in dark mode when using Payment Components. Previously, the icon appeared blurry or unclear against dark-themed backgrounds. This fix ensures better visual consistency for customers using dark mode, helping maintain trust and professionalism in the checkout experience.
## Improved coupon application for subscriptions with multiple plans
You can now confidently use coupons with subscriptions that include multiple plans. We fixed an issue where eligible coupons were not displayed for selection and were not applied correctly in subscription estimates. With this update, coupon availability is accurately displayed and discounts are correctly calculated across all applicable plans in a subscription.
## Syncs now pause automatically on token invalidation
A reauthorization flow has been introduced to handle expired HubSpot tokens for Chargebee integrations.
Previously, if a Chargebee app was uninstalled from a HubSpot portal, the associated refresh token would become invalid without the Chargebee integration being aware. This caused repeated sync failures. Now, this fix ensures that Chargebee detects the invalid token, stops further sync attempts, and waits for you to reconnect the integration.
This will be a backend operation. If token invalidation is detected, all forward and backward syncs are paused. You'll see a banner on the integration dashboard prompting you to reauthorize the connection. Once you complete the reauth flow, the setup resumes from where it stopped ensuring minimal disruption.
## Checkout no longer shows non-actionable edit order option
When you create an [in-app layout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout#in-app-layout) Checkout session to update an existing subscription, customers sometimes saw an **Edit order** option even if you had [configured](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/configure-fullpage-fieldslabels#edit-a-field-name) Checkout to prevent any changes. Clicking **Edit order** led customers to an empty screen with nothing they could modify, which could cause confusion and drop-offs. This has now been corrected.
## Offline checkout works as expected with overrides
When setting [`allow_offline_payment_methods`](https://apidocs.chargebee.com/docs/api/hosted_pages#create_checkout_for_a_new_subscription_allow_offline_payment_methods) to `true` while creating Checkout sessions, some checkouts could still fail at submission even after the customer selected an offline option. This issue occurred when the parameter was passed but [**Allow customers to use offline payment methods**](https://www.chargebee.com/docs/payments/2.0/offline-checkout/offline_payments#on-the-checkout) setting was disabled, resulting in errors such as "*data not formatted properly*" or "*there is no card on file*". This has now been fixed. Checkout consistently respects the parameter value as an override, regardless of the site setting.