June 2026

Accept Klarna Buy Now, Pay Later payments via Stripe

You can now offer Klarna, a popular Buy Now, Pay Later (BNPL) method, through the Stripe gateway. During checkout, your customers can choose to pay in full, pay later, or split the cost into interest-free installments, based on their eligibility and region.

Why is this important?

Offering Klarna gives shoppers more flexible payment options and can improve conversion in regions with high BNPL adoption. Because it runs through your existing Stripe connection, you can start accepting Klarna without adding a new gateway. Klarna via Stripe supports both one-time payments and recurring subscriptions using subscription-scoped mandates.

How can you use it?

1. Prerequisite: Enable Klarna in your Stripe account.
2. This feature is in Beta — contact Chargebee Support to get it enabled for your live and test sites.
3. Once enabled by Chargebee Support, turn on Klarna under Settings > Configure Chargebee > Payment Gateway > Stripe.
4. Under Smart Routing, assign your Stripe account to Klarna for the relevant currency, and then click Apply.

Klarna via Stripe currently supports USD; support for additional currencies depends on your Stripe account configuration.

Collect NZD direct debit payments with BECS NZ via Stripe

You can now collect New Zealand Dollar (NZD) direct debit payments using the BECS NZ scheme through the Stripe gateway. Previously, BECS NZ was available only via GoCardless.

Why is this important?

You can now keep Stripe as your primary gateway for both cards and direct debit in New Zealand, simplifying reconciliation and reporting while offering customers a low-friction local bank debit option. This extends Chargebee's Direct Debit coverage alongside ACH, SEPA, BACS, BECS AU, PAD, and Autogiro.

How can you use it?

1. Prerequisite: Enable BECS NZ in your Stripe account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on BECS Direct Debit (for the NZ region only) under Settings > Configure Chargebee > Payment Gateways > Stripe.
4. Enter your business name, email, and contact number, then click Save and Apply.

New Zealand customers paying in NZD can then add a bank account and accept the mandate at checkout, and recurring charges are collected via BECS NZ direct debit.

Accept PayPay payments in Japan via Stripe

You can now accept PayPay, a leading QR-code-based mobile wallet in Japan, through the Stripe gateway. Customers are redirected to authorize the payment and returned to Chargebee once it completes. PayPay via Stripe supports one-time payments in JPY only.

Why is this important?

PayPay is one of Japan's most widely used wallets. Offering it gives your Japanese customers a familiar local checkout experience and can improve conversion, all through your existing Stripe connection.

How can you use it?

1. Prerequisite: Enable PayPay in your Stripe account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on PayPay under Settings > Configure Chargebee > Payment Gateway > Stripe and click Apply.

Accept South Korean card payments via Stripe

You can now accept South Korean cards through the Stripe gateway during checkout. Customers authenticate with their South Korean card credentials on the provider's page and then return to Chargebee once the process is complete. This method supports both one-time and recurring payments in KRW.

Why is this important?

South Korean cards rely on local authentication and processing rails. Native support lets you serve customers in South Korea natively, with local authentication, and can improve conversion using your existing Stripe connection.

How can you use it?

1. Prerequisite: Enable South Korean cards in your Stripe account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on South Korean cards under Settings > Configure Chargebee > Payment Gateway > Stripe and click Apply.

Accept Alipay and Alipay HK via Adyen

You can now accept Alipay and Alipay HK, leading digital wallets in China and Hong Kong, through the Adyen gateway. Customers authorize payments in the Alipay or Alipay HK app on mobile, or by scanning a QR code on desktop. Both are one-time payment methods: Alipay supports CNY, AUD, CAD, EUR, GBP, HKD, JPY, SGD, MYR, NZD, and USD, while Alipay HK supports HKD.

Why is this important?

Alipay and Alipay HK are preferred wallets for many shoppers in China and Hong Kong. Offering them through Adyen expands your local payment coverage and can improve conversion in supported regions.

How can you use it?

1. Prerequisite: Enable Alipay and Alipay HK in your Adyen account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on Alipay and Alipay HK under Settings > Configure Chargebee > Payment Gateways for your Adyen instance and click Apply.

Accept PayPay and GCash wallets via Adyen

You can now accept two more local wallets through the Adyen gateway: PayPay in Japan and GCash in the Philippines. In both flows, customers authorize the payment in their wallet app and are returned to Chargebee once it completes.

Why is this important?

PayPay and GCash are among the most widely used wallets in their markets. Offering them helps you provide a familiar local checkout experience and improve conversion. PayPay supports one-time payments in JPY, while GCash supports recurring subscriptions in PHP after the initial customer authorization.

How can you use it?

1. Prerequisite: Enable PayPay or GCash in your Adyen account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on the payment method under Settings > Configure Chargebee > Payment Gateways for your Adyen instance and click Apply.

Accept Apple Pay and Google Pay via Worldpay US eCom (Vantiv)

You can now offer Apple Pay and Google Pay through the Worldpay US eCom (Vantiv Litle) gateway, at Checkout and on Hosted Pages. On eligible devices, customers can pay quickly using Apple Pay (with Face ID, Touch ID, or their device passcode) or any card saved to their Google Account.

Why is this important?

Apple Pay and Google Pay offer a fast, secure, low-friction checkout that can improve conversion, especially on Apple devices and on Android and Chrome. You can now offer both through Worldpay US eCom (Vantiv Litle) within your existing Chargebee-powered payment flows, with the wallet card reused for subsequent recurring payments.

How can you use it?

1. Prerequisite: Set up Apple Pay in your Apple Developer account and Google Pay in the Google Pay & Wallet Console, and ensure both are enabled on your Worldpay US eCom account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on Apple Pay and Google Pay under Settings > Configure Chargebee > Payment Gateway > Worldpay US eCom (Vantiv Litle), provide the required certificates and merchant details, and click Save.

Process card payments through the Ecentric gateway

Chargebee now supports card processing through the Ecentric payment gateway, integrated via the payFURL partner platform. The integration supports card payments in South African Rand (ZAR), merchant-initiated transactions (MIT) using vaulted tokens, and card vaulting and reuse.

Why is this important?

Adding Ecentric expands Chargebee's gateway coverage for card payments and gives you more flexibility in how you route and secure card transactions, particularly for businesses operating in South Africa.

How can you use it?

1. Prerequisite: Have an Ecentric Payment Systems account with your Merchant GUID and Environment API URL.
2. Configure Ecentric in Chargebee Billing. Go to Settings > Configure Chargebee > Payment Gateways, click Add Gateway, select Ecentric Payment System, enter your Merchant GUID and Environment API URL, and click Connect.

Once configured, card payments can be routed through this gateway.

Collect ACH payments via NMI

You can now collect ACH bank account (direct debit) payments through the NMI gateway.

Why is this important?

ACH lets your US customers pay directly from their bank account, offering a lower-cost alternative to cards and helping reduce card-related failures and churn. You can now offer ACH alongside cards within your existing NMI connection.

How can you use it?

1. Prerequisite: Enable ACH in your NMI account.
2. This feature is in Beta — contact Chargebee Support to get it enabled.
3. Once enabled by Chargebee Support, turn on ACH for your NMI gateway in Chargebee Billing. Eligible customers can then pay directly from their bank account at checkout, and ACH payment status updates are handled through webhooks.

Perform selected billing actions through Chargebee MCP

You can now use Chargebee MCP servers for selected write operations—not only data lookup. Connected AI clients can manage customers and subscriptions and collect invoice payments, so agents can move from answering questions to completing approved billing actions in the same workflow.

Why is this important?

Until now, MCP was focused on retrieval. Write support lets teams automate common billing tasks from tools like Claude, Cursor, and ChatGPT, while you still control which tools each server exposes and how clients authenticate.

How can you use it?

1. In the Chargebee Billing app, go to Settings > Configure Chargebee > Agentic AI > MCP Servers.
2. Open the server you want to use (system or custom).
3. On the Toolsets / Tools tab, enable only the write tools you need.
4. On Access & Authentication, connect your AI client with API key or OAuth, then review and approve actions in the client before they run.

You are responsible for actions AI clients perform through MCP, including writes. Connect only trusted clients and review actions before they run.

Build custom MCP servers with the tools your AI clients need

You can now create custom MCP servers by assembling tools from Chargebee's catalog. Pick only the tools each use case needs, turn tools on or off per server, and connect AI clients to a focused endpoint instead of a broad default server.

Why is this important?

Different teams need different access. Custom servers let you scope tool access per use case—for example, invoice lookup only, or customer and subscription management—and reduce unnecessary exposure.

How can you use it?

1. In the Chargebee Billing app, go to Settings > Configure Chargebee > Agentic AI > MCP Servers.
2. Under Custom MCP servers, click + Create custom server.
3. Name the server, add tools from the catalog, and toggle individual tools as needed.
4. On Access & Authentication, turn on MCP Access and share the server URL with your AI client (API key or OAuth).

Note: Custom MCP servers require latest Product Catalog (PC 2.0).

Simplified webhook setup for the Razorpay OAuth integration

Chargebee now supports webhooks for Razorpay connected through the OAuth-based partner integration, using a single shared webhook URL configured by Chargebee at the partner level.

Why is this important?

Previously, each Razorpay gateway account required its own unique webhook URL. With the OAuth partner integration, Chargebee manages a single webhook endpoint centrally, so you no longer need to configure a separate webhook URL for each account. This simplifies onboarding and ongoing maintenance for Razorpay connections.

How can you use it?

Connect Razorpay to Chargebee Billing using the OAuth flow. Webhook configuration is handled as part of the partner integration, so no manual per-account webhook setup is required.

Override retry behavior for specific gateway error codes

You can now customize Chargebee's default retry behavior for specific gateway error codes, in addition to the overrides already available at the Chargebee error cause level.

Why is this important?

Chargebee Billing applies default retry (dunning) behavior based on standardized error causes. By overriding this behavior for specific gateway error codes, you can tailor your payment recovery strategy — deciding which failures should enter dunning retries and which should be marked as failed without further retry attempts — while retaining Chargebee's platform defaults wherever you haven't set an override. This helps improve recovery rates and reduce involuntary churn.

How can you use it?

Set up error overrides at the gateway error code level from your payment error settings in Chargebee Billing. Learn more

Domain validation for Chargebee.js loading

Chargebee.js now validates the domain on which it is loaded, adding a layer of protection against unauthorized use of your Chargebee.js integration.

Why is this important?

Restricting Chargebee.js to approved domains helps prevent your keys and checkout components from being misused on unauthorized sites, strengthening the security of your payment pages.

How can you use it?

No action is required for standard integrations. If you load Chargebee.js on custom domains, ensure they are among your configured allowed domains so the library loads correctly.

Mobile numeric keypad for card and bank fields in Payment Components

On mobile devices, the digit-only fields in Payment Components now bring up a number-optimized keypad automatically. Card expiry, CVV, and bank fields show the numeric keypad, while the card number and phone number fields show the telephone keypad.

Why is this important?

Your customers no longer have to switch a full QWERTY keyboard over to its number layout to type a card or bank number on their phone. The right keypad appears the moment they tap into the field, which makes mobile checkout faster and reduces entry errors.

How can you use it?

No additional setup is required. The correct keypad appears automatically for customers completing these fields on a mobile browser.

Recognize payment and credit note application in the period it happens

RevRec Premium can now recognize the reclassification of a payment or credit note from Unapplied to Applied based on the date it is actually applied, rather than the original payment or transaction date.

Why is this important?

Previously, when an unapplied payment (or a credit note) was applied to an invoice in a later period, the reclassification depended on whether the earlier period was still open. If it was open, the system would reduce the unapplied balance back in the original period; if it was already closed, it recorded the reduction in the later period. That made your balances depend on period-close timing and could restate a prior period.

For example, a $10,000 payment received in January with no invoice sits fully unapplied; when a $500 invoice in February draws $500 from it, the $500 reduction should belong to February, not January.

How can you use it?

Contact Chargebee Support to get it enabled for your site.

Filter and export omnichannel subscriptions (Early Access)

On the omnichannel subscriptions list page, use the new purchased_at and updated_at filters to narrow results by purchase and last-updated dates. The List Omnichannel Subscriptions API supports additional filter parameters. You can also export omnichannel subscription data.

Why is this important?

As omnichannel subscription volume grows across the Apple App Store, Google Play Store, and web, you need tighter control over which records you review, sync, and report on. These filters and export options make it easier to segment subscriptions and retrieve data from Chargebee for analysis or downstream workflows.

How can you use it?

Note: Omnichannel subscriptions is in early access. Submit a request to enable this feature.

To filter omnichannel subscription data, use either of the options:

1. In Chargebee Billing, open the omnichannel subscriptions list page and apply the purchased_at or updated_at filters.
2. For the List Omnichannel Subscriptions API request, use filter parameters such as purchased_at, updated_at, source, customer_id, omnichanel_subscription_id, id_at_source, omnichannel_subscription_item[status], or omnichannel_subscription_item[item_id_at_source].

To export omnichannel subscription data, go to Settings > Import & Export Data > Export Data in Chargebee Billing. See Export data for details.

Delete archived plays you no longer need

You can now permanently delete archived plays from your Chargebee Growth site. Previously, you could archive and unarchive plays, but archived plays stayed in the Archive section with no way to remove them. You can now delete an archived play from the row menu, confirm the action, and remove it from your workspace.

Why is this important?

Delete lets you remove plays you no longer need, so your archive stays focused on items you might still reference. Delete is different from archive, archive temporarily removes a play from active use, while delete permanently removes an archived play from the Plays list and the Archive section.

How can you use it?

1. In Chargebee Growth, go to the Plays module and open Acquisition, Expansion, or Retention, depending on where the play lives.
2. Open the Archive section. Find the archived play you want to remove, click the menu, and select Delete.
3. Click Confirm. Only archived plays show the Delete action.

Bulk export and archive plays

You can now select up to five plays from the plays list in Chargebee Growth and run bulk actions on them. Use Export CSV to download play reports or Archive to move completed plays to the Archive section, without opening each play individually. Bulk export is available for in-app offer, cancel page, and pricing table plays.

Why is this important?

If you manage many plays across Acquisition, Expansion, or Retention objectives, exporting reports or archiving completed plays one at a time does not scale. Bulk actions let you handle repetitive reporting and cleanup from the plays list.

How can you use it?

1. In Chargebee Growth, go to the Plays module and select Acquisition, Expansion, or Retention.
2. Use the Cancel Page, In-app Offer, or Pricing Table tab to view the desired plays.
3. Select up to five plays. Once five plays are selected, you cannot select more until you clear your selection.
4. When at least one play is selected, choose Export CSV or Archive, or click X button to deselect all and close the bar. 4a. Click Export CSV to bulk export reports. The download includes report data for each selected play type:

• In-app offer plays: customer-level and user-level reports.
• Cancel page plays: experience performance and offer performance reports.
• Pricing table plays: user-level sessions and visitor-level sessions reports. If you select plays across more than one play type, Chargebee delivers one CSV file per play type, bundled together in a ZIP file.

4b. Click Archive to bulk archive plays, review the modal content, and confirm. The selected plays move to the Archive section.

Broader read-only MCP coverage

Data Lookup MCP now covers more read-only domains, including entitlements, omnichannel subscriptions and one-time orders, orders, and scheduled changes (such as pending app-store subscription item changes).

Why is this important?

Support, RevOps, and mobile teams can ask AI clients about entitlement state, app-store subscriptions and orders, and upcoming scheduled changes without leaving Claude, Cursor, or ChatGPT.

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 (or a custom server that includes these tools).
3. Enable the entitlement, omnichannel, order, and scheduled-change tools you need.
4. Reconnect or refresh your AI client, then query those records in plain language.

Payment schedule installments no longer fall a day early on day-based billing

When you applied a payment schedule to an invoice on a site using day-based billing, the first installment could be dated to the day before the invoice date (for example, an invoice dated May 14 produced a first installment due May 13), and later installments could shift to the prior day of their respective months. Because the first installment appeared to be already past due the moment the schedule was applied, it could be treated as due right away. This is now fixed. The first installment takes the date and time at which you apply the payment schedule, and later installments align to the start of the day in your site's time zone on the correct calendar dates, so installment due dates no longer land a day early.

Fixed-amount coupons now apply in full to each subscription on a consolidated invoice

On a consolidated invoice, when the same fixed-amount coupon (set to apply on the invoice amount) was applied to more than one subscription, the discount was split across those subscriptions instead of being applied in full to each. For example, a fixed $100 coupon applied to two subscriptions produced a total discount of $100 (about $50 per subscription) rather than $100 for each subscription. This happened on consolidated invoices generated at renewal, while the first invoice applied the coupon correctly. This is now fixed. The coupon applies in full to each subscription that carries it, so the total discount reflects the full coupon amount for every subscription it is applied to.

Journal Entry Reconciliation report no longer shows FX gain/loss for transaction-currency postings

When your journal entries are posted in the transaction currency, the Journal Entry Reconciliation report incorrectly included foreign exchange (FX) gain and loss entries and reported a difference, even though no currency conversion applies in that setup. This is now fixed. When journals are posted in transaction currency, the report excludes FX gain and loss entries, so it reconciles cleanly without those extra rows or differences.

Multi-language support for quote form labels

Labels on the CPQ and CPQ HubSpot Quote Form previously remained in English even when your site's language pack supported other languages. This happened because translations for the quote form weren't included in the language. This is now fixed, and quote form labels translate correctly based on your configured language.

Quote to Subscription conversions now allowed till the date of expiry

Quotes accepted on the same day they expired couldn't be converted to a subscription from the quote page when users clicked Convert to Subscription, even if the quote was accepted before its expiry date and time. This is now fixed. Quotes accepted before their expiry date and time can now be converted to a subscription successfully, even when the acceptance and expiry occur on the same day.

Fixed: Event triggering for expired quotes

No event was triggered when a quote expired automatically. This affected the HubSpot Quote-to-Cash integrations and workflows. This is now fixed. Now, an event is triggered whenever a quote expires.

Custom field values on HubSpot quotes are now saved correctly

Non-string custom field values entered in the CPQ HubSpot quote form were being cleared despite clicking Save. This is now fixed. Users can now add custom fields of any data type, and the data remains saved after quote conversion.

Smart Routing now selects the correct payment gateway for quote acceptance

Smart Routing could select the wrong payment gateway when customers accepted a quote for a plan priced in a different currency than their preferred currency. This is now fixed. Payment gateway selection on quote acceptance now uses the plan's currency, consistent with the standard checkout flow.