Main Source Categories We Record
Source categories describe the nature of materials and their initial handling; they do not automatically determine whether content is true or false. Some categories may have verification statuses initialized according to system configuration, but such status remains only a workflow label and does not mean the content has been independently confirmed. Announcements from official accounts and ordinary user posts on the same platform must not be assigned the same evidentiary weight.
Product Websites and Official Documentation
Generally highProduct websites, help centers, fee pages, terms, regional and KYC information, and product announcements.
Suitable for supporting the relevant product rules; dates, applicable products, regions, and subsequent changes must still be checked.
Regulatory, Card-Network, and Issuer Materials
Generally highRegulatory registrations or announcements, card-network information, issuing institutions, and other verifiable legal-entity materials.
Suitable for supporting entity, issuance-relationship, and regulatory-event information. Legal status should be based on current records from authorities with jurisdiction.
Issuer or Brand Submissions
Independent verification requiredFee schedules, regional information, KYC rules, FAQ, or correction materials proactively provided by issuers.
The submitter's identity and the material's content are verified separately. Providing information does not mean the platform accepts, recommends, or endorses it.
Platform-Curated and Reference Materials
Moderate reference valueCurated results used to standardize region names, categories, field definitions, and comparison structures.
The basis and update date should be retained. These materials do not replace product providers, regulators, or other primary factual sources.
App-Store Pages
Moderate reference valueApp identity, developer, version, regional visibility, and listing status on the App Store or Google Play.
May support app-status information. Individual user reviews in stores should be handled separately as third-party evaluations.
Third-Party Reviews
Moderate to relatively lowContent from Trustpilot, app-store reviews, and other public review platforms.
Suitable for observing experience themes and complaint trends. Duplication, review manipulation, regional differences, and missing context must be addressed.
User-Submitted Feedback
Case-by-case verificationStructured experiences submitted by users through UCard Radar, such as region, KYC, fees, card blocking, refunds, or payment outcomes.
After checking the subject, time, evidence, and independence, the material may support individual-case or trend assessments. A single report does not automatically change a rating.
Screenshots, Emails, and Support-Ticket Materials
Depends on contextMaterials such as customer-service conversations, emails, app interfaces, transaction failures, or KYC outcomes.
The full context, time, and right to submit must be confirmed. Access to sensitive originals is generally restricted, and only authorized redacted summaries may be displayed when necessary.
Media, Research, and Public Social Content
Primarily leadsNews, research reports, Reddit, X, forums, videos, or other public content.
May supplement background or identify issues requiring verification. Ordinary posts, KOL content, and secondhand accounts cannot independently confirm product rules.
Commercial Pages and Unknown Sources
Low or unknownAffiliate, Referral, or promotional pages, as well as materials whose nature or origin cannot be confirmed.
Commercial pages are used only to identify partnership or promotional information. Unknown sources serve only as leads and cannot independently support public facts or ratings.
Source-Type Baseline Values (Before More Specific Rules Apply)
The table below lists initial reliability reference values from the source-type registry. Some source types may also inherit a default verification status in the current administrative process. Authorized personnel may adjust these defaults, which are used only for material management and are not accuracy rates, factual certifications, risk scores, or card ratings.
| Source Type | Examples | Default Reliability | Information It May Confirm | Can It Independently Affect the Rating? |
|---|---|---|---|---|
| Product Website/Official Documentation | Official websites, terms, help centers, and fee pages | 90 (initial value) | Product rules and official statements | May support the relevant fields; dates, scope, and conflicts must be checked |
| Regulatory Materials | Registrations, announcements, penalties, or licensing information | 90 (initial value) | Entities, regulatory status, and major events | May support the relevant facts; jurisdiction and effective dates must be considered |
| Issuer Submission | Fee schedules, FAQ, and correction materials | 75 (initial value) | Product information asserted by the submitter | Both the submitter's identity and the content require review; not accepted automatically |
| Platform-Curated Materials | Standardized regions, categories, and comparison criteria | 70 (initial value) | Standardized presentation and comparison criteria | Does not replace primary product or regulatory facts |
| Customer-Service Screenshot/Email | Customer-service replies, support tickets, and app screenshots | 65 (initial value) | Case-specific materials for a particular time and account | Generally cannot be generalized; context, redaction, and authorization must be verified |
| App-Store Page | App identity, version, and listing status | 60 (initial value) | The status of a store page in a particular region and at a particular time | Individual reviews are handled separately as third-party evaluations |
| Media Source | News, investigations, and industry reporting | 55 (initial value) | Background, public events, and third-party statements | Distinguish original reporting, opinion, and republication, and check primary sources |
| Third-Party Review | Trustpilot, store reviews, and review platforms | 50 (initial value) | User-experience leads and thematic trends | May be used for trend assessments only after duplication, manipulation, and sample bias are addressed |
| User Feedback | Structured experiences and evidence descriptions | 45 (initial value) | The submitter's specific experience | A single report is not automatically generalized and does not automatically change a rating |
| Affiliate/Promotional Page | Affiliate programs, Referral information, or promotional descriptions | 40 (initial value) | Commercial relationships or promotional terms | Not used to prove product quality or improve a risk rating |
| Unknown Source | Origin or nature cannot be confirmed | 20 (initial value) | Creates only a lead requiring verification | Cannot independently support public facts or ratings |
How Conflicting Sources Are Handled
- First confirm whether the materials concern the same product, version, region, account type, and period. Differences in scope do not necessarily constitute a conflict.
- Compare the publisher's identity, proximity to the primary source, verification status, publication time, and whether the material directly supports the disputed field, rather than considering only the platform name or default score.
- When regulatory or issuer materials conflict with brand promotions, prioritize explaining the scope of materials from authorities with jurisdiction. When an official page conflicts with an actual case, retain both the rule description and the verified exception.
- Unresolved conflicts should be marked unconfirmed, pending verification, or disputed, with a clear distinction between what can and cannot currently be confirmed.
- Multiple independent materials pointing to the same serious issue may enter risk-event or rating review; this is not an automatic determination.
- When new evidence changes a published fact, update the relevant field, source, and available update time, and handle significant changes under the correction policy.
How Community and Third-Party Reviews Are Used as Leads
Public communities and review platforms can often reveal service anomalies early, but they also involve anonymity, duplication, deleted posts, review manipulation, marketing, regional differences, and missing context. A platform name alone cannot establish that content is true.
May reveal public discussions and experience themes. Posts or comments must be checked for the subject, time, account independence, and verifiable materials.
X
Announcements from confirmed official product accounts are handled separately from ordinary user or KOL posts; the latter are primarily treated as leads requiring verification.
Review Platforms and App-Store Reviews
Used to observe experience themes within a version, region, and period. The number of ratings does not constitute verifiable fact, and an individual review generally cannot be generalized.
Other Public Social Content
It may serve as supporting material only after being submitted by a user or manually recorded and undergoing necessary verification. UCard Radar does not promise systematic coverage of every platform.
Community and third-party reviews do not automatically change an A/B/C/D rating merely because they are included. They may affect a public rating only after they are incorporated into a specific component rationale during editorial review and the publication process is completed. Source category, default reliability, and “verified” status do not themselves have this effect.
How Sources Enter the Fact and Rating Processes
Source records do not automatically generate public facts or risk scores. Under the editorial standards on this page, before materials are used in public content or scoring rationales, the target card, field, region, period, and conflicting information should be checked, followed by the applicable publication process. A source-type or verification-status field does not itself prove that these checks have been completed individually.
- An official fee page may support fee fields, but the version, currency, region, and effective date must be checked.
- Regional and KYC materials may support rule descriptions. Reviewed failure reports may reveal exceptions or differences in implementation.
- Regulatory or issuance-relationship materials may support entity and structure assessments, but the jurisdiction and current status should be stated.
- Multiple independent materials concerning card blocking, freezes, or refunds may form a trend signal and may enter risk-event review.
- A source's default reliability score, verification status, and risk score are independent and cannot be directly converted into one another.
- When evidence is insufficient, conflicts remain unresolved, or materials do not apply to the current product, the information should remain unconfirmed or be excluded from scoring.
What a Source Record Typically Describes
To determine whether a material applies, UCard Radar records necessary source context. Not every field or original material is made public; privacy, copyright, security, membership permissions, and submitter authorization may restrict display.
Source Identity
Records the source category, platform, title, link or file identifier, and available publisher information.
Helps determine whether the material is a primary rule, third-party statement, individual user case, or commercial content.
Time and Version
Records available publication dates, collection times, most recent verification times, and languages.
Used to determine whether the material still applies to the current product, region, and rule version.
Verification Status
Distinguishes unverified, verified, and disputed materials. Some source categories may have their status initialized according to presets. This field reflects workflow position; it does not prove independent field-by-field verification or mean that content is absolutely true or permanently valid.
May be reassessed after new evidence, a scope mismatch, or a conflict is identified.
Applicable Scope
Identifies the card, issuer, field, region, account type, or period associated with the material.
Prevents individual cases, older versions, or information about other products from being incorrectly generalized.
Visibility and Privacy
Necessary information from public sources may be displayed. Access to sensitive screenshots, emails, and personal information is generally restricted, or only authorized redacted summaries are displayed.
Submitters should not provide passwords, verification codes, private keys, seed phrases, or personal information they are not authorized to disclose.
Source-Coverage and Accuracy Boundaries
UCard Radar cannot guarantee coverage of every page, announcement, review, or historical version. External pages may be updated, deleted, access-restricted, or display different content in different regions. Saved summaries may also cease to reflect current policies. Links, quotations, or source scores do not constitute recommendations, certifications, or endorsements of third parties. Before taking action, return to verifiable primary materials and check the current time, product, region, and account conditions.
Frequently Asked Questions
Is a reliability score an accuracy rate?
No. It is a baseline value for a source type before more specific rules apply and may be adjusted according to the collection channel, identity, and verification results. It is not a probability, risk score, or rating.
Are official sources always correct?
Not necessarily. Official materials are generally better suited to explaining a provider's own rules, but they may be outdated, limited in scope, or inconsistent with regulatory materials and actual implementation.
How is user feedback used?
The subject, time, evidence, independence, and permission for public disclosure are checked first. A single case is generally not generalized, and multiple consistent materials still require deduplication and verification.
Why is some original evidence unavailable?
Privacy, copyright, security, submission authorization, or membership permissions may restrict display of originals. Public pages may provide only source information and redacted summaries.
Can a brand correct a source?
It may submit materials, but whether an update is made depends on the evidence. A commercial relationship does not improve a reliability score or risk rating.
Does the page include every source?
No guarantee is made. Sources may be missing, changed, or taken offline. Consider the page's update time and verify primary materials.