Text version of this lessonExpand
A domestic business license can solve part of the launch path, but it does not automatically solve cross-border payment or overseas platform review. Decide whether it is the main entity, supporting proof, or a temporary bridge.
The previous lesson handled one adjacent branch: whether an overseas entity is relevant when the earliest blocker is getting paid, payouts, KYC, public merchant identity, or year-one upkeep. It left an overseas entity mission and readiness sheet, and it can also conclude that filing should wait while evidence is collected.
That record did not decide whether a domestic license can carry supplier contracts, invoices, China-side banking, tax rhythm, or public storefront identity. It did not prove payment approval or that an overseas entity is required. A payout is the path that moves settled money from a payment provider to a receiving account; it is not an approval promise.
Return to the same 20oz tumbler. If the supplier contract, first-batch payment, invoice title, Contact / Refund pages, or bank record cannot explain who is responsible, it remains a launch hypothesis, not an order or settlement result. Do not look for another jurisdiction yet; write down which part the domestic entity carries and which part it cannot replace.
Enter this lesson only when that China-side responsibility chain is the current blocker. The output is a domestic entity boundary sheet, not a conclusion that registration is complete.
Check which parts a domestic entity can actually cover
A common mistake is assuming a business license means the cross-border entity problem is done. Payment, settlement, ads, tax, and public store information still need to match.
This lesson places the domestic entity inside the launch path: which accounts it can support, which steps need another entity, and which records must stay consistent.
Decision lens for this lesson
- Operating entity: The identity that carries account registration, payment, tax, and contract responsibility.
- Fit boundary: What this entity can and cannot support across accounts, payments, tax, and review.
- Record consistency: Company name, address, responsible person, store policy, and payout information should not conflict.
Lesson output: domestic entity fit and boundary sheet. Use this output to decide whether the lesson is truly complete.
Turn "entity" into a responsibility chain
In this article, an entity is the company, sole proprietor, or person named on a contract, account, or public page for a specific responsibility. When a supplier, payment provider, buyer, or platform asks who is responsible, that name should lead to a real person and a usable record. One store can have a China-side purchasing entity, payment-account entity, public merchant identity, and return handler. They may differ, but each difference needs an explainable role.
An entity role only asks what job the domestic license performs right now. This article begins from the main operating entity as a reading baseline. It does not recommend that every seller treat the China entity as the main operating entity. Start by checking whether one license can carry purchasing, contracts, business banking, and team work. Then assess payout, payment, and overseas responsibility separately when it cannot.
- Write four facts: who signs supplier contracts and pays for purchasing, whose name is on the payment account, whose name buyers see on policy pages, and who handles returns and refunds.
- Read what the domestic entity can cover and what it cannot cover. A covered domestic task does not mean the payment route or overseas responsibility is ready.
- If the domestic entity only supports purchasing or acts as supporting proof, use that role when reading the boundary table. Do not force it to explain the full operating responsibility.
- The text provides a complete reading route on its own. Turn the four facts into a boundary sheet only when you are ready to organize your own records.
The role you assign to the domestic entity only says which part it handles first. It does not automatically explain every entity, payment, or public-identity question. Even when it seems to cover a lot, list what it is still not enough to solve.
You do not need a better-sounding role next. Put the same license into purchasing, payment, team finance, and storefront disclosure, then see which evidence is missing in each scene.
How this connects: entity choice affects payment and overseas structure
A domestic license is not just “having a business record.” It affects payment review, tax explanation, dispute handling, and whether an overseas entity is needed later.
- Entity route: overseas company registration to decide when a domestic entity is not enough and when early registration is unnecessary.
- Payment route: payment gateway setup to keep entity records, KYC, and payout path in one evidence table.
First decide what role the domestic entity plays in your launch path
A business license is not a comfort document or a universal pass. Place it inside payment, supply chain, tax, and public store disclosure: is it your main operating entity, the China-side purchasing entity, supporting proof, or a temporary bridge while you validate demand?
| Use case | Fields to confirm | What goes wrong if you assume |
|---|---|---|
| China-side purchasing and contracts | Entity name, business scope, invoices, and business bank account | Purchasing, reimbursement, and bookkeeping become hard to explain later |
| Payment or platform review | Whether the target gateway accepts this entity and whether storefront disclosure matches | Documents look complete, but payment setup can still be blocked |
| Cross-border business boundary | How overseas entity, payout, tax filing, and refund responsibility work together | The China license gets misused as an answer to overseas compliance or payout requirements |
Completion standard
You can write what the domestic entity solves, what it does not solve, and
whether an overseas entity or payment-path change is needed next. If your
answer is only "register one first," this step is not complete.
Early action boundary table: which early moves a domestic entity can support
A domestic China business license is useful, but it is not a universal answer. A better framing is that it can organize the China-side operating chain while overseas checkout and target-market responsibility still need separate proof. Beginners usually make one of two mistakes: thinking no license means nothing can move, or thinking one license means payment and ads are ready. The right question is which move you are trying to push next.
| Early move | The domestic entity can cover | It cannot cover | Next route |
|---|---|---|---|
| Supplier contract and first purchase | Purchasing responsibility, invoice title, business payment, cost archive, and supplier communication records. | Overseas refund responsibility, target-market tax position, payment entity, or support promise. | If only purchasing is blocked, repair domestic records first. If live checkout is next, move to payment gateway and overseas entity work. |
| Ad account and platform proof | Company name, address, assigned lead, business scope, contracts, and basic diligence records. | Business Portfolio control, ad billing path, domain verification, Pixel/CAPI asset control, or recovery access. | If the issue is ad asset control, move to Meta or Google asset lessons. Do not use the license to hide permission problems. |
| Policy pages and merchant identity | Who operates, who supports, who handles returns, who keeps records, and what the China-side contact path is. | Contradictory return address, billing descriptor, overseas warehouse, privacy contact, and domestic entity. | If public records are not explainable, go back to policy and compliance pages before launch QA. |
| Checkout, payout, and payment review | One operating proof, plus purchasing proof, address records, and domestic account boundaries. | The local company, local bank, actual-operations proof, or overseas tax boundary required by the target payment path. | If stable overseas checkout is the goal, the domestic entity is only one proof item. Next move into payment gateway or overseas entity lessons. |
How to use this selector
Write the current move, what the domestic entity can cover, what it cannot cover, and the evidence to keep. If the uncovered column already affects launch, do not mark entity readiness complete. A domestic entity can make China-side operations cleaner, but overseas payment access, buyer refund responsibility, and target-market compliance need separate judgment.
Name mismatch: payment, ads, invoices, and disputes all check it
This is not about making the folder look tidy. In real operations, names must match. Buyers, payment paths, ad platforms, suppliers, and finance records do not only ask whether you have a business license. They ask who is responsible for this store, this money, this invoice, and this refund.
| Business area | How the names mismatch | What gets blocked | Repair first |
|---|---|---|---|
| Payment and payout | Policy pages show the domestic company, the payment account uses a personal name, and the bank beneficiary is another company. | Reviewers ask who is responsible for transactions and refunds; payout, refund, and chargeback explanations become harder. | Write a payment role sheet: storefront merchant, payment account, bank beneficiary, and refund lead. |
| Ad account proof | The license, Business Portfolio, ad billing, domain, and Pixel/CAPI assets belong to different people or entities. | Account recovery, risk review, and asset handover can stall; paid traffic may not prove who controls the assets. | Put ad asset control, billing method, domain verification, and license screenshots into one asset sheet. |
| Invoices and tax | Supplier contract, invoice title, business payment, business scope, and real SKUs tell different stories. | Cost records, reimbursement, filing, and supplier diligence become patchwork, and the team cannot review real profit cleanly. | Line up core SKUs, contract entity, invoice title, payment account, and business scope in one record-chain table. |
| Refunds and disputes | Contact email, return address, billing descriptor, payment entity, and public merchant identity do not show who is responsible. | Buyer trust drops and support cost rises; platforms may reject explanations during refunds, chargebacks, or privacy requests. | Align merchant identity and responsibility across Contact, Refund, Privacy, order emails, and support templates. |
Do not just collect documents. Record what each document proves
Business-license work often turns into "we have a folder of files." Payment review, platform review, bank setup, supplier contracts, and policy-page checks are not asking whether you have many files. They ask whether those files explain the same operating entity.
Build one entity evidence sheet from day one. For each document, record the field, purpose, reviewer, and launch risk. Later, when payment setup, policy pages, ad account review, or tax support comes up, you do not need to rebuild the story from chat history.
| Document | Fields to record | What it proves | Where mismatch blocks you | Where to store it |
|---|---|---|---|---|
| Business license | Unified social credit code, entity name, legal representative, domicile, business scope, issue date. | Who the China-side operator is and what domestic purchasing, contracts, and activities it can support. | Payment review, ad account business proof, supplier contracts, merchant identity on policy pages. | Entity evidence sheet, file version, and latest review date. |
| Address evidence | Registered address, actual operating address, lease or use proof, reachable contact. | The entity has an explainable address path for bank, tax, and platform checks. | Bank setup, tax checks, platform diligence, Contact / Privacy pages. | Address folder marked as registered address, return address, or support address. |
| Banking and payout records | Account status, account name, bank name, currency, beneficiary, whether used for ads or payouts. | Where money leaves, where it returns, and who is responsible for the cash path. | Payment gateway, payout, ad billing, refunds, and reconciliation. | Cash account sheet, aligned with the 3-account model from the finance lesson. |
| Tax and invoice records | Taxpayer type, filing cycle, invoice title, invoice lead, first filing reminder. | The license is not idle and ongoing tax / contract paperwork has an lead. | Supplier settlement, contract archive, annual filing, team finance responsibility. | Tax calendar and contract / invoice folder. |
| Store policy entity information | Contact, Refund, Privacy, and Terms page URLs, operating entity, support inbox, return handler. | Buyer-facing merchant identity and backend records tell the same responsibility story. | Launch QA, payment review, refund disputes, privacy, and support responsibility. | Policy-page version log with publish date and assigned lead. |
| Supplier contracts and SKU list | Supplier name, contract entity, SKU, category, invoice title, payment method, delivery responsibility. | How the domestic entity supports sourcing and cost records, not that overseas payout is solved. | Business scope, product claims, purchase payment, after-sales compensation, inventory responsibility. | Supply-chain folder, next to SKU test records. |
Minimum acceptance standard: completion is not "all files are saved." It is one sheet that explains what the domestic entity covers, who is responsible for overseas payout if needed, how the store displays the merchant, and which record to inspect when payment or refund responsibility is questioned.
First Ask Why You Need a Domestic License
Not every cross-border seller needs to start with a domestic China entity. But if you need domestic procurement, formal contracts, invoicing, company-bank operations, or stronger compliance records for counterparties, a local license can materially improve your operational flexibility.
Most Common Use Cases
- Domestic sourcing and contracts: easier cooperation with suppliers, warehouses, and service providers.
- Invoicing and company-bank settlements: more suitable for standardized procurement and financial management.
- Documentation and verification: helps when platforms, payment providers, or partners ask for stronger operating records.
- Team-based operations: clearer role and money boundaries once the business moves beyond personal testing.
Do Not Treat a Domestic License as a Universal Fix
- A China entity does not automatically solve overseas payment limitations such as Shopify Payments availability.
- Registration is only the start: the long-term burden comes from tax filing, account management, and compliance upkeep.
- If your core objective is overseas payment capability, you still need to plan domestic and overseas structures together.
Individual Business or Limited Liability Company?
This is usually the first real decision. There is no universally best answer. If you are still validating the business in a lightweight way, an individual business can be more efficient. If you expect long-term operations, collaboration, cleaner financial separation, and better structural clarity, a company is usually the safer path.
Individual Business
Simpler registration and lower maintenance cost, better for solo testing and smaller operating scope.
Limited Liability Company
Better fit for long-term operation, team growth, clearer structure, and more formal business cooperation.
Entity Comparison
Tradeoffs: weaker brand and financing posture, more direct personal operating responsibility.
Best for: solo founders and early validation.
Tradeoffs: more process, more finance work, and more upkeep.
Best for: brand-oriented or longer-term operating models.
What Matters More in 2026
- If you choose a company structure, do not ignore the practical consequences of capital subscription rules under the newer Company Law regime.
- If you are only testing demand, do not overcomplicate the entity for appearance alone.
- If you expect team growth, financing, or more formal cooperation within 6-12 months, setting up a company earlier can be practical.
Worked ecommerce scenario: where a China license fits in a 20oz tumbler store
Assume you are launching a 20oz stainless-steel travel tumbler. The supplier is in Zhejiang, the first batch is 300 units, the target market is the United States, the store runs on Shopify, and ads will start on Meta and Google. You now have three pressures: the supplier wants a formal purchasing contract, the payment path needs merchant review, and your policy pages must say who is responsible for refunds and support.
| Area | What the domestic entity can do | What it cannot solve for you | Next action |
|---|---|---|---|
| Supply chain | Sign China-side purchase contracts, issue invoices, pay through a business account, and keep records for samples and the first batch. | It does not prove refund responsibility, overseas tax position, or payment entity for US buyers. | Put supplier contract, invoice title, SKU list, and business scope into one evidence sheet. |
| Payment review | Act as one proof that you have a real China-side sourcing and operating base. | If the gateway requires a US, UK, Hong Kong, or other local company or bank account, the China license does not replace it. | Check supported regions, merchant entity type, bank beneficiary, and policy-page identity before building checkout. |
| Storefront disclosure | Support Contact, Refund, and Privacy pages that explain the China-side operator, support email, and record responsibility. | It cannot make return address, support email, and payment descriptor look like different merchants. | Write a merchant identity map: operator, support team, return handler, and refund responsibility. |
| Capital and business scope | Cover realistic ecommerce, trading, technical service, or import/export activities where relevant. | High registered capital is not credibility, and vague scope does not cover high-risk claims. | Use the next 1-3 years of real operations to set capital and use core SKUs to test scope. |
The decision sentence
If this tumbler is still a test product, the domestic entity may cover China-side purchasing, contracts, and records first. Once you move into real checkout, ads, and refunds, you must separate domestic entity, overseas payout entity, payment account, and public policy language. The cost of getting this wrong is not just one missing document; it can be rejected payment review, unclear refund responsibility, or ad spend that leads to an unstable checkout.
After the New Company Law, Registered Capital Cannot Be Treated Casually
This is where a lot of old advice becomes misleading. Under the newer Company Law framework, shareholders of a limited liability company generally need to fully contribute subscribed capital within five years from the company’s establishment. The State Council's 2024 registration-capital rules also define transition handling for older companies and regulatory attention for abnormal capital or contribution deadlines. That means registered capital should no longer be treated as a random image-building number.
Why This Matters
- If you set capital unrealistically high, it can later create real contribution pressure and internal financial strain.
- For cross-border sellers, registered capital is not branding material. It should match your operating stage and actual business path.
- Early-stage operators should optimize for execution, not for looking large on paper.
Safer Handling Logic
- Set the number based on realistic 1-3 year operating needs instead of image management.
- Align internally on capital responsibilities before filing, not after.
- If you already have an older high-capital structure, especially one with a very long contribution deadline or an unreasonable amount, review whether later normalization is needed under official registration requirements and proper advice.
What the Registration Flow Looks Like in 2026
Business registration in China is now highly digitalized. Registration authorities use unified systems and standardized forms, and many regions support integrated online business-start workflows plus electronic business licenses. In practice, most delay comes from incomplete materials, a weak business-scope design, or inconsistent address evidence.
Recommended Sequence
What to Do Within 30 Days After the License Is Issued
Getting the license is not the finish line. The first 30 days determine whether the entity becomes a useful operating base or just a shell that later creates avoidable problems.
Banking setup
Open the company account and define online-banking permissions early, especially if multiple people touch operations or finance.
Tax rhythm
Confirm taxpayer type, filing cycle, and filing responsibility before the first deadline catches the team unprepared.
Contracts and invoices
Prepare standard procurement, vendor, and service paperwork so later settlement and bookkeeping are cleaner.
Compliance trail
Archive filing confirmations, tax notices, bank materials, and signed contracts for future reviews, platform checks, or due diligence.
Why This Period Matters Most
- The license only proves the entity exists. It does not mean the operating system is ready.
- Many cross-border sellers do not fail at registration itself. They fail at the tax and finance follow-through afterward.
- If you expect platform reviews, payment reviews, or financing later, this documentation layer becomes increasingly valuable.
Annual Reporting, Tax Filing, and Ongoing Duties Cannot Be Ignored
A common founder mistake is treating the license as the end of the work. In reality, annual reporting, tax filing, account maintenance, and updates to registered information are what define long-term compliance quality.
Core Ongoing Duties
- Annual reporting and public disclosure: both companies and individual businesses should keep reporting obligations on a calendar instead of relying on memory.
- Tax filing: no revenue does not automatically mean no filing obligation. The real answer depends on tax status and local requirements.
- Registered-information changes: address, scope, responsible people, or company details should not be changed only internally while registration data stays outdated.
- Company-account and invoice management: this directly affects settlement, audits, cooperation, and future diligence quality.
Frequent Risks
- Business scope is too narrow: you later expand and end up paying in time and friction for amendments.
- Weak address materials: this gets exposed during bank-account opening, tax matters, or spot checks.
- No clear tax assigned lead: no one is truly responsible until penalties force the issue.
Practical Advice for Cross-Border Store Operators
If your business relies on China-based sourcing and overseas selling at the same time, a domestic business license should usually be treated as the domestic operating base, not as a substitute for overseas entities or overseas payment structures.
A Better Way to Think About It
- If your procurement, contracting, and local cost structure are China-based, a domestic entity can be very useful.
- If you still need stronger overseas payment capability, combine domestic planning with a Hong Kong, UK, or other overseas structure where appropriate.
- If you are still validating a one-person business, you do not always need a complex company setup immediately.
- If you plan to operate long term, build finance and compliance habits early instead of fixing them later under pressure.
Operating Recommendation
- Choose the domestic structure based on your real operating path, not on what other sellers happen to be doing.
- Treat the license, tax, banking, and documentation system as one connected workflow, not four unrelated tasks.
- In cross-border ecommerce, the domestic entity solves domestic-chain problems. Do not confuse that with overseas structure design.
Entity evidence folder: a license is not enough; produce the record chain in five minutes
Entity readiness is not the sentence "we have the license." Payments, ads, suppliers, support, and finance review need one record chain that explains who operates, who collects money, who is responsible for refund and support responsibility, and who handles tax and invoices.
Pick the weakest folder below and repair it first. Do not wait until payment review, supplier diligence, or customer dispute pressure appears before rebuilding the story from chat history.
| Folder | Keep | Weak signal | Next repair |
|---|---|---|---|
| License and business scope | License screenshot, unified social credit code, business scope, address, registration date, and status. | Business scope cannot explain the real SKU, product claim, or ad promise. | Put core SKU, PDP claims, and business scope into one table; pause unclear categories first. |
| Responsible person, address, and contacts | Responsible-person records, address proof, support email, phone, Contact / Privacy / Refund pages. | Public merchant identity, support inbox, return address, and payment profile look like different operators. | Map merchant identity first: operator, support, refund lead, and privacy contact, then sync pages. |
| Bank, tax, and invoice path | Business-bank status, tax filing rhythm, invoice title, contract template, payment records, and archive folder. | The license exists, but banking, tax, contracts, and invoices have no responsible person. | Assign responsible leads and 30-day due dates for banking, tax, contracts, invoices, and archive. |
| Platform, payment, and storefront proof | Payment-path entity requirements, account screenshots, bank beneficiary, Shopify store profile, policy pages, and billing descriptor. | Storefront entity, payout entity, bank beneficiary, and refund responsibility cannot form one record chain. | Pause live checkout or ad scaling first, then repair payment path and policy-page entity explanation. |
Acceptance standard: if payments, ads, banks, suppliers, or customers ask who is responsible for the store, you can produce one set of screenshots, files, and page records within five minutes instead of assembling materials under pressure.
Entity mismatch pause check: decide whether launch can continue
This lesson is easy to misread as "just register a license." The useful skill is deciding what to do when the entity, payment path, public store identity, and post-license duties do not tell the same story. Pause the unsafe move, find the first evidence, then decide what must be repaired.
| Mismatch scenario | Unsafe move | Continue-or-pause decision | First evidence | Pause rule |
|---|---|---|---|---|
| The license is Hangzhou Company A, PayPal uses the founder's personal name, Meta Business Portfolio belongs to a friend company, support still uses free Gmail, and the footer has no company name. | Open live checkout and scale ads first, then explain the mismatch after payment KYC or ad review gets blocked. | Pause live checkout and ad scaling. Write one entity role table: storefront identity, payment account, ad assets, support, and refund responsibility. | License, PayPal / payment profile, Meta Business Portfolio screenshot, domain verification, support email test, Contact / Refund / Privacy / Terms pages, and bank beneficiary name. | Do not enter launch judgment until store, money, ad assets, and support responsibility are explainable. |
| The store shows a domestic company, but payment or bank records use a person, another company, or another jurisdiction. | Finish the store first and explain the entity only after payment review or payout is blocked. | Pause live payment setup and write the roles for merchant identity, payment account, refund responsibility, and payout bank. | Payment entity requirement, account record, bank beneficiary name, and policy-page URLs. | Do not open live checkout or scale ads until the identity chain is explainable. |
| Business scope does not cover the real category or strong product claims. | Use broad wording to explain everything and launch first to see whether platforms notice. | Pause high-risk SKUs or strong claims and check business scope, SKU list, supplier contract, and market restrictions. | License business scope, core SKUs, claims, supplier contract, and permit or restricted-goods notes. | Do not launch high-risk SKUs when scope and category cannot be explained. |
| Address, support email, return address, and privacy contact look like different operators. | Assume buyers will not check these details and hide or scatter them across pages. | Create a merchant identity map: who operates, who supports, who handles returns, and who is responsible for privacy and refunds. | License, address proof, Contact / Return / Privacy pages, and support-email test. | Do not enter launch QA until public merchant identity has one consistent explanation. |
| The license is issued, but tax, banking, contracts, invoices, and archive have no assigned lead. | Mark "license done" in the roadmap, then start purchasing, ads, or large contracts. | Create a 30-day post-license board with a assigned lead for banking, tax, contracts, invoices, archive, and policy sync. | License issue date, bank status, tax status, contract template, invoice title, and archive path. | Do not sign large purchases or scale ad spend until post-license duties have responsible people. |
| The target payment path or platform requires an overseas entity, local bank, or proof of actual operations. | Keep building and advertising, hoping to explain it during review. | Separate the domestic purchasing entity from the overseas payout entity, then move into the overseas entity or payment lesson when needed. | Supported-country list, bank-account requirements, gateway region requirements, storefront entity, and refund-responsibility language. | Do not mark payment ready until domestic and overseas roles are separated. |
The decision sentence
The question is not "Do I have a license?" It is "Can the license, storefront, payment path, bank records, tax duties, and refund responsibility be explained as one record chain?" If not, pause the launch.
Official boundary review: check these three items first
A mainland entity is more than a business license image. China government's published Company Law of the People's Republic of China covers basic items such as company name, domicile, articles, and business scope. In an ecommerce setup, those details need to support payments, ads, tax, and customer-service responsibility. Do not rely on memory here. Check the three official boundaries below before deciding that the entity path is ready.
| Boundary | Official position | What to do for a direct store |
|---|---|---|
| Registered capital | State Council registration-capital rules define transition handling for older companies and allow registration authorities to require adjustment when contribution periods or capital amounts are clearly abnormal. | Do not inflate capital for appearance. Work backward from the next 1-3 years of real operating needs. |
| Registration portal | SAMR's national business-entity registration service provides entry points for setup, changes, cancellation, name search, and related registration services. Local material rules still depend on the local platform. | Confirm the local portal, address evidence, business scope, and electronic license access instead of copying another city's process. |
| Shopify payments | Shopify's help center says Shopify Payments is not available from Mainland China, and Hong Kong SAR setup requires a Hong Kong entity, verifiable physical operations, an HKD bank account, and matching documents. | If overseas checkout is the goal, check payment requirements before deciding how the China entity, Hong Kong or overseas entity, and policy pages split responsibility. |
Entity record consistency check
- Company name, legal representative, address, business scope, and license version match.
- Payment, FX, ad account business proof, and Shopify store use one explainable record set.
- Supplier contract, invoice title, business payment, cost archive, and tax filing rhythm point to the same domestic entity.
- Business scope covers the actual product category and avoids restricted or high-risk goods.
- Address proof, contact details, policy pages, and support email point to the same operator.
- Refund responsibility, return address, support email, payment entity, and public merchant identity form one explainable responsibility chain.
Copyable lesson notes: domestic entity boundary decision
If you plan to launch with a domestic sole-proprietor license but the target
payment provider requires an overseas company or local bank account, do not
wait until the store is finished to change the entity. Fill the notes below
before you treat this lesson as complete.
Write this into your copyable lesson notes
- Current pressure: China-side purchasing, payment review, policy pages, tax and banking, or overseas entity setup.
- First evidence: License type, business scope, responsible-person and address records, supplier contract, bank and tax status, target gateway requirements, and policy-page URLs / version records.
- This-week action: Choose individual business or company, check the target gateway, repair scope or record consistency, or move into overseas entity and payment setup.
- Stop action: Do not use a China license as the overseas compliance answer, do not submit payment review while entity and payout records conflict, and do not inflate registered capital for appearance.
- Review window: Review banking, tax, contracts, invoices, and policy pages within 30 days after the license is issued; review domestic and overseas role split before live checkout.
- Next route: Payment gateway setup, overseas company registration, policy and compliance pages, or personal cash readiness, depending on the biggest blocker.
The point of these notes is not to save a nice conclusion. It is to make the next payment, policy, overseas entity, or tax conversation start from evidence instead of starting over.