Methodology

What We Track

CryptoCardsList tracks public information about crypto debit, prepaid, virtual, and physical card programs. The dataset includes fields such as provider, network, currency, issue countries, spend countries, wallet support, supported assets, fees, limits, KYC fields, issuers, review profiles, cardholder agreements, rewards, and merchant category restrictions where they are available.

Source Priority

• Provider pages, help-center articles, pricing pages, and cardholder agreements are preferred for card-specific claims.
• Issuer or program-manager documents are preferred for legal terms, limits, and dispute handling.
• Public review profiles and community discussions may be linked as context, but they do not replace provider terms.
• User or provider submissions are treated as leads until a source can be reviewed.

Unknown Does Not Mean None

A blank or unlisted field means the current dataset does not have enough source-backed information for that field. It does not mean a fee, KYC step, country restriction, limit, or merchant restriction is absent. When a provider explicitly states that a fee or restriction does not apply, that should be recorded as a confirmed data point rather than inferred from an empty field.

Status and Confidence

Card pages may show availability status, confidence, and last checked dates. Status can be active, waitlist/prelaunch, discontinued/inactive, or unknown. Confidence describes the current source coverage in the repository; many records still need further verification before they should be treated as high-confidence.

Ordering and Comparisons

Directory pages are data views, not personalized recommendations. Some sections use clear mechanical rules, such as recently updated records or category predicates like country, network, card format, wallet support, or listed KYC fields. If a page uses a different ranking or sponsored placement in the future, it should be labeled clearly.

Corrections

Crypto card terms change often. Users and providers can submit corrections through the correction workflow. Corrections should include the card name, field to update, official source URL, and date checked where possible.