Chargebee Release Notes

You can now accept Google Pay via Worldpay US eCom (Vantiv). Google Pay is a digital wallet for card payments.

Why is this important?

Google Pay via Worldpay US eCom (Vantiv) helps you convert customers who already store cards in Google Wallet, especially on mobile, without typing card details at checkout. If you already process cards on Worldpay US eCom, Google Pay settles on the same Worldpay connection instead of routing wallet traffic elsewhere.

How can you use it?

Prerequisite: Contact Chargebee Support to enable Google Pay via Worldpay US eCom (Vantiv) if it is not already enabled for your site.

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Payment Gateways > Worldpay US eCom (Vantiv Litle), enable Google Pay, and complete the Google Pay fields.
3. Confirm Smart Routing for the Google Pay path you want.

For setup details, see Google Pay via Worldpay US eCom (Vantiv).

You can now accept Alipay and Klarna via Adyen at checkout and on Chargebee hosted pages.

Why is this important?

1. Alipay is a digital wallet widely used in China and by Chinese travelers and diaspora shoppers. It supports one-time wallet payments across Adyen's supported currencies. Chargebee Billing already offered Alipay on other gateways; Adyen support helps when Adyen is already your primary stack for Asia or for routing alternative payment methods (local wallets and bank methods), so you do not need a second processor only for Alipay.
2. Klarna is a Buy Now, Pay Later (BNPL) / bank-based option for Europe and other Klarna-supported markets (pay later, installments, or pay now, depending on shopper eligibility). If you already take cards on Adyen, Klarna on the same connection lets you offer flexible payment terms where BNPL lifts conversion, without integrating Klarna as a standalone gateway.

How can you use it?

To accept Alipay or Klarna through Adyen:

Prerequisite: Enable the payment method in your Adyen account, and contact Chargebee Support to enable Alipay and Klarna in your Chargebee Billing site. …

Chargebee's PayPal wallet integration now supports the PayPal Complete Payments Platform (PPCP) Vault ID flow, in addition to the legacy Billing Agreement ID (BAID) flow. After the customer approves PayPal, Chargebee creates and stores a Vault ID and uses it for future payments. Existing merchants with BAIDs continue to process recurring payments without interruption; backward compatibility is maintained.

Why is this important?

Chargebee previously supported PayPal wallet only through PayPal's legacy BAID integration. Upgrading to the Vault ID-based flow on PPCP aligns Chargebee with PayPal's Complete Payments Platform and enables modern PayPal APIs, improved tokenization and reuse, and better compliance and future support.

How can you use it?

To use Vault ID for PayPal wallet payments on PPCP:

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Payment Gateways, open your PayPal gateway, and reconnect your PayPal account so Chargebee can request the vaulting permission required for PayPal wallet.
3. After you reconnect, new PayPal wallet payments use the Vault ID flow. Existing BAID payment methods keep working. …

You can now see every payment intent started through Chargebee Checkout components and hosted pages in one place. The Payment Intents log lists each intent with its status, customer information, attempt details, and associated metadata. The details page breaks a single intent into every attempt, with error codes, failure reasons, and gateway responses.

Why is this important?

Not every failed payment attempt creates a transaction in Chargebee Billing, so first-time checkout failures were hard to see and harder to explain. Payment Intent logs close that gap: you get full visibility into every attempt, your team can diagnose declines and authentication failures without raising a support ticket, and you can act on repeated failures before they turn into abandoned checkouts.

How can you use it?

To review payment intents:

1. Log in to your Chargebee Billing site.
2. Go to Logs > Payment Intents.
3. Select any intent to open the details page.
4. Review the Intent Summary, Customer Info, and Attempts for status, payment method, errors, and gateway responses.

For more details, check our Payment Intents documentation.

You can now track a payment from start to finish on a single timeline. Transaction Lifecycle appears on the transaction details page and lays out every major event in order—from intent created and authorized through transaction created, status changes, and any refunds or reversals. Each step includes a label, timestamp, linked entity or reference ID, and relevant amounts and statuses.

Why is this important?

Tracing a payment used to mean piecing the story together from several places. One ordered timeline answers what happened and in what order, so you can explain a payment to a customer, verify refunds during an audit, or pinpoint where a payment broke.

How can you use it?

To open Transaction Lifecycle:

1. Log in to your Chargebee Billing site.
2. Go to Logs > Transactions.
3. Select any transaction to open its details page.
4. Review the lifecycle timeline on the right, from the first event to the most recent.
5. Use the linked entity IDs to jump to the related payment intent, refund, or transaction.

For full details, see Transaction Lifecycle.

You can now inspect the API conversation between Chargebee and your payment gateways. Gateway Activity Logs record each call Chargebee makes for payments, refunds, and other gateway operations—including request and response headers and bodies, status code, duration, and related transaction and customer context. A trace ID groups every call made during the same operation so you can follow a multi-step payment flow end to end.

Why is this important?

When a payment behaves unexpectedly, the answer is usually in what the gateway returned. Having those calls in Chargebee means you can debug failures and integration issues without asking your gateway for logs, follow multi-call operations with a single trace ID, and keep sensitive values such as card numbers, CVV codes, and authentication tokens masked before storage.

How can you use it?

To review gateway activity:

1. Log in to your Chargebee Billing site.
2. Go to Logs > Gateway Activity.
3. Search the logs, or filter by operation type, gateway, status code, HTTP method, invocation time, or a related resource ID.
4. Select a log to see the full request and response, along with duration, source, and trace ID.
5. From a transaction or payment intent details page, use View Request/Response Logs when you need the calls for that payment. …

You can now check exactly what your payment gateway sent to Chargebee and how Chargebee responded. Gateway Webhook Logs record each incoming webhook with its headers, payload, the HTTP status code Chargebee returned, the endpoint that received it, and how long processing took. The logs for each webhook link to the related transaction, customer, or invoice.

Why is this important?

A payment that looks stuck in Chargebee is often a webhook that never arrived or failed to process. These logs let you confirm whether Chargebee received a webhook, inspect what the gateway actually reported, and investigate failed, delayed, or duplicate webhooks. Sensitive header and payload values are masked before storage.

How can you use it?

To review gateway webhooks:

1. Log in to your Chargebee Billing site.
2. Go to Logs > Gateway Webhooks.
3. Search the logs, or filter by gateway, status code, URL, received time, or a related transaction, customer, or invoice ID.
4. Select a row to open the webhook details and review Headers and Webhook Payload. …

You can now monitor payment recovery across your site from one screen. The Retries page lists every invoice in the payment retry cycle, showing retry status, attempts, when the cycle started or the next retry is scheduled, payment source, last error, gateway, recovery system, and whether the last failure is retryable.

Why is this important?

Recovery progress used to be visible only one invoice at a time. In a single list, you can spot invoices failing on the same error or gateway, use Retryable to separate soft failures from hard declines that need a payment-method update, and see whether Chargebee, FlexPay, or Success+ is driving each retry.

How can you use it?

1. Log in to your Chargebee Billing site.
2. Go to Logs > Retries.
3. Search by invoice or customer, or use Filter list to narrow by retry status, amount due, currency, next retry, gateway, error code, recovery system, or attempts.
4. Click an invoice amount or number to open the invoice.
5. To collect payment now, or to pause, resume, or stop retries, use the dunning controls on the invoice. …

You can now configure tool input schemas for Chargebee MCP tools. You can tailor which fields AI clients can send, disable fields, set defaults, or add constraints, while Chargebee still validates inputs and returns clear error feedback.

Why is this important?

Different use cases need different guardrails. Tool input configuration lets you limit what agents can submit per server and tool, reducing risk and keeping agent-driven billing actions within the limits you define.

How can you use it?

1. In Chargebee Billing, go to Settings > Configure Chargebee > Agentic AI > MCP Servers.
2. Open the MCP server you want to configure.
3. On the Tools tab, open the tool you want to constrain.
4. Configure inputs (disable fields, set defaults, or add min/max and length constraints), then click Save.

Note: Tool input configurations apply only to the specific server and tool where they are set.

You can now connect Claude to Chargebee MCP through the official Claude Marketplace. This replaces manual setup, letting you link your account in just a couple of clicks from the connector directory.

Why is this important?

The marketplace connector removes setup complexity and gives admins and builders immediate, secure access to Chargebee context in the tools they already use daily.

How can you use it?

1. Open the Chargebee connector in the Claude Marketplace.
2. Follow Claude's connect flow and authenticate with your Chargebee MCP access (API key or OAuth, as configured for your server).
3. In Chargebee Billing, confirm the tools you want exposed under Settings > Configure Chargebee > Agentic AI > MCP Servers.

Note: You are responsible for actions AI clients perform through MCP. Connect only trusted clients and review actions before they run.

When you record a purchase with a that does not already exist, Chargebee Billing now creates the customer automatically and links the omnichannel subscription to it. To include basic profile details for the new customer record, you can optionally pass , , and in the same request.

Why is this important?

Previously you had to create the customer first, then record the purchase. That extra step slowed process that depend on omnichannel_subscription_created event, increased API volume on bulk imports, and forced you to maintain ordering logic. One API call now covers both steps.

How can you use it?

1. Call the Record a Purchase API with .
2. If the customer record does not exist, Chargebee creates it and records the purchase.
3. Optionally include , , and/or to populate the new customer record.

Chargebee now supports Razorpay Import so businesses registered outside India can collect INR from Indian customers, including cards, UPI mandates, and Netbanking eMandates, and settle to an overseas SWIFT-enabled bank account, without an Indian legal entity. After successful Import payments, Chargebee generates the invoice and sends it to Razorpay automatically. Chargebee can also render Razorpay UPI QR codes in an iframe on desktop instead of opening a new browser tab.

Why is this important?

1. Razorpay Import is for international SaaS / services businesses that need India-local methods (especially UPI) while settling overseas. It is a separate Razorpay merchant account from Domestic / Export, and Chargebee's integration covers the SaaS Import path (not physical goods).
2. In-page UPI QR improves India checkout for UPI: keeping the QR on the same page avoids breaking immersion when Razorpay has enabled iframe / collect QR for your account.

How can you use it?

To set up Razorpay Import or in-page UPI QR:

Prerequisite: …

In Error Intelligence, you can now control whether errors under an error cause ID are treated as retryable.

Why is this important?

Not every decline under the same cause should stop collection. Retryability overrides let soft failures continue into dunning or retries, so you recover more revenue on temporary failures while still hard-failing true permanent declines. You get finer control than Chargebee's default cause-level behavior alone.

How can you use it?

To mark payment error causes as retryable:

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Error Settings to open Error Handling Settings.
3. Select the Gateway error group, then find the Chargebee Error ID or matching condition you want to adjust.
4. Set Retryable at the error ID level or for the specific matching rule, then click Apply.

For payment error overrides and dunning behavior, see Payment errors.

The Payment Method Type filter on the Customers index now includes offline methods such as bank transfer, cash, and cheque.

Why is this important?

Ops and finance teams often need to segment customers by offline payment methods for reconciliation and follow-up. Those methods were missing from the filter before, which forced API exports or support requests.

How can you use it?

To filter customers by offline payment methods:

1. Log in to your Chargebee Billing site.
2. Open the Customers list.
3. Open the Payment Method Type filter and select the online or offline methods you need.

For payment method types in Chargebee, see Payment methods overview.

You can now omit when you call Create pricing page for new subscription. Pass a valid instead, and Plays resolve which Pricing Table to serve from your targeting rules. Previously this endpoint required a specific pricing page ID, so every prospect who hit it saw the same table.

Why is this important?

You can now dynamically target pricing tables to people who don't have a subscription yet, not just returning subscribers. That means:

• Prospects see pricing matched to their segment instead of one static table.
• You can run targeting and experiments on acquisition pricing.
• New subscription sessions behave the same way existing subscription sessions already do.

How can you use it?

In your Chargebee Growth site:

1. Configure targeting for your pricing table in Plays.
2. Call with and leave out of the request. …

The Chargebee MCP tool catalog now includes more operations for AI clients: checkout operations, product (item) and item family lookups, and improved customer lookup tools.

Why is this important?

Broader read and workflow coverage lets connected agents answer product-catalog questions, work with hosted-page flows, and find customer records more reliably, without leaving the AI client.

How can you use it?

1. In your Chargebee Billing site, go to Settings > Configure Chargebee > Agentic AI > MCP Servers.
2. Open the server (system or custom) you use with your AI client.
3. On the Tools tab, enable the hosted page, product/item, item family, and customer tools you need.
4. Reconnect or refresh your AI client so it picks up the updated tool list.

You can now export omnichannel subscriptions directly from the omnichannel subscriptions list page. Previously, list-page export was unavailable even though export via Settings > Import & Export Data was supported.

Why is this important?

You can download filtered omnichannel subscription data without leaving the list page, which speeds up reporting and operational workflows as Apple and Google subscription volume grows.

How can you use it?

1. In Chargebee Billing, open the Omnichannel subscriptions list page.
2. Optionally apply filters, then choose Export > Download data.
3. Download the CSV when the export job completes.

Omnichannel events now show the API key name as the acting user, instead of a generic "omnichannel" label. This makes it clear which integration or key triggered each event.

Why is this important?

When multiple keys or systems write omnichannel data, a generic user makes audit and troubleshooting harder. Showing the API key name ties each event to the source that produced it.

How can you use it?

Review omnichannel-related events in Chargebee Billing; the user field now reflects the API key name used for the request. No additional setup is required.

You can now set Auto Collection and Payment Terms (Net D) when you create a one-time invoice in the Chargebee Billing UI.

Why is this important?

When you create a one-time invoice in the UI, you're no longer tied to the customer's stored settings. You can set the collection behavior and due date that fit each charge:

• Choose whether Chargebee attempts to collect payment automatically for that invoice.
• Set how many days the customer has to pay (Net D).

These overrides were already available on the Create invoice for items and one-time charges API. The create-invoice flow in the UI now gives you the same controls.

How can you use it?

1. On your Chargebee Billing site, confirm that Payment Terms (Net D) for one-time invoices are enabled.
2. Open a customer or subscription record, select Add One-Time Charges and Addons, and add your charges or items.
3. Set Auto Collection and Net term days (Payment Terms) for this invoice as needed, then preview and create the invoice.

The Create invoice for items and one-time charges API now supports , so you can create a one-time invoice in Pending status and close it when you're ready.

Why is this important?

You can stage one-time invoices before they're finalized, and add the exact line wording you need on the invoice without changing the underlying catalog item. You can also override line item descriptions on and when you create the invoice, so the text on the invoice can differ from the product catalog default for that charge.

How can you use it?

1. Call the Create invoice for items and one-time charges API.
2. Set to when you want the invoice created as Pending.
3. Pass or (and related description fields as needed) to override line text for that invoice.