Chargebee Release Notes
157 release notes curated from 1 source by the Releasebot Team. Last updated: Jun 16, 2026
- May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Connect AI assistants to Chargebee with MCP Servers (Beta)
Chargebee introduces MCP server support for connecting AI assistants like Cursor, Claude, and ChatGPT to live Chargebee data. It brings secure, context-aware access for answering API questions, generating integration code, building onboarding flows, and retrieving customer, subscription, invoice, event, and transaction records.
You can now connect your favorite AI assistants like Cursor, Claude, and ChatGPT directly to Chargebee using the Model Context Protocol (MCP). This allows your AI tools to securely read, analyze, and act on your Chargebee data using real-time account context.
What can your AI assistants do with Chargebee MCP?
Interact with Chargebee data in plain English through three specialized servers. Chargebee MCP anchors its responses in your live account data and up-to-date documentation to ensure highly reliable, context-aware results.
- Knowledge Base Server: Instantly answers complex API and integration questions, and generates working integration code for the REST API and Chargebee.js.
- Onboarding Server: Automatically generates a product catalog directly from your pricing page, and builds features, entitlements, and branding inside a test sandbox for faster evaluation.
- Data Access Server: Retrieves live records—including customer profiles, subscriptions, invoices, events and transactions.
Secure Access Control
You maintain full control over what your AI assistants can see and do. Secure standalone workflows with dedicated API keys, or authenticate via OAuth to ensure the AI’s permissions strictly mirror each user's existing Chargebee access level. Easily govern access by enabling only the specific servers and toolsets your team needs.
How can you use it?
- Log in to Chargebee Billing and go to Settings > Agentic AI > MCP Servers.
- Select the server you want to configure: Knowledge Base, Data Access, or Onboarding.
- On the Toolsets tab, enable the toolsets you want to expose on the server.
- On the Access & Authentication tab, under MCP Installation or Authentication, follow the Setup Guide for your AI assistant.
For a guided in-product alternative, see Chargebee Copilot.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Ask product questions and look up data with Chargebee Copilot (Beta)
Chargebee introduces Copilot, a built-in chat assistant for Chargebee Billing that answers product questions from docs and looks up customer and billing data in your site. It delivers instant guidance, code examples, and secure role-based access to account details.
Chargebee Copilot is a chat assistant built into Chargebee Billing that answers your questions without you leaving the application. It has two skills:
- It answers product questions using Chargebee docs.
- It looks up customer and billing data within your Chargebee site.
The skills available to you depend on your site configuration and access level.
Why is this important?
Copilot puts both skills a question away. Instead of searching the documentation to learn how a feature works, you get instant explanations, how-to guidance, and code examples in the chat. Instead of filtering through lists and records to resolve a support query, you ask for a customer's subscriptions, invoices, or latest transaction and get the answer back directly. Lookups respect the access privileges set for your user role, so Copilot surfaces only what you can already see.
How can you use it?
- Log in to your Chargebee Billing site.
- Click the Chargebee Copilot icon in the bottom-right corner, or open it from the ellipsis next to Need Help in the left navigation.
- Ask a question about Chargebee, or ask Copilot to look up your data.
To connect external AI assistants with Chargebee, see Chargebee MCP servers.
Original source All of your release notes in one feed
Join Releasebot and get updates from Chargebee and hundreds of other software products.
- May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Update recipient details on unclaimed gift subscriptions via API
Chargebee adds API support for updating unclaimed gift subscription recipient details, helping fix email typos and other errors so the right person can claim a gift without manual intervention.
You can now update the recipient details, including email address, first name, and last name, on an unclaimed gift subscription using the Update a gift operation in the Gifts API. Once a gift has been claimed, these fields are locked and can't be changed.
Why is this important?
If the purchaser enters the wrong recipient email at checkout, the intended recipient can't claim the gift, because the claim flow validates the email against the stored value before allowing redemption. Previously, fixing a typo meant contacting Chargebee for a manual data update. Now you can correct the recipient details yourself through the API, so the right person can complete their redemption without delay.
How can you use it?
Call the Update a gift operation with the updated gift_receiver[email], gift_receiver[first_name], or gift_receiver[last_name] values. The update is allowed only while the gift is unclaimed, and the claim flow then validates against the new values so the recipient can redeem normally. This updates the gift receiver details only, not the linked customer record; to change the customer record, update the customer separately.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Invoice final prorated period on scheduled cancellation
Chargebee introduces prorated final-period invoicing for subscriptions scheduled to cancel mid-period, reducing credit notes and simplifying billing, accounting, and deferred revenue reporting.
You can now choose to invoice the final billing period in a prorated manner when a subscription is scheduled for mid-period cancellation during upcoming billing periods.
Why is this important?
Previously, when a subscription was scheduled to end mid-cycle, Chargebee Billing invoiced the full final period and then issued a credit note for the unused portion. The net amount was correct, but the extra credit note created accounting artefacts, complicated integrations, and incorrectly reported deferred revenue until the credit note was generated at cancellation. By billing the exact final period upfront, Billing eliminates the need for a credit note and simplifies billing.
How can you use it?
- Go to Settings > Configure Chargebee > Billing LogIQ > Customers & Subscriptions > Subscription cancellation.
- For "When a subscription is scheduled to be canceled after the current billing period, how do you want to bill the final period?", select Invoice only the remaining term.
- Click Apply.
- May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Run multiple invoice numbering sequences on one site
Chargebee Billing adds multiple invoice numbering sequences on a single site, letting teams assign segment-based series by invoice or customer attributes for independent, non-overlapping invoice numbers and better compliance without splitting operations across sites.
Chargebee Billing now supports multiple invoice numbering sequences on a single site. Instead of one global series for every invoice, you can set up several numbering configurations and link each one to a segment: a set of conditions based on invoice or customer attributes such as business line, region, or the invoice template used. When an invoice matches a segment, Chargebee applies that segment's numbering series; if no segment matches, it uses the default. Invoices in different categories then receive independent, non-overlapping number sequences.
Why is this important?
Many businesses need to distinguish invoices by type, business line, region, or customer segment, for accounting and compliance. For example, some tax regimes require a separate numbering format for simplified invoices, and finance teams often want distinct series for different brands or entities. A single shared number series makes this hard without workarounds. Segment-based numbering lets you meet reconciliation and compliance requirements for each invoice category without splitting your operations across multiple Chargebee sites.
How can you use it?
Contact Chargebee Support to have the multiple invoice numbering feature enabled for your site.
Original source Similar to Chargebee with recent updates:
- Smokeball release notes135 release notes · Latest Jul 2, 2026
- Cosmolex release notes20 release notes · Latest Jul 30, 2025
- PracticePanther release notes34 release notes · Latest Apr 8, 2026
- Salesforce release notes49 release notes · Latest Jun 1, 2026
- Microsoft release notes638 release notes · Latest Jul 6, 2026
- Zoom release notes169 release notes · Latest Jul 3, 2026
- May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Smoother In-App Checkout and Higher Completion Rates
Chargebee improves In-App Checkout with instant subscription completion after payment authorization, fixed totals before payment, and smoother checkout safeguards that help reduce failed transactions and boost conversion.
Instant order completion after payment authorization
This release introduces key updates to In-App Checkout to make the purchase flow more intuitive, reduce failed transactions, and boost conversion rates for your business.
Chargebee now creates or updates the subscription the moment a payment is authorized, even if your customer doesn't make it back to the original checkout page. Many payment methods redirect customers to an external banking app or link for authorization. On mobile devices especially, customers often do not return to the original checkout page once the payment is approved. Chargebee now updates the subscription the moment authorization is received—ensuring a successful transaction even if the customer closes the window or navigates away.
Fixed total confirmation before payment
The payment authorization step now occurs immediately after the order review step. This locks in the exact final total—including taxes and shipping adjustments—before the customer authorizes the payment. This prevents total mismatches and failed transactions that previously occurred if a customer modified their address late in the checkout flow after an early authorization had already taken place.
Other improvements to the checkout flow
- Conditional Shipping Fields: Configure checkout to collect shipping addresses only when the cart contains shippable items.
- Early Error Validation: Address fields (like postal codes) are now validated during the address entry step, instead of at the final submit.
- Hybrid Cart Support: Smoother, error-free handling when you add a recurring item to one-time checkout.
- Skip Cart Safeguard: Enabling the "skip cart" setting will no longer bypass the customer login step.
How can you use it?
This experience is being rolled out in phases and your customers will see it when it is enabled for your site.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Richer BECS Direct Debit notifications for GoCardless
Chargebee adds richer BECS Direct Debit email notifications for GoCardless payments, helping merchants stay compliant with clearer pre-payment details like amount, currency, charge date, and description.
Chargebee now sends richer email notifications to your customers for BECS Direct Debit payments processed through GoCardless. Pre-payment notifications for recurring payments now include the debit amount, currency, the charge date, and a charge description.
Why is this important?
GoCardless enforces BECS compliance regulations for Direct Debit payment notifications. These notifications give your customers more detail about upcoming debits and changes to their Direct Debit Request (DDR).
How can you use it?
To stay compliant, enable Direct Debit email notifications for your customers either in Chargebee or GoCardless.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Credit unused charges when proration is re-enabled mid-term
Chargebee adds automatic credit notes when proration is re-enabled and a subscription is updated mid-term, so unused current-term charges are credited correctly and subscribers pay only the remaining difference.
When proration is re-enabled after being disabled, updating a subscription mid-term now automatically generates a credit note for the unused portion of the current term charges.
Why is this important?
Businesses running periodic price increases often turn proration off during a mid-cycle change so existing subscribers aren't charged right away. Previously, if a subscriber then upgraded or changed their subscription later in the same term with proration on, Chargebee did not credit what they had already paid for that term, which could overcharge them. This enhancement credits the unused current-term charges correctly, so your subscribers pay only the incremental difference for the remaining days.
How can you use it?
No additional setup is required.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Set a per-item origin address for Avalara sales tax
Chargebee adds Avalara location codes for individual price points, improving line-item tax accuracy by sending the right origin address to AvaTax instead of using a single site-level address.
You can now assign an Avalara location code to individual price points in Chargebee Billing. When a location code is set on a price point, Chargebee sends the matching origin address to AvaTax for Sales at the line-item level during tax calculation, instead of applying the site-level organization address to every item.
Why is this important?
Some businesses ship goods from more than one location, or sell products tied to different physical origins. Applying a single site-level origin address to every line item produces the wrong tax for any item whose origin differs from your primary address. By passing a per-item origin address to Avalara, Chargebee applies the correct jurisdiction and rate to each line item based on where that product or service originates.
How can you use it?
- Go to Product Catalog > Plans (or Addons), and open the item price you want to edit.
- In the tax settings, select a location code from the dropdown. The list is populated from the locations configured for your Avalara company. If you don't set a location code, tax calculation falls back to the existing site-level organization address. Note: If a location code configured in Chargebee is later modified or removed in Avalara, tax calculations for that item will fail.
- Save the price point. Chargebee will now include the origin address for that location in the line-item-level tax request sent to Avalara for any invoice containing that item price.
- May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Usage Summary API now returns the correct billing term after a term reset
Chargebee fixes the Usage Summary API to return the correct billing term after term resets and mid-term subscription changes.
The Usage Summary API was returning an incorrect billing term for subscription items in cases where a term reset had occurred, for example, when a mid-term subscription change involved a billing period update. The term window shown in the usage summary for affected items did not reflect the actual current billing period. The API now returns the correct term for all items regardless of whether a term reset has taken place.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Subscription create and update APIs now validate Automated Metered Billing configurations
Chargebee tightens subscription API validation for automated metered billing, catching invalid configs before submission.
The Create Subscription and Update Subscription APIs now enforce validation rules specific to automated metered billing. Previously, certain invalid configurations could be submitted without returning an error, leading to inconsistent subscription states downstream. Requests that violate automated metered billing constraints will now receive a clear API error at the point of submission, making it easier to identify and correct configuration issues before they affect billing.
Original source - May 1, 2026
- Date parsed from source:May 1, 2026
- First seen by Releasebot:Jun 16, 2026
Corrected state code mapping for Chhattisgarh in the Taxes API
Chargebee fixes Taxes API state code handling so Chhattisgarh customer addresses and tax records are saved correctly.
The state code for Chhattisgarh, India, in Chargebee's Taxes API was not aligned with the current ISO 3166-2 standard. Chargebee was mapping the state using CT, while the ISO 3166-2 code is also CT (IN-CT)—however, when the state code CG was passed via the API, it was not being recognized and the state was not updated correctly. The internal state code mapping file has been updated to correctly handle the Chhattisgarh state code, so addresses and tax records for customers in Chhattisgarh are now saved and processed accurately.
Original source - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:May 21, 2026
Unlock Brazil's Favorite Way to Pay - Pix (BETA)
Chargebee adds Pix payments for Brazil through the dLocal gateway, letting businesses accept local instant bank payments in Chargebee Billing with higher authorization rates, lower involuntary churn, and automated subscription workflows without local entity overhead.
You can now accept Pix, Brazil’s most popular instant payment method, directly within Chargebee Billing via the dLocal gateway.
Why is this important for your growth in Brazil?
- Bypass Credit Card Declines: Cross-border credit cards in Brazil suffer from high failure rates due to aggressive anti-fraud blocks. Pix runs directly through bank accounts, offering higher authorization rates and drastically reducing involuntary churn.
- Zero Local Friction: Via dLocal, you can accept local Brazilian payments seamlessly without the legal, operational, and tax overhead of establishing a local regional entity.
- Automated Subscription Workflows: Built-in webhooks automatically track payment status, verify transactions asynchronously
How can you use it?
Follow these steps to configure Pix as a payment method for dLocal in your Chargebee Billing site:
- Go to Settings > Configure Chargebee > Payment Gateways > dLocal.
- Enable Pix on the Configure dLocal page.
- Click Apply to save your changes.
Once enabled, you can start accepting Pix payments. To learn more, refer to the documentation.
Original source - Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:May 21, 2026
Set a site-level redirect URL for subscription checkout
Chargebee adds a site-level redirect URL for subscription Checkout sessions, giving teams a fallback destination after checkout while keeping separate API, session, and plan-level redirects. Sites migrated from legacy Checkout automatically copy the existing redirect URL into the new setting.
You can now configure a site-level redirect URL for subscription Checkout sessions that is distinct from the URL configured for one-time Checkout. If your site is migrated from the legacy Checkout suite, your existing site-level redirect URL is copied to the new configuration.
Why is this important?
You can use this URL as a fallback destination after a subscription checkout is completed, while continuing to set separate redirect URLs at the API session and plan levels. This gives you more control over where customers are sent after completing subscription checkout. Chargebee applies redirect URLs in the following order of precedence: API or session-level URL first, plan-level URL next, and site-level URL last.
How can you use it?
- Sign in to Chargebee Billing.
- Navigate to Settings > Configure Chargebee > Checkout & Self-Serve Portal > Configuration tab.
- In the Checkout section, scroll down to Redirect URL and select the downward chevron (˅) next to it.
- In the text box, enter a valid HTTP or HTTPS URL to redirect to, then select APPLY.
- Apr 1, 2026
- Date parsed from source:Apr 1, 2026
- First seen by Releasebot:May 21, 2026
Target Renewal Reminders by Billing Country
Chargebee adds location-based customer segments for renewal reminder notifications, helping teams target specific geographies and stay aligned with local subscription compliance rules in markets like the UK and EU.
You can now leverage location-based customer segments to target subscription renewal reminders to specific geographies, ensuring seamless adherence to local regulations.
Why is this important for your global compliance and revenue operations?
Strict consumer regulations, such as those in the UK and EU, require advance notice before a subscription auto-renews. With this update, you can isolate these notifications to a location or country, ensuring local compliance without over-notifying global subscribers.
How can you use it?
- Sign in to Chargebee Billing site.
- Navigate to the Subscriptions or Customers list page.
- Use the filter to define a segment with billing country as a condition. Save this segment and apply it when configuring renewal reminder notifications.
You can attach different segments to notification workflows and schedule reminders at required intervals, ensuring that only customers in the selected locations receive the communication at the right time.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.