Does Chargebee Work in China? Data Residency, ICP & Cross-Border Rules

Chargebee is cloud-only subscription-billing SaaS: your China customers' identities, subscription records, invoices and payment-method data live only in offshore AWS regions (US, EU or Australia) — none in mainland China — held abroad under PIPL, while moving the money needs a licensed China payment path. A compliance-first look at the residency, payment-licensing and ICP doors.

By the 21YunBox Compliance Team · Reviewed 2026-10-12 · Verified against Chargebee's own documentation

Does Chargebee work in China?

Chargebee loads in mainland China about as well as anywhere — but speed was never the question for a subscription-billing platform. Chargebee is cloud-only SaaS hosted only in offshore AWS regions (US, EU or Australia), with no mainland-China region, so your China customers' identities, subscription records, invoices and payment-method data are held abroad — a PIPL cross-border transfer (Articles 38–40).

The distinctive exposure is the money itself: a foreign billing platform is not a licensed China payment institution, so moving payments for mainland users must run on a licensed domestic payment path under China's Regulations on Non-bank Payment Institutions (State Council Order No. 768) — Chargebee orchestrates on top of that, it does not replace it. The compliance question is where the customer and payment data lives and who is licensed to move the money; a reachability check sees neither.

21YunBox is a compliance overlay and partner to the billing platform you already run — never a competitor. We map what your tenant holds, help you keep the regulated data on a lawful in-country path and route money through a licensed domestic payment path, and deliver any China-facing checkout or self-service portal ICP-filed and in-country. We never use or suggest circumvention; treat the specifics as a risk to confirm with counsel.

What Chargebee's own documentation says about China

Fact	Primary source
Chargebee hosts customer data only in offshore regions — none in mainland China. Chargebee's data-centre documentation states: “When creating a Chargebee account, you can choose one of three data hosting regions: AU, US, or EU,” and names the underlying AWS regions as US East (N. Virginia), EU (Frankfurt) and Asia Pacific (Sydney). No mainland-China region is offered.	Chargebee, “Data Centers” product documentation (chargebee.com), retrieved 2026-10-12
The hosting region is a data-residency choice, fixed to one of those offshore locations. Chargebee's documentation says “You may select a hosting region based on your data residency requirements,” stores both Live and Test site data in the selected region, and states that “To change the hosting region for an account after signing up, create a Support ticket.” None of the selectable regions is inside mainland China.	Chargebee, “Data Centers” product documentation (chargebee.com), retrieved 2026-10-12
A foreign billing platform is not a licensed China payment institution. China's Regulations on the Supervision and Administration of Non-Bank Payment Institutions (State Council Order No. 768, in force May 1, 2024) require an offshore non-bank institution that provides cross-border payment services to users inside China to establish a non-bank payment institution within China (Article 2), and require domestic transaction processing, fund settlement and data storage to happen inside China (Article 19). The money movement must run on a licensed domestic path; the billing platform sits on top of it.	Regulations on the Supervision and Administration of Non-Bank Payment Institutions, State Council Order No. 768, Arts. 2 and 19 — 21YunBox translation, retrieved 2026-10-12
Holding China customers' personal and payment data offshore is a regulated cross-border transfer. Customer identities, invoices and payment-method references collected from people in China are personal information; holding them in an offshore region is a cross-border transfer under PIPL Articles 38–40 (notice, separate consent, and a transfer mechanism). For a critical information infrastructure operator or high-volume handler, the Cybersecurity Law's Article 39 (formerly Article 37) requires personal information generated in China to be stored in the mainland.	Cross-Border Data Transfers under PIPL (Arts. 38–40) and Cybersecurity Law Art. 39 (formerly Art. 37) — 21YunBox compliance reference, retrieved 2026-10-12

Sources verified by the 21YunBox compliance team on 2026-10-12.

For a company running Chargebee to bill a mainland-China operation, the deciding question is not how quickly the checkout or the customer portal paints from Shanghai. It is where your data is allowed to live — and who is allowed to move the money — because Chargebee is the system of record for your China subscription revenue. It holds the identities of your China customers, their subscription and contract records, their invoices and billing history, the payment-method references tied to them, and the revenue those relationships represent. Chargebee is a cloud-only SaaS platform, hosted in offshore AWS regions with no region inside mainland China — so all of that is held and processed abroad. That makes this a compliance-risk question first, not a performance one.

Chargebee's own Data Centers documentation stating that when you create an account you choose one of three data hosting regions — AU, US, or EU — backed by AWS Asia Pacific (Sydney), US East (N. Virginia) and EU (Frankfurt), with no mainland-China region. — Chargebee's own Data Centers documentation: “you can choose one of three data hosting regions: AU, US, or EU,” backed by AWS US East (N. Virginia), EU (Frankfurt) and Asia Pacific (Sydney) — and “You may select a hosting region based on your data residency requirements.” None of the three is inside mainland China, and there is no mainland region to pick. Source: Chargebee — Data Centers documentation

Chargebee in China at a glance

What decides it	In Chargebee's own terms — and China's law
What it holds	The record of your China subscription revenue: your China customers' identities (names, emails, billing addresses, company and tax details), their subscription and contract records, their invoices and billing history, the payment-method references tied to each account, and the revenue those relationships represent.
Where it runs	Chargebee is a cloud-only SaaS platform. Its documentation offers three data hosting regions — AU, US or EU, backed by AWS Asia Pacific (Sydney), US East (N. Virginia) and EU (Frankfurt); the region is chosen at signup, and none is inside mainland China. Changing it later requires a support ticket.
Customer & payment-related PII	Your China customers' identities, invoices and payment-method references rest in whichever offshore region your account is assigned — a cross-border transfer under PIPL Articles 38–40, layered on the Article 13/23 notice-and-consent. For a critical information infrastructure operator or a high-volume handler, Cybersecurity Law Article 39 (formerly Article 37) requires personal information collected in China to be stored in the mainland.
The money movement — a licensing door	This is the half a speed test never sees. A foreign billing platform is not a licensed China payment institution. Under the Non-bank Payment Institutions regime (State Council Order No. 768), an offshore provider offering cross-border payment services to China users must establish a payment institution within China (Art 2), with domestic processing, settlement and data storage inside China (Art 19). The actual money movement for China customers needs a licensed domestic payment path; Chargebee orchestrates on top of it.
A China-facing checkout or portal	A public checkout, hosted payment page or self-service subscription portal served to mainland users is an internet information service, so it carries an ICP filing (备案) duty bound to a mainland hosting resource. A Chargebee-hosted page runs on offshore infrastructure, so it offers no ICP-filing path of its own.
Reachability is not the axis	Whether the checkout loads quickly from the mainland is operational, not the compliance question. What decides it is where the customer and payment data live, and who is licensed to move the money. 21YunBox helps you keep the regulated data in-country, route money through a licensed domestic path, ICP-file any public page, and deliver it compliantly — the 21YunBox Optimizer — in front of the Chargebee you already run.

What it actually holds — the record of your China subscription revenue

Chargebee is not a static asset like a font or a script; it is the operational core of your China recurring-revenue business, and it concentrates two kinds of exposure China’s law cares about. The first is personal and commercial data: the identities of your China customers — names, work and billing emails, billing addresses, company and tax details — together with their subscription and contract records, their invoices and billing history, and the revenue those relationships represent. The second — the half a reachability check never sees — is the payment dimension: the payment-method references and billing flows tied to each China account. Because Chargebee is a cloud-only SaaS platform hosted in offshore AWS regions, that record of who your China customers are and what they pay is held and processed abroad by default.

The doors: residency, the payment-licensing path, and ICP

The first door is data residency. The customer identities, invoices and payment-method references your Chargebee account collects from people in China are personal information under China’s Personal Information Protection Law, and holding them in an offshore region is a cross-border transfer (数据出境). The duty lands on you, the handler, not on Chargebee: Articles 13 and 23 require notice and a basis to collect the data, and Articles 38–40 require a transfer mechanism to send it abroad — a CAC security assessment, the CAC standard contract, or certification. And for a critical information infrastructure operator or a high-volume handler, the Cybersecurity Law’s Article 39 (formerly Article 37 — the 2025 Cybersecurity Law amendment, in force January 1, 2026, renumbered the data-localization article from 37 to 39, with its substance unchanged) requires personal information generated in China to be stored in the mainland, which an offshore account cannot satisfy.

The second door is the one that makes a billing platform different from an ordinary SaaS: the money itself. Collecting or processing payments from customers in mainland China is a licensed financial activity, and a foreign billing or subscription platform is not a licensed China payment institution. Under China’s Regulations on the Supervision and Administration of Non-Bank Payment Institutions (State Council Order No. 768, in force May 1, 2024), an offshore non-bank institution that intends to provide cross-border payment services to users inside China must establish a non-bank payment institution within China (Article 2), and domestic transaction processing, fund settlement and data storage must happen inside China (Article 19). In practice, the actual money movement for your China customers runs on a licensed domestic payment path, and the billing platform orchestrates invoices, subscriptions and dunning on top of it — it does not replace the licensed path. Treat the exact structure as a question to settle with counsel; the point is that where the money moves, and who is licensed to move it, is a door a speed test will never surface.

The third door is the ICP filing. If you publish a China-facing checkout, hosted payment page or self-service subscription portal to mainland users, you are running a public internet information service, and that turns on an ICP filing (ICP 备案) duty bound to a hosting resource physically inside the mainland. A Chargebee-hosted page runs offshore, so there is nothing on it to file against — tuning the stack does not create the mainland footing a filing needs.

A reachability check never sees this

Chargebee is not the kind of service that simply refuses to load in China — the exposure is quieter and more durable than a slow paint. Even if the checkout and the customer portal opened instantly, using them would still place your China customers’ identities and payment-method data outside the country, and would still leave the actual money movement running without a licensed domestic path. A reachability test answers “did the page come back?”; it is blind to where the customer and payment data come to rest, and to who is lawfully allowed to move the money. Where the data lives and who is licensed to move the money, not how fast the page arrives, is what China’s law responds to.

This is a risk map, not a verdict that Chargebee is “blocked” or “illegal” in China. Which duties bite your case turns on your entity, what your account actually holds, your role under Chinese law, how you collect payment, and who your customers are — worth settling the specifics with counsel before your China revenue depends on it.

The lawful path — map, localize, deliver

There is a compliant way to run subscription billing for a China operation, and it sits in front of the Chargebee your team already uses — no rebuild, no second tool, no migration.

First, map: our China team inventories what your Chargebee account holds — the customer identities, subscription and invoice records, and payment-method references — establishes where it is hosted (an offshore AWS region), the ICP status of any public checkout or portal, and the consent, residency and payment-licensing basis each flow relies on. We build the technical picture; the legal conclusions are settled with counsel.

Then localize/govern: we help you keep the regulated data — customer and payment-related personal information — on a lawful in-country path, obtain the Article 13/23 notice-and-consent, and route the actual money movement for China customers through a licensed domestic payment path rather than leaving it to run offshore and unlicensed. Localize means keeping the data and the money on an in-country, licensed path — never a route that ships them offshore anyway.

Then deliver: any public China-facing checkout, payment page or self-service portal is an internet information service, so it carries an ICP filing duty bound to mainland hosting and needs compliant, in-country delivery. 21YunBox stands that up — the 21YunBox Optimizer — in front of what you already run, so it serves your customers in China legally and compliantly. 21YunBox never uses or suggests circumvention of any kind — we keep in-country what the law says must stay, route the money through a licensed path, deliver the rest compliantly from inside the mainland, and never move personal information or payments across the border by stealth. Making an offshore account merely reachable is not the answer; keeping the regulated data in-country, running the money on a licensed path, ICP-filing the portal and delivering it compliantly is. 21YunBox is a compliance overlay and partner to the billing platform you already run, not a competitor to it.

Get a compliance assessment →

Related reading:

Frequently Asked Questions

Does Chargebee have a data centre in mainland China?

No. Chargebee's own data-centre documentation offers three hosting regions — AU, US and EU (AWS Sydney, N. Virginia and Frankfurt) — and none is inside mainland China; the region is chosen at signup and changing it requires a support ticket. So your China customers' identities, subscription records, invoices and payment-method data are held offshore, which is a cross-border transfer under PIPL Articles 38–40. The deciding question is where that data is allowed to live, not how fast the billing pages load. Treat the specifics as a risk to confirm with counsel.

Can a foreign subscription-billing platform take payments from customers in mainland China?

Not on its own. A foreign billing platform is not a licensed China payment institution, and under China's Regulations on the Supervision and Administration of Non-Bank Payment Institutions (State Council Order No. 768) an offshore provider offering cross-border payment services to users in China must establish a payment institution within China (Article 2), with domestic processing, settlement and data storage inside China (Article 19). The practical pattern is to run the actual money movement for China customers through a licensed domestic payment path and let the billing platform orchestrate on top of it — never a route that circumvents the licensing. Confirm your exact obligations with counsel.

What is the lawful way to run Chargebee for China, and what does 21YunBox do?

Keep the regulated data in-country, route the money through a licensed domestic payment path, and ICP-file and deliver any China-facing checkout or self-service portal in-country — in front of the Chargebee you already run, with no rebuild or migration. 21YunBox is a compliance overlay and partner to your billing platform, not a competitor: we map what your tenant holds and where it rests, help you localize the regulated data and the payment path, and deliver compliantly with the 21YunBox Optimizer. We never use or suggest circumvention of any kind. Get in touch to map your case.