Chargebee Release Notes

Payment Components

Payment Components is out of early access and generally available on all plans. More than 40 businesses are already processing live payments through it. You can use it to build a checkout that collects cards, digital wallets, direct debit, and local payment methods from a single component, without writing separate handling for each one. Because one integration covers every payment method Chargebee supports on a payment gateway, adding a payment method no longer means changing your checkout code. The payment step in Chargebee’s full-page layout for Checkout is now powered by Payment Components.

July brings the following enhancements to Payment Components:

1. Channel-specific payment methods. A new channels parameter lets you offer different payment methods by device channel, for example, cards on desktop and Payconiq on mobile.
2. Focus moves to the field that needs attention. When a payment form is ready, keyboard focus moves to the first empty field. When validation fails, focus moves to the first field with an error. This applies to payment methods with multi-field forms, including card, direct debit, iDEAL, Bancontact, UPI, and Netbanking eMandates.

How can you use it?

To get started, follow the quickstart. For scenarios that go beyond a basic integration, see use cases. If you use Card Components or the Payment Method Helper, we recommend moving to Payment Components. Both continue to be supported until further notice, but new advanced capabilities, including payment optimization and orchestration, will be available only in Payment Components and Checkout.

You can now accept Pix payments through EBANX and dLocal. One-time Pix covers checkout QR payments; recurring collection uses Pix Automático mandates so renewals can debit without a new QR code each cycle. Pix is Brazil's preferred real-time bank payment method for the BRL currency.

Why is this important?

Offering Pix helps you convert Brazilian customers who expect local instant bank payments, not only cards. Adding Pix on EBANX and dLocal matters when you already run those gateways for Latin America: you get Pix without standing up a separate Brazil-only processor. For failed Pix Automático renewals, Chargebee supports Real Time Payments Dunning (up to 3 retries within 7 days, separate from card dunning), so you can recover more recurring revenue before final invoice actions.

How can you use it?

To accept Pix through EBANX or dLocal:

Prerequisite: Confirm Pix (and Pix Automático for recurring) is enabled on your EBANX or dLocal merchant account.

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Payment Gateways, open EBANX or dLocal, and enable Pix.
3. Review Smart Routing so Pix traffic routes to the gateway you intend.
4. For failed Pix Automático renewals, configure Real Time Payments Dunning under Settings > Configure Chargebee > Dunning for Online/Offline Payments. Pix dunning is separate from card dunning: Pix allows up to 3 retries within 7 days (1 per day), and Chargebee optimizes retries in that window before applying your invoice and subscription final actions.

For full setup, currencies, flow details, and dunning behavior, see Pix via EBANX and Pix via dLocal.

You can now process ACH bank payments through the NMI payment gateway. ACH is a US bank-account direct debit payment method for United States Dollar (USD).

Why is this important?

This addition gives your US customers a lower-cost alternative to cards and often reduces card-related failures on renewals. If you already use NMI for cards, ACH on the same connection means you do not need another US ACH gateway. Choose this when your US volume justifies bank debit and you want one NMI stack for cards and ACH.

How can you use it?

To process ACH payments through NMI:

Prerequisite: Confirm ACH is enabled on your NMI account.

1. Log in to your Chargebee Billing site.
2. Open Settings > Configure Chargebee > Payment Gateways > NMI, and enable ACH.
3. Update Smart Routing so USD ACH payments can route to NMI where appropriate.

For full setup and collection behavior, see NMI and direct debit payments.

You can now collect BECS NZ direct debit and UPI payments through the Stripe payment gateway.

Why is this important?

1. BECS NZ is New Zealand's bank-account direct debit for New Zealand dollar (NZD) currency. It suits NZ customers who prefer debiting a bank account for subscriptions. Chargebee already offers BECS NZ via GoCardless; Stripe support gives you a second gateway choice so you can keep cards and NZD direct debit on one Stripe connection.

2. UPI is India's real-time bank payment method for INR (one-time and recurring, within Stripe's UPI limits). Choose Stripe UPI when Stripe is already your primary gateway for India—for example, you take cards on Stripe today and want UPI on the same connection without adding another gateway such as Razorpay or dLocal. If you already collect UPI through Razorpay or dLocal, those paths remain available.

How can you use it?

To enable BECS NZ or UPI through Stripe:

Prerequisite:

1. Confirm that BECS NZ or UPI is enabled on your Stripe account.
2. Then contact Chargebee Support to enable BECS NZ and UPI via Stripe in your Chargebee Billing site.

Once enabled, follow these steps to configure the payment methods in your Chargebee Billing site:

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Payment Gateways > Stripe, and enable the method you need (BECS NZ for NZD, or UPI for INR).
3. Under Smart Routing, assign Stripe for that method and currency.

For full setup, see BECS NZ via Stripe or UPI via Stripe.

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.

Once enabled, follow these configuration steps:

1. Log in to your Chargebee Billing site.
2. Open Settings > Configure Chargebee > Payment Gateways > Adyen, and enable Alipay and/or Klarna.
3. Confirm Smart Routing and payment method display for the countries and currencies you support.

Where they differ: Alipay is one-time only, so for subscription checkout enable one-time payment methods in Checkout & Self-Serve Portal and use Pay Now style collection for renewals. For details, see Alipay via Adyen and Klarna via Adyen.

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.

For PayPal configuration details, check our PayPal Commerce documentation.

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:

• Log in to your Chargebee Billing site.
• Go to Logs > Transactions.
• Select any transaction to open its details page.
• Review the lifecycle timeline on the right, from the first event to the most recent.
• 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:

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

Note: Gateway activity logs are retained for 60 days. For full details, check our Gateway Activity Logs documentation.

Why is this important?

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.

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.
5. Use the related resource links to move to the matching transaction, customer, or invoice.

Note: Gateway webhook logs are retained for 60 days. For more details, check our Gateway Webhook Logs documentation.

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.

For more details, check our Retries documentation.

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 customer[id] 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 customer[email], customer[first_name], and customer[last_name] 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 customer[id].
2. If the customer record does not exist, Chargebee creates it and records the purchase.
3. Optionally include customer[email], customer[first_name], and/or customer[last_name] to populate the new customer record.