Research methodology
How We Research
A transparent look at how Extentage finds, evaluates, cross-checks and maintains practical information about China’s fast-changing payment and commercial systems.
Authority first
We start as close as possible to the rule, product or event being explained.
Cross-checked
Material claims are compared across independent evidence where possible.
Limits stated
We identify geographic, account and timing limitations that affect readers.
Review triggered
Important changes prompt targeted review rather than silent assumptions.
01 · Scope and framing
We begin with the reader’s actual decision
A useful guide starts by defining what the reader is trying to do, which jurisdiction or platform is involved, and what could materially change the outcome. We separate broad background from operational instructions so readers can distinguish context from steps they may rely on.
Before research begins, we identify the core questions, likely exceptions and time-sensitive claims. This reduces the risk of collecting impressive information that does not answer the practical problem.
02 · Evidence hierarchy
Not every source carries equal weight
We evaluate evidence by proximity to the underlying rule or product behavior, authority, date, specificity and whether the claim can be independently confirmed.
Primary authorities
Regulations, central-bank releases, government notices, official legal texts and regulator guidance.
Official provider documentation
Product terms, fee schedules, help centers, eligibility rules, support notices and formal platform announcements.
Direct and reproducible evidence
Documented workflows, screenshots, observable interfaces and transaction behavior where appropriate and safely verifiable.
Credible secondary context
Established reporting, specialist analysis and academic work used to explain context or corroborate—not replace—stronger evidence.
Anonymous posts, copied summaries and unsupported promotional claims may help identify a question, but they are not sufficient support for a material factual conclusion.
03 · From question to publication
Our research workflow
Map the claim set
We identify the rules, fees, availability, steps, exceptions and safety considerations the guide needs to address.
Collect the strongest current sources
We prioritize official and primary material, recording dates and the scope of each source.
Cross-check material statements
Important claims are compared with additional authoritative or independently observable evidence where available.
Write for practical clarity
Technical rules are translated into plain language without removing meaningful qualifications.
Review claims, links and limitations
The draft is checked for unsupported certainty, unclear attribution, missing context and time-sensitive instructions.
04 · Verification
Different claims require different checks
No single verification method fits every topic. Depending on the question and what can be responsibly confirmed, our checks may include:
Document comparison
Comparing current terms, help documentation and official notices for consistency and scope.
Workflow review
Examining the sequence, labels and decision points users encounter inside a documented process.
Date validation
Checking whether a source predates a policy, fee or product change that could make it misleading.
Exception testing
Looking for residency, identity, card, region, currency and account-status conditions that alter the answer.
We do not claim hands-on testing when a conclusion is based only on documentation. When direct verification is unavailable, we state the limitation rather than presenting inference as observation.
05 · Conflicting information
When reliable sources disagree
Payment rules and platform behavior can differ across documents, regions and account types. A newer support article may conflict with older terms; an app interface may change before documentation catches up.
- We check publication and effective dates.
- We distinguish formal policy from observed implementation.
- We identify whether sources describe different users or jurisdictions.
- We prefer the most authoritative source that directly governs the claim.
- If uncertainty remains material, we disclose it and point readers to direct confirmation.
06 · Numbers and reference data
How we handle rates, fees and figures
Numbers can create false precision when their timestamp, source or basis is unclear. Exchange rates, transaction fees, limits and market figures are therefore presented with context appropriate to their use.
Reference data is not a guaranteed transaction quote
Where a rate or figure may change, we identify the source or nature of the figure, indicate timing where practical and avoid calling delayed or cached data “live.” Provider spreads, card-network conversion, intermediary fees and account-specific pricing can produce a different final amount.
07 · Maintenance
What triggers a review
Publication dates show when material first appeared; review or update dates indicate later attention. A date alone does not guarantee that every external interface remained unchanged afterward.
- New regulation or authoritative guidance
- Changed provider terms, fees, limits or eligibility
- Material interface or workflow changes
- Reliable reader reports supported by evidence
- Broken, removed or superseded primary sources
- Scheduled review of high-impact evergreen guides
Minor formatting changes may not require a new substantive update date. Material corrections follow our separate Corrections Policy.
08 · Transparency
What our research cannot guarantee
China’s payment environment can vary by provider, location, identity verification status, linked card, currency, device and account history. Documentation may lag implementation, and an individual support decision may not establish a general rule.
We aim to give readers the strongest practical explanation supported by available evidence. We do not guarantee that a platform will approve an account or transaction, and our content does not replace financial, legal, tax or compliance advice.
Have stronger or newer evidence?
Send the page URL, the claim concerned and a source we can examine.