Read the claim. Check the source. Know the limits.

Start with primary sources

For rules and product capabilities, we prioritize the organization responsible: government entry and travel guidance, payment-network and wallet documentation, mobile-provider plan details, app documentation and attraction operators. Guides link to their sources so you can inspect the underlying information yourself.

For example, payment guidance cites the People’s Bank of China Guide to Payment Services in China (PDF), with the relevant claim attached to each payment record. A broad policy announcement is useful context, but does not establish every bank, card type or merchant outcome.

Community accounts and editorial explanations can help describe a practical problem. They are not interchangeable with an official rule, and an official statement is still a statement—not our own transaction test.

Keep the claim as narrow as the evidence

Linking a card to Alipay and paying a merchant are different operations. A network-level statement about Visa, Mastercard or UnionPay does not prove support for a particular issuer, issuing country, debit or credit card, account setup or transaction.

Payment answers show their scope, conditions, limitations and sources. Missing coverage means there is no reviewed answer for that combination; it does not mean the combination is unsupported. The checker may ask for more context or return unknown or unavailable rather than infer a positive result.

Similarly, an eSIM provider’s description of overseas routing is not proof that every plan reaches every app. Device compatibility, the purchased plan, routing, current service conditions, applicable laws and provider terms all matter.

Provider statements are not first-hand testing

A source-review date means the cited material was reviewed for that guide. It does not mean a traveler tested the product that day. We do not present Nana’s illustrated voice, a provider’s marketing claim or a working checker response as a personal travel experience.

Where a first-hand test is described, it needs its own stated context and limitations. Successful payment-checker software only demonstrates the request and evidence-retrieval path; it cannot demonstrate a successful bank authorization or merchant payment.

Dates tell you what was reviewed—not what is guaranteed

Guide headers show their actual source-review dates. Different guides can have different dates; changing page wording or layout does not reset the evidence date. A publication date, source publication date and source-review date describe different events.

The current published payment evidence was verified on October 1, 2026 and expires on October 31, 2026. Live checker answers carry their own verification and expiry information. Expiry is a limit on reuse, not a promise that nothing changes before then.

The live checker excludes answers that fail its freshness, evidence or scope policy. Static guides are not a live status feed: check their dates and current primary sources again before travel, especially for entry requirements, prices, plan terms and payments. Rechecking a source can lead to a revised claim, a shorter scope or no usable answer.

The checker can use automated research

The checker first looks for current, applicable evidence. If no reusable answer is available and the service is configured to do so, it can use an AI provider for semantic lookup and source-backed research. Automated research is not a human editorial review or first-hand testing.

The service applies evidence, applicability and freshness checks before publishing an answer. Those checks reduce unsupported claims; they do not remove the need to read sources and confirm your own situation with the provider or bank.

Corrections and commercial separation

If a source changed or a claim looks wrong, compare the guide with the current primary source. Keep the page URL, the statement in question and the source link for your own reference. Our contact page states whether a public contact channel is available. Do not share card numbers, security codes, identity documents or account credentials. A personal success or failure is useful context, but is not by itself evidence of a universal rule.

Corrections should change the affected claim and source context, not silently turn one traveler’s experience into general support. We do not promise a response or re-review deadline.

There are currently no affiliate purchase links on nihaonana. Mentioning a provider does not imply a partnership or endorsement. Any future commercial placement must be disclosed separately from source evidence; payment for placement is not evidence that a product works.