**Artifact** from Bead: Business Model And Strategy · [canonical source](https://redfish.acequia.io/guerin/.agents/fa3b0dc9-9dc9-479d-b40a-d6d5400ae313/2026-06-11/artifacts/china-market-entry-report.md) · session 2026-06-11 · discussion: Talk: Business Model And Strategy
Research report, June 2026. Produced for the business-model-and-strategy bead (`fa3b0dc9-9dc9-479d-b40a-d6d5400ae313`). Multi-source web research; load-bearing claims verified across ≥2 independent sources. **Research-grade, not legal advice.** **Scope assumed:** small US company; web-based emergency-management sand-table/simulation SaaS, agent-based modeling tools, real-time geospatial viewers, developer platform; no hardware, no initial PRC presence. **Terminology correction up front:** in MIIT's VATS catalog, the **ICP license is category B25 ("internet information services")** and the **EDI license is category B21 ("online data processing and transaction processing")**. Subscription SaaS is generally treated as B25 territory (platform/marketplace features push into B21). Sources: [AppInChina B25 guide](https://appinchina.co/blog/the-complete-guide-to-chinas-icp-license-b25/), [AppInChina B21/EDI guide](https://appinchina.co/edi-electronic-data-interchange-b21-online-data-processing-and-transaction-processing-services/), [Morrison Foerster](https://www.mofo.com/resources/insights/240418-china-pilots-relaxed-foreign-ownership).
## 1. ICP Bei'an filing vs commercial ICP license (B25) vs EDI license (B21) | Scenario | Requirement | |---|---| | (a) Serve a website into China from **offshore servers** | **Nothing.** ICP obligations attach to China-hosted infrastructure only. No filing or license legally required — but no protection from blocking/throttling either. ([MS Advisory](https://msadvisory.com/icp-license-china/), [QPSoftware](https://qpsoftware.net/blog/icp-license-basics), [Zscaler](https://www.zscaler.com/compliance/china-faq)) | | (b) **Host inside China**, non-commercial | **ICP Bei'an filing** (备案) with MIIT via the hosting provider. Free; ~20–30 working days; requires a **Chinese business license** — a non-resident foreign company cannot file directly. ([MS Advisory](https://msadvisory.com/icp-license-china/), [AppInChina](https://appinchina.co/blog/the-complete-guide-to-chinas-icp-filing/)) | | (c) **Charge Chinese subscribers** from a China-hosted service | **Commercial ICP license (B25)** on top of the filing. 60–90 working days; typically RMB 1M registered capital; ~US$5k–15k all-in via agents. ([MS Advisory](https://msadvisory.com/icp-license-china/), [AppInChina](https://appinchina.co/how-can-i-get-an-icp-license-for-china/)) | **Nuance:** charging Chinese subscribers from *offshore* does not itself require an ICP license — the requirement keys to operating the internet service *within* China. Cross-border selling is the loophole the whole "offshore model" lives in (§2). **Who can hold a B25/B21:** - Baseline: foreign ownership in most VATS incl. B25 capped at **50% (JV required)**; in practice almost no foreign JVs ever got B25 — hence the VIE structure. ([China Briefing](https://www.china-briefing.com/news/china-internet-business-licenses-foreign-companies/), [Wikipedia](https://en.wikipedia.org/wiki/ICP_license)) - **April 8, 2024 MIIT pilot:** WFOEs registered in **Beijing, Shanghai (Pudong + Lin-gang), Shenzhen, Hainan** may hold **B11/B12/B14/B21 (all service types), and B25 limited to two subcategories**: "information release platform and transmission services" (excl. news/publishing/audiovisual/cultural) and "information protection and processing services." Infrastructure must be in the pilot area; services can then be offered nationally. ([Morrison Foerster](https://www.mofo.com/resources/insights/240418-china-pilots-relaxed-foreign-ownership), [China Briefing](https://www.china-briefing.com/news/china-to-relax-foreign-ownership-limits-in-value-added-telecommunication-services/)) - **Thin implementation:** as of 28 Feb 2025, only **13 foreign-invested companies** approved under the pilot. ([DaHui Lawyers](https://www.dahuilawyers.com/en/news-insights/chinas-elimination-of-foreign-investment-restrictions-in-telecoms-services-under-pilot-policy-comes-to-fruition/), [Light Reading](https://www.lightreading.com/regulatory-politics/china-approves-13-companies-for-pilot-program-to-open-its-telecom-market)) - **Caveat:** the pilot circular has an explicit "exit ramp" (suspension for violations / cybersecurity-supervision failures). Whether a simulation SaaS fits the pilot's two permitted B25 slices is **untested — needs PRC counsel**.
## 2. Pure cross-border (offshore) SaaS: legality and reality **Legal:** no PRC law prohibits a Chinese person or company from purchasing an offshore SaaS subscription; no ICP requirement applies to offshore-hosted services. ([Harris Sliwoski "SaaS in China: The 101"](https://harris-sliwoski.com/chinalawblog/saas-in-china-the-101/), [Harris Sliwoski foreign-server option](https://harris-sliwoski.com/chinalawblog/selling-software-as-a-service-saas-in-china-the-foreign-server-option/)) **In practice:** - **Great Firewall:** offshore connections "can and will be blocked with no prior notice"; even unblocked, cross-GFW traffic suffers latency/packet loss — material for real-time geospatial viewers and WebSocket-heavy sand-table apps. HK/Singapore POPs help latency, do nothing against blocking. - **Fapiao:** Chinese corporate buyers need an official VAT invoice a foreign company cannot issue. Standard workaround: a **Chinese reseller** contracts locally in RMB, issues fapiao, withholds taxes, remits offshore. Individuals/small teams paying by wallet/card usually don't need fapiao → pure cross-border works better B2C/prosumer than B2B. ([Harris Sliwoski](https://harris-sliwoski.com/chinalawblog/saas-in-china-the-101/), [ADG China](https://www.adgchina.co/china-insights-resources/unlock-your-china-software-sales-is-your-reseller-network-holding-you-back)) - **SOEs** are effectively prohibited from offshore-hosted SaaS (policy practice per Harris Sliwoski + Document 79 direction, not a single citable statute). - **Onshore trade-off:** performance + procurement acceptability, at the cost of entity, licensing-or-partner, and Chinese-government access rights to the server.
## 3. Entity options - **WFOE:** no statutory minimum capital for service WFOEs (subscribed capital paid within 5 yrs under 2024 Company Law); practical US$30k–150k. Timeline 6–10 weeks once documents legalized; RMB 80k–350k first-year via agents. Gets bei'an, local contracting, hiring, fapiao — **not** B25 outside the pilot zones. ([FDI China](https://fdichina.com/blog/china-wfoe-formation-2025-guide/), [China Briefing](https://www.china-briefing.com/news/setting-up-a-wfoe-in-china-complete-guide/), [Acclime](https://china.acclime.com/guides/wholly-foreign-owned-enterprise-wfoe/)) - **Local reseller/distributor (no entity):** minimum-friction B2B answer; reseller is legally treated "as if it is the developer" (liability concentrates there → good resellers are picky); margin loss; channel dependence. - **Licensed-partner hosting ("Azure-China pattern"):** license the platform to a Chinese company holding the ICP/EDI license who operates the China deployment for royalties — the Microsoft/21Vianet, AWS/Sinnet model; works at small scale as the "license model." ([Harris Sliwoski](https://harris-sliwoski.com/chinalawblog/saas-in-china-the-101/)) - **Hong Kong entity:** ~US$1–2k, days-to-weeks; Asia banking, wallet-program onboarding, holding vehicle for a later WFOE. **No mainland regulatory status** (no bei'an/ICP/fapiao); HK is outside the GFW and the mainland data-law perimeter.
## 4. Data laws (CSL / DSL / PIPL) and the geospatial overlay - **PIPL applies extraterritorially** from subscriber #1 (processing PI of people in China to serve them). 2024 Guangzhou Internet Court decision confirmed reach + **separate consent** for cross-border transfers. ([IAPP](https://iapp.org/news/a/first-case-on-pipl-s-extraterritorial-scope-highlights-key-compliance-priorities), [Paul Weiss](https://www.paulweiss.com/insights/client-memos/chinese-court-releases-landmark-decision-on-requirements-for-cross-border-transfer-of-personal-information-under-the-pipl)) - **Network Data Security Management Regulations (eff. Jan 1, 2025):** foreign handlers in PIPL scope must **designate an organization or representative in China** and report to CAC. ([Mayer Brown](https://www.mayerbrown.com/en/insights/publications/2024/12/prc-network-data-security-management-regulations), [China Briefing](https://www.china-briefing.com/news/china-issues-new-regulations-on-network-data-security-management-effective-january-1-2025/)) Practical enforcement against small foreign SaaS with no PRC assets is minimal; real exposure is blocking + customer compliance objections. - **CSL localization** binds CIIOs — you won't be one, but emergency-management *customers* plausibly are → localization drags into deals contractually. - **Cross-border transfer, post-March-2024 relaxations** ([Greenberg Traurig](https://www.gtlaw.com/en/insights/2024/3/china-relaxes-requirements-for-cross-border-data-transfers), [IT Consultis](https://it-consultis.com/insights/china-cross-border-data-transfer-2024), [Benesch](https://www.beneschlaw.com/resources/china-officially-promulgates-new-cross-border-data-transfer-requirements.html)): **exempt** below 100k individuals/yr non-sensitive PI (+ contract-necessity, HR, emergency exemptions) — a small SaaS's subscriber data almost certainly rides these; SCC filing 100k–1M; **CAC security assessment** for ≥1M, ≥10k sensitive, any **"important data"** (presumed NOT to apply unless notified — major 2024 de-risking), any CIIO transfer. FTZ negative lists (Hainan, Tianjin, Beijing, Shanghai) free remaining data. - **Geospatial overlay — the real product-specific exposure:** - **Surveying and Mapping Law** (2017 rev.): collecting, **storing, transmitting, processing** geographic data restricted to licensed entities; foreign entities only via Chinese-foreign JV with approval. ([Wikipedia](https://en.wikipedia.org/wiki/Restrictions_on_geographic_data_in_China), [Lexology](https://www.lexology.com/library/detail.aspx?g=9f755dba-12a6-47b5-8b47-c16200cb6d58), [Intellias](https://intellias.com/map-compilation-for-china-challenges-and-ways-to-overcome-them/)) - **Internet map services** require a qualification foreign providers cannot hold; 2016 Map Management Regulations require internet-map data **stored on servers inside China**; published China maps must use **GCJ-02**; only ~a dozen licensed firms may do WGS-84↔GCJ-02 conversion. Penalties to RMB 500k + criminal exposure. - **Practical posture:** offshore viewers rendering the customer's own data or global basemaps are commercially tolerated (the Google/Esri pattern), but ingesting/storing/republishing China-territory geodata — especially emergency-management layers (infrastructure, hazards, response assets = "important data" candidates) — is squarely restricted once onshore, and creates customer-side legality questions even offshore. Standard pattern: licensed-partner basemaps (AutoNavi/Amap, Baidu, Tianditu) + GCJ-02 + no export of China-collected geodata.
## 5. Payments - **Stripe:** does not onboard mainland businesses, but a US Stripe account accepts **Alipay, WeChat Pay, UnionPay** from Chinese customers, settling USD. Recurring support on Chinese wallets is limited — many fall back to annual invoicing or UnionPay card. ([Stripe](https://stripe.com/gb/payments/chinese-payment-methods)) - **Cross-border wallet programs:** Alipay via **Antom/Alipay Global**, WeChat Pay via Tencent's cross-border program (usually through an aggregator); customer pays RMB, you settle USD/EUR/HKD; requires overseas entity + KYC. ([Antom](https://global.alipay.com/docs/ac/web/intro)) - **Merchant of record (lowest effort):** **Paddle** sells into China (cards incl. UnionPay, PayPal, Alipay with approval) and absorbs tax/compliance/FX — the realistic Tier-0 answer. ([Paddle](https://developer.paddle.com/concepts/sell/supported-countries-locales/)) - **Onshore RMB acquiring** (native wallet merchant accounts, fapiao) requires Chinese entity + bank account + ICP-filed domain. Repatriation via service fees/royalties (SAFE + tax clearance) or dividends (10% WHT to US parent under treaty). - **Currency:** RMB not freely convertible; individuals have US$50k/yr FX quota — the licensed cross-border rails exist precisely to make consumer payments clean.
## 6. Tax (cross-border, US company, no PE) - **VAT 6%**, withheld by the Chinese payer. New **VAT Law in force Jan 1, 2026** codifies place-of-consumption + withholding-agent mechanics for overseas digital providers — you don't register; the customer withholds. ([PwC](https://taxsummaries.pwc.com/peoples-republic-of-china/corporate/other-taxes), [DLA Piper](https://www.dlapiper.com/en/insights/publications/2026/01/key-changes-in-the-new-implementation-regulations-of-the-china-value-added-tax-law), [Hawksford](https://www.hawksford.com/insights-and-guides/china-new-vat-law-compliance)) - **Surtaxes** (urban construction + education, ~12% *of the VAT*) are not levied on VAT withheld on overseas service sales per PwC; some payers withhold anyway — budget ~0.4% noise. - **Income tax:** royalty characterization → **10% WHT** (US-China treaty); pure service fee with no PE → no CIT under treaty, but bureaus push SaaS toward royalty. Net practical haircut on a cross-border B2B contract: **~6% VAT + 0–10% WHT** (gross-up pricing). - B2C via MoR: the MoR absorbs the indirect-tax problem.
## 7. Emergency-management / government / mapping / US-side controls - **Document 79 ("Delete America," Sept 2022) + xinchuang:** government/Party then SOEs under quarterly-reported mandates to replace foreign software with domestic. China is not a WTO-GPA member; buy-domestic preferences in procurement. **Government/SOE emergency-management buyers ≈ a non-market for a US SaaS vendor in 2026.** Viable wedge: license the engine/IP to a Chinese partner who ships it as a domestic product (accepting IP-leakage risk). ([WSJ via The Asia Group](https://theasiagroup.com/wp-content/uploads/2024/03/WSJ-Mar-7-China-Intensifies-Push-to-%E2%80%98Delete-America-From-Its-Technology.pdf), [USCBC](https://www.uschina.org/articles/understanding-chinas-xinchuang-initiative/), [trade.gov](https://www.trade.gov/country-commercial-guides/china-selling-public-sector)) - **EM data sensitivity:** hazard/infrastructure/response data are prime "important data" / state-secret candidates; an offshore sand-table holding live Chinese incident data puts *the customer* in legal jeopardy. Serious public-safety deals will require onshore deployment and handling a foreign vendor cannot satisfy. - **US-side controls:** SaaS access by Chinese persons can be an EAR "deemed export"; mass-market encryption (5D992) mostly fine but 2025 rules tightened some 5A992/5D992 to China; **screen every Chinese customer** against Entity List (~600+ Chinese entities), Military End-User list — EM/public-safety buyers are disproportionately MEU-adjacent. ([BIS](https://www.bis.gov/regulations/ear/734), [Sidley](https://www.sidley.com/en/insights/newsupdates/2025/01/new-us-export-controls-on-advanced-computing-items-and-artificial-intelligence-model-weights))
## 8. Minimum-viable ladder | Tier | What you do | Cost | Timeline | Unlocks / limits | |---|---|---|---|---| | **0 — Pure cross-border** | Offshore hosting; MoR (Paddle) or Stripe + Alipay/WeChat/UnionPay; PIPL-lite hygiene (privacy notice, separate consent, stay under 100k exemption); Entity List screening | ~$0 setup; MoR ~5% of revenue | Days | Individuals/prosumers/private SMEs. No fapiao; GFW risk; no gov/SOE. **Do not ingest/store China-territory geodata.** | | **1 — HK entity + cross-border rails** | HK Ltd + banking; Antom/WeChat cross-border merchant accounts; optional HK/SG POP; resellers for B2B fapiao; appoint China data rep if scaling | ~$2–10k + $3–5k/yr | 2–6 weeks | Better wallet onboarding, RMB invoicing, Tier-2 holding vehicle. Still offshore: same GFW + procurement limits. The reseller matters more than the HK shell. | | **2 — WFOE + bei'an + licensed-partner hosting** | Service WFOE (in a pilot city to keep Tier 3 open); bei'an domain; Alibaba Cloud/Azure China; commercial ops via reseller or ICP-licensed partner | ~$15–50k yr-1 + $10–20k/yr | 3–6 months | In-country performance, fapiao, local support, localization story. Monetization runs through the partner; gov/SOE still closed; geodata needs licensed map partners + GCJ-02. | | **3 — Own B25/B21 via pilot zones (or ≤50% JV)** | Pilot-zone WFOE applies for B25 subcategories or B21; infra in pilot area; full self-operated SaaS nationally | ~$50–150k+ (incl. RMB 1M capital expectation) | 6–18 months | Your license, URL, billing. Pilot exit-ramp risk; subcategory fit untested; JV is the only route to actual map-service qualifications. | **Realistic minimum, June 2026:** Tier 0 (Paddle/Stripe + Alipay cross-border + export screening) costs ~nothing and is legal both sides for private-sector customers; add a Chinese reseller when a B2B deal needs fapiao; treat Tier 2 as demand-driven; treat gov/SOE EM sales and China-geodata hosting as out of reach without a Chinese licensing partner fronting the product. **Key uncertainty flags:** (1) pilot-zone B25 subcategory fit for simulation SaaS — untested; (2) recurring billing on Chinese wallets — feature-level, changes often; (3) "important data" classification of EM/geospatial layers — catalogs still being issued; (4) possible VATS-pilot geographic expansion — watch MIIT; (5) SOE-offshore-SaaS prohibition is well-attested practice, not a single statute.
## References (bead cross-links) - Bead 9f755dba · [canonical](https://redfish.acequia.io/guerin/.agents/9f755dba-12a6-47b5-8b47-c16200cb6d58/) (no page yet)