Chargebee Release Notes

You can now offer seven local payment methods through your existing dLocal connection.

• GCash: wallet payments in the Philippines, in PHP. The customer approves the first payment in GCash, and later recurring payments use that enrollment.
• OVO: wallet payments in Indonesia, in IDR, with the same enrollment flow.
• NuPay: wallet payments in Brazil, in BRL, with the same enrollment flow.
• PicPay: wallet payments in Brazil, in BRL, with the same enrollment flow. Recurring charges are not available in production until dLocal finishes moving PicPay to its enrollment API.
• Mercado Pago: wallet payments in Brazil (BRL), Chile (CLP), Mexico (MXN), and Colombia (COP), with the same enrollment flow.
• Nequi QR: one-time QR payments in Colombia, in COP.
• Thai QR: one-time QR payments in Thailand, in THB.

GCash, OVO, NuPay, PicPay, and Mercado Pago are available in In-App Checkout, Full-Page Checkout, the Chargebee Self-Serve Portal, APIs, and Chargebee.js. A later charge for Nequi QR or Thai QR needs a Pay Now link.

Why is this important?

Offer customers local wallet and QR payment options through your existing dLocal connection, without setting up a separate gateway connection for these methods.

How can you use it?

Prerequisite: Ask dLocal to enable the method on your account, and connect dLocal in Chargebee. Enable that method's currency on your site before you enable the payment method.

• Log in to your Chargebee Billing site.
• Go to Settings > Configure Chargebee > Payment Gateways, and open your dLocal gateway.
• On Configure dLocal, enable the method, and click Apply. Chargebee adds a Smart Routing rule for that currency when none exists yet.
• If a rule already points to another gateway, open Manage Rules under Smart Routing and route the payment method to dLocal.
• Chargebee registers the dLocal webhook for you. You do not need to create that endpoint in the dLocal dashboard.

You can now offer six local payment methods through your existing Stripe connection.

• Bizum via Stripe: one-time payments in Spain, in EUR. The customer's phone number is required.
• Pay by Bank via Stripe: one-time open-banking payments in Finland, France, Germany, Ireland, and the United Kingdom, in EUR or GBP.
• PayNow via Stripe: one-time QR payments in Singapore, in SGD.
• PayTo via Stripe: one-time and recurring bank payments in Australia, in AUD.
• Pix via Stripe: one-time QR payments and recurring Pix Automático charges in Brazil, in BRL.
• PromptPay via Stripe: one-time QR payments in Thailand, in THB.

Why is this important?

Offer customers local bank and QR payment options through the Stripe connection you already use for card payments, without adding a separate gateway connection for these methods.

How can you use it?

• Prerequisite: Enable the payment method in your Stripe account.
• Log in to your Chargebee Billing site.
• Go to Settings > Configure Chargebee > Payment Gateways > Stripe, turn on the method, and click Apply.
• Open Manage Rules under Smart Routing, route that method's currency to your Stripe account, and click Save.

Each payment method's document covers the Stripe webhooks Chargebee needs for refunds and, for PayTo and Pix, for the final payment status.

You can now set up alerts that notify you when the prepaid credit balance of a subscription drops to or below a threshold you choose. Each alert applies to a subscription and a credit unit.

Why is this important?

Identify subscriptions that need a top-up before credits run out, so your team can remind customers in time.

How can you use it?

• Sign in to your Chargebee Billing site.
• Go to Usages > Alerts and select Create Alert.
• Enter a name and description for the alert.
• Select Credits under Alert Type.
• Set the alert threshold, choose which subscriptions it applies to, and select the delivery channel. See Creating an alert for the scope and delivery settings.
• Click Save Alert.

You can now create spend-based alerts that notify you when the accrued usage charges on a subscription reach a threshold.

Why is this important?

Earlier, you could set alerts on usage quantity only. Spend alerts help you monitor accrued usage charges, rather than usage quantity alone.

• Avoid bill shock. You can reach out to a customer or adjust their plan before rising usage turns into an unexpected invoice.
• Limit unpaid bills and fraud. You can spot unusual spikes early, such as unauthorised or runaway usage, before they grow into a charge that a customer disputes or doesn't pay.

How can you use it?

Spend alerts are in early access. Contact [email protected] to join the Early Adopter Program and enable this feature.

• Sign in to your Chargebee Billing site.
• Go to Usages > Alerts and select Create Alert.
• Enter an alert name and description.
• Select Spends as the Alert Type.
• Enter the spend threshold, select your preferred setting for the application of the alert, and select your preferred alert delivery channel.
• Click Save Alert.

You can now retrieve the payment schedule schemes on your site with a single API call. The List payment schedule schemes endpoint returns your schemes sorted by ID, newest first. You can filter the results by ID and last updated time.

Why is this important?

You can find scheme IDs and details in a single request, instead of retrieving schemes one by one. This makes it easier to choose the right scheme when you work with payment schedules.

How can you use it?

Send a request to with your site API key. Use (up to 100) and to page through the results, and use the and filters to narrow them. The list returns scheme-level details only. To get the schedules for a scheme, retrieve that scheme by its ID.

You can now map each Chargebee Growth survey reason to a Chargebee Billing cancellation reason code. When a customer cancels via a Retention offer, Growth sends the code corresponding to their answer to Billing. Before, every cancel carried the same code: . Several survey reasons can map to the same code. Reasons with no mapped code still send .

Why is this important?

Analyze cancellations by the customer's mapped survey reason instead of seeing every Growth cancellation grouped under 'Chargebee Retention.' This gives your Billing subscription history and churn reports more useful cancellation context.

How can you use it?

Prerequisite: Set up the codes in your Chargebee Billing site first. Learn more in Configuring reason codes.

• Log in to your Chargebee Growth site.
• Go to Experiences > Survey Reasons.
• Open a survey reason and select a Chargebee reason code.
• Save your changes.

Growth will send as the fallback code if the reason code has been disabled in Billing.

When Multi-Plan Subscriptions is enabled in Chargebee Billing, your customers can now add multiple plans to their subscriptions through the Self-Serve Portal. They can also view and edit subscriptions that already include multiple plans.

Why is this important?

The portal previously didn't support subscriptions with multiple plans. Customers can now manage these subscriptions themselves instead of contacting you.

How can you use it?

Multi-plan subscriptions on the Customer Portal are in early access. Contact [email protected] to join the Early Adopter Program and enable this feature.

Review your portal settings to ensure they provide the right level of access to your customers.

You can now try Payment Components before integrating. Use the playground to see how the component changes by country, currency, layout, device, and theme, and get the integration snippet for your setup.

Why is this important?

Compare payment layouts and themes before you start integrating, then use the generated snippet as a starting point for your chosen setup.

How can you use it?

• Open the Payment Components overview page.
• In the playground, switch country and currency; compare the accordion and tab layouts; and preview desktop and mobile.
• Apply a theme, then expand View Code to copy the snippet.

You can now enable Klarna via Stripe, Amazon Pay via Stripe, ACH via NMI, and cards and Venmo on PayPal Commerce directly in your Chargebee Billing site. Chargebee no longer has to enable these methods for you.

• Klarna via Stripe covers one-time payments and recurring payments in USD.
• Amazon Pay via Stripe is available for customers in the United States, in In-App Checkout, Full-Page Checkout, the Chargebee Self-Serve Portal, APIs, and Chargebee.js.
• ACH via NMI is US bank debit in USD, for one-time payments and recurring payments.
• Cards and Venmo on PayPal Commerce run on the same PayPal connection as PayPal wallet. Cards and Venmo use a PayPal Vault ID.

Why is this important?

You can offer these methods on the gateway connection you already use, and you can enable them without waiting for Chargebee Support.

How can you use it?

Prerequisite: Enable the method in your Stripe, NMI, or PayPal account before you turn it on in Chargebee.

1. Log in to your Chargebee Billing site.
2. Go to Settings > Configure Chargebee > Payment Gateways.
3. Open the gateway and enable the method.
4. Stripe: turn on Klarna or Amazon Pay, then click Apply.
5. NMI: turn on Direct Debit (ACH/eCheck), enter your company name, email, and phone, click Save, then click Apply.
6. PayPal: enable Cards, Venmo, or both.
7. For Klarna, Amazon Pay, and NMI ACH, open Manage Rules under Smart Routing, assign the gateway for that method and currency, then click Save.

You can now build Advanced Routing rules from the card itself. Conditions can use the 6-digit or 8-digit card BIN, card brand, card type (credit, debit, or prepaid), and issuing country.

Why is this important?

Route card payments to different gateways based on BIN, brand, type, or issuing country, instead of using one default gateway for every card.

How can you use it?

• Log in to your Chargebee Billing site.
• Go to Settings > Configure Chargebee > Payment Gateways > Advanced Routing.
• Click Create Rule.
• Add Card BIN, Card Brand, Card Type, or Card Issuing Country, choose the gateway, enter a rule name, and click Publish.

A co-badged card carries more than one network, such as Cartes Bancaires and Visa. When the card is collected through Adyen's Card Component and stored as a card token, Chargebee keeps the network your customer selects and uses it for the first charge and for recurring payments.

Why is this important?

For a card with more than one network, preserve the customer's selected network for recurring charges as well as the first payment.

How can you use it?

No additional setup is required when co-badged cards are already enabled for Adyen.

If you process payments through CyberSource, Chargebee can sign and encrypt those gateway requests with message-level encryption (MLE). Chargebee also warns you when an uploaded certificate is nearing expiry.

Why is this important?

CyberSource is replacing HTTP signatures with message-level encryption, and Chargebee signs requests the same way so those payments keep working. The expiry warning gives you time to replace a certificate before it lapses.

How can you use it?

Chargebee turns MLE on per site, after CyberSource has enabled it for your account and both certificates are on file. It is not switched on for every CyberSource account at once.

In your Chargebee Billing site, go to Settings > Configure Chargebee > Payment Gateways > CyberSource.

Upload both P12 certificate files. One encrypts the requests Chargebee sends, and the other decrypts CyberSource's responses.

After Chargebee enables MLE for the site, new gateway requests use those certificates. Watch the certificate-expiry warning on the gateway configuration and replace a certificate before it expires.

You can now retrieve e-invoices and their related documents directly through the API, instead of only as a status on invoices and credit notes. Chargebee also sends dedicated webhook events when an e-invoice is created or updated.

Why is this important?

Get e-invoice status and details directly, without checking the parent invoice or credit note, and react to e-invoice changes in real time through dedicated events.

How can you use it?

To start receiving the e-invoice webhook events, contact Chargebee Support to enable them for your site.

If your site uses AvaTax for Sales, you can now update the address lines, city, state, and zip on an invoice while its Avalara document status is Uncommitted, as long as the re-estimated tax stays the same.

Why is this important?

This lets you correct minor address details on recent invoices without voiding and recreating them, while still protecting against unexpected changes to calculated tax.

How can you use it?

To update the address on an invoice:

• In your Chargebee Billing site, go to Invoices and open the invoice.
• Click Update Invoice Address.
• Edit the address lines, city, state, or zip, and save.