# February 2026
Chargebee product updates released in February 2026.
Source: https://release-notes.chargebee.com/february-2026
## Paystack gateway and ACH via Checkout.com now generally available
The [Paystack](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/paystack) payment gateway and [ACH payments via Checkout.com](https://www.chargebee.com/docs/payments/2.0/payment-gateways-and-configuration/checkout-ach) 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](https://app.chargebee.com/login).
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.
## Migrate from UPI Collect to UPI Intent for Razorpay
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](https://www.chargebee.com/checkout-portal-docs/upi-tutorial.html) to set up the UPI Intent flow for Razorpay.
When calling [**handlePayment()**](https://www.chargebee.com/checkout-portal-docs/upi-tutorial.html), 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 [**`fetchUpiInstalledAppList()`**](https://www.chargebee.com/checkout-portal-docs/payment-handler-api-ref.html#fetchupiinstalledapplist) function to retrieve the list of supported UPI apps.
## Prevent deletion of the last saved payment method
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](https://app.chargebee.com/login), [Self-serve Portal](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/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](https://app.chargebee.com/login).
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.
## Set custom renewal dates when creating a subscription
You can now set the **Next Renewal Date** during [subscription creation](https://www.chargebee.com/docs/billing/2.0/subscriptions/subscriptions#creating-a-subscription). This lets you control when the subscription renews for the first time.
### **Why is this important?**
Manually adjusting renewal dates after a subscription is live can be a challenge. This update makes sure your invoices are generated in line with your intended schedule.
\- Contract Alignment: Match billing cycles to specific contract terms or commercial agreements.
\- Backdated Starts: Align billing for services that began before the data was entered.
\- Migrations: Maintain existing billing schedules when moving customers from other platforms.
### **How can you use it?**
Follow these steps to enable the capability:
1. Log in to your [Chargebee Billing site](https://app.chargebee.com/login).
2. Go to **Settings** > **Configure Chargebee** > **Billing LogIQ** > **Billing & Invoices** > **Calendar Billing** and click **Enable**.
3. Enable the toggle **On** under **Enable next renewal date at subscription creation** option.
4. After configuring your preferred Calendar Billing settings, click **Apply** > **Confirm** to save your updates.
While creating a new subscription, the **Next Renewal On** field is set to Default, which is based on the plan frequency or calendar billing setting. Click the dropdown and choose a desired date. Chargebee Billing uses this date to determine the upcoming billing cycle, allowing you to configure renewal timing in line with your business requirements.
## Advance invoices on Quote Form Builder
Quote Forms in [Quote Form Builder](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq-quote-form-builder) now include an Advance Invoices option. This option is designed to help your sales team generate invoices upfront and collect advance payments from customers before the product or service is delivered.
### **Why is this important?**
When your sales team can control invoice generation at the quote stage, it results in: - **Better clarity around billing periods**, so customers clearly understand what they are paying for. - **A smoother quote-to-cash process**, by aligning invoicing with the quote's billing terms. - **Faster collections**, since collecting payments upfront helps reduce delays.
### **How can you use it?**
1. Log in to your [Chargebee Billing site](https://app.chargebee.com/login). 2. Go to **Settings** > **Configure Chargebee** > **CPQ** > **Billing and Terms**. 3. Enable the option **Generate Advance Invoices** while configuring billing terms in the quote form. Once enabled, Chargebee automatically displays the corresponding invoice period (start date to end date). During checkout, customers can view the invoiced items along with the applicable dates. image_path: "quote.png"
## Dutch translation for metered addons now reflected in quotes
We've enhanced Chargebee CPQ to extend language pack support to [metered addons](https://www.chargebee.com/docs/billing/2.0/usage-based-billing/metered_billing#defining-plans-addons-as-metered-components) in quotes. Previously, translations from the CSV language pack were applied only to non-metered addons, while metered addons continued to display the default English label.
### **Why is this important?**
If you operate in multiple languages, accurate translations in quotes help you present a consistent buying experience and reduce confusion for customers. This fix ensures that metered addons display the correct localized labels, helping you maintain brand consistency and avoid manual workarounds.
### **How can you use it?**
To apply translations for addons, continue updating the relevant entries in your CSV [language pack](https://www.chargebee.com/docs/billing/2.0/customers/configure-multiple-languages#language-pack) and upload them to your site. Translations for both metered and non-metered addons will now reflect correctly in newly created quotes based on the customer's preferred language.
## Define contract term behavior from pricing tables
You can now pass [contract term](https://apidocs.chargebee.com/docs/api/contract_terms) details directly through the [Pricing Table Sessions API](https://apidocs.chargebee.com/docs/api/pricing_page_sessions). This update introduces two new input parameters `contract_term[action_at_term_end]` and `contract_term[cancellation_cutoff_period]`.
### **Why is this important?**
This enhancement lets you define contract term renewal behavior directly from your [pricing table](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/pricing-table) flow, no workarounds needed. You can enforce a cancellation cutoff period to ensure sufficient time for processing contract closures. This gives you the flexibility to model fixed-term subscriptions—paid in installments—that renew automatically.
### **How can you use it?**
When creating pricing page sessions, pass the `contract_term` parameters. This works for both [new](https://apidocs.chargebee.com/docs/api/pricing_page_sessions/create-pricing-page-for-new-subscription#contract_term) and [existing](https://apidocs.chargebee.com/docs/api/pricing_page_sessions/create-pricing-page-for-existing-subscription#contract_term) customers. Once the customer completes their purchase via [Checkout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout), the contract term settings are applied to the subscription.
## Sync Non-General Ledger item changes to NetSuite
Currently, plans, addons, and charges are created in NetSuite when first synced from Chargebee, but subsequent updates to those items in Chargebee are not synced to the NetSuite item master record.
### **Why is this important?**
When plans, addons, and charges are updated in Chargebee but not reflected in NetSuite, the item master record in NetSuite can become outdated, leading to inconsistencies in internal reports and operational analysis. While invoice creation continues to use the latest Chargebee data, reporting that relies on the NetSuite item record may not reflect current values. This enhancement helps you maintain accurate reporting in NetSuite while ensuring that accounting-sensitive fields remain protected from retrospective changes in closed periods.
### **How can you use it?**
1. In your Chargebee Billing site, go to **Apps** > **NetSuite** **Configure** **Advanced Sync Rules**.
2. Enable **Sync Item Updates** to start syncing non-GL-impacting fields from Chargebee to NetSuite for existing items, such as rate, tracking categories, supported custom fields, and rule ID.
## Fix for delayed updates in Checkout settings
We've fixed an issue where changes to [Smart Routing](https://www.chargebee.com/docs/billing/2.0/customers/configure-multiple-languages) or [Language Pack](https://www.chargebee.com/docs/billing/2.0/customers/configure-multiple-languages) settings weren't reflected immediately in [Checkout](https://www.chargebee.com/docs/billing/2.0/hosted-capabilities/hosted-checkout). This caused customers to see outdated translations, content, or routing behavior.
## Strict validation for trial_end parameter
Chargebee now enforces strict validation for the trial end dates. Previously, passing a wrong value of 0 caused the system to default to the Unix epoch start date (1970-01-01), leading to incorrect billing calculations. These requests are now rejected with a clear error message to help you make corrections before invoicing.
## Accurate tiered pricing
Previously when using tier-based price points with decimal values, applying discounts in Salesforce resulted in validation errors, and quote PDFs rounded tier prices to two decimal places, often displaying them as 0.00.
This issue has now been resolved. With this bug fix, you can now \* Prevent pricing discrepancies in customer-facing quotes \* Reduce errors when applying discounts in Salesforce \* Ensure high-precision tier and usage rates are displayed accurately
## Fixed Quote creation error with volume-based charges
We fixed an issue in [Chargebee CPQ](https://www.chargebee.com/docs/billing/2.0/chargebee-cpq/chargebee-cpq) that caused an error stating `item_tiers[starting_unit][0]: It should be atleast 1` when you created a quote with a volume-based one-time charge. This occurred because certain pricing details were not populated when MDS (Multi decimal support) was enabled, which prevented the quote from being created. With this fix, volume-based line items now work as expected, so you can add them to quotes without encountering validation errors and proceed with quote creation confidently.
## Shipping address now appears on invoices from quotes
Earlier, when you converted a one-time quote with both billing and shipping addresses into an invoice, only the billing address was displayed because the shipping address was not passed from the quote to the invoice. This bug has now been fixed, and the shipping address is correctly carried over during the conversion. This ensures your invoices show complete address details, which helps with accurate fulfillment, tax handling, and record-keeping.
## Resolved shipping address issue in checkout
We've fixed an issue in **Checkout** where certain shipping address inputs caused an error and blocked customers from completing their purchase. This issue could interrupt the buying flow and impact conversions when shipping details were captured. With this fix, checkout now handles shipping address data correctly, allowing customers to proceed without disruption.