May 2026

Connect AI assistants to Chargebee with MCP Servers

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?

1. Log in to Chargebee Billing and go to Settings > Agentic AI > MCP Servers.
2. Select the server you want to configure: Knowledge Base, Data Access, or Onboarding.
3. On the Toolsets tab, enable the toolsets you want to expose on the server.
4. 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.

Ask product questions and look up data with Chargebee Copilot

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?

1. Log in to your Chargebee Billing site.
2. Click the Chargebee Copilot icon in the bottom-right corner, or open it from the ellipsis next to Need Help in the left navigation.
3. Ask a question about Chargebee, or ask Copilot to look up your data.

To connect external AI assistants with Chargebee, see Chargebee MCP servers.

Build custom apps on Chargebee with the Chargebee Apps CLI (Early Access)

The Chargebee Apps CLI lets you build private serverless applications that extend Chargebee Billing by responding to Chargebee events. Scaffold an app, implement and test event handlers locally, and package it into a ZIP file—with no server or infrastructure to provision, scale, or maintain.

Why is this important?

Custom apps let you add tailored automation and integrations on top of Chargebee without standing up and maintaining your own backend. You write only the handler logic; Chargebee runs it in its hosted environment whenever a matching event occurs.

How can you use it?

1. Install the CLI globally from npm using the @chargebee/chargebee-apps package (see the CLI developer guide).
2. Create an app using chargebee-apps create <app_name> with the standard or iParams template.
3. Implement your event handlers and test them locally using chargebee-apps run.
4. Package your app using chargebee-apps package, then contact support to publish it privately to your site.

The Apps CLI is in early access. Request access to enable it on your test site.

Update recipient details on unclaimed gift subscriptions via API

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.

Invoice final prorated period on scheduled cancellation

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?

1. Go to Settings > Configure Chargebee > Billing LogIQ > Customers & Subscriptions > Subscription cancellation.
2. 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.
3. Click Apply.

Run multiple invoice numbering sequences on one site

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.

Look up quotes, exports, and subscription ramps through MCP

AI clients connected to Data Lookup MCP can now work with quote data (including PDF links), export jobs for large datasets, and subscription ramp lookups—alongside existing customer, subscription, invoice, and payment tools.

Why is this important?

Teams can investigate quotes, pull bulk exports, and inspect ramp schedules from the same AI client they already use for billing lookups.

How can you use it?

1. In the Chargebee Billing app, go to Settings > Configure Chargebee > Agentic AI > MCP Servers.
2. Open Chargebee Data Lookup MCP Server.
3. Enable quote, export, and subscription-ramp tools.
4. In your AI client, ask for quote details, start or check an export job, or retrieve ramp data for a subscription.

Smoother In-App Checkout and Higher Completion Rates

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.

Instant order completion after payment authorization

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.

Richer BECS Direct Debit notifications for GoCardless

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.

Credit unused charges when proration is re-enabled mid-term

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.

Set a per-item origin address for Avalara sales tax

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?

1. Go to Product Catalog > Plans (or Addons), and open the item price you want to edit.
2. 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.
3. 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.

Usage Summary API now returns the correct billing term after a term reset

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.

Subscription create and update APIs now validate Automated Metered Billing configurations

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.

Corrected state code mapping for Chhattisgarh in the Taxes API

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.