SpendNode Methodology

What This Page Covers

SpendNode is not a vendor directory that copies headline cashback rates and stops there. Our methodology is built to answer a more useful question: what does a crypto card actually look like once fees, funding friction, custody tradeoffs, and regional limits are accounted for?

That means we do not treat "8% cashback" and "0% FX" as complete answers on their own. We look at the operating conditions behind those claims, document where terms are clear or unclear, and try to show the product the way a real user experiences it.

Our Core Principle: Real-World Value Beats Marketing Headlines

Crypto card marketing is often directionally true but operationally incomplete. A card can advertise:

• high cashback but require a large token stake
• 0% FX but still rely on network exchange rates or limited settlement currencies
• self-custody while still depending on issuer-controlled card rails
• free membership while charging meaningful conversion, spread, or ATM costs

Our job is to make those tradeoffs explicit.

Where Our Data Comes From

We prioritize primary sources and recent evidence.

1. Official issuer materials

This includes:

• fee schedules
• terms and conditions
• help center articles
• app store pages
• official product pages
• official announcements and changelogs

If an issuer publishes contradictory terms across multiple official pages, we note the conflict and use the most specific or most recent source available.

2. In-app and first-hand product checks

Where possible, we verify things directly in the app or product flow, including:

• funding methods
• card ordering flow
• wallet support
• rewards screens
• network warnings
• top-up behavior
• shipping or availability prompts

When we include screenshots or product-behavior warnings, those come from direct observation, not paraphrased marketing copy.

3. Direct clarification from vendors

If terms are unclear, missing, or internally inconsistent, we may contact the issuer or product team directly. That can help resolve:

• regional availability
• waitlist status
• funding assets
• reward denomination
• physical vs virtual issuance
• whether a feature is live or merely announced

Direct clarification can improve accuracy, but it does not override written terms when the public documentation says something else.

4. Community and user signals

We also pay attention to credible real-user reports, especially around:

• support responsiveness
• delayed credits
• frozen withdrawals
• top-up quirks
• card acceptance issues
• rollout gaps between what is announced and what is actually usable

We treat community reports as supporting evidence, not primary truth, unless we can verify them ourselves.

What We Verify on Each Card

We try to verify the operating facts that matter most in real use.

What "Verified by SpendNode" Means

When a vendor or product carries a Verified by SpendNode badge, it does not mean we are endorsing the issuer or guaranteeing future performance.

It means we completed a higher-confidence review at the time of publication, including:

• reviewing the issuer's public terms, fees, and marketing claims
• checking the live product flow directly where possible
• comparing what the product says publicly with what a user actually sees in the app, onboarding, or card flow
• not finding a materially misleading mismatch at the time of review

In plain English: the badge means we did more than copy the headline page, and we did not find obvious gaps between the vendor's public story and the live product experience when we checked it.

That badge can still be revised or removed if terms change, rollout quality degrades, or a later review finds a mismatch we did not see earlier.

How We Think About "Net Value"

We do not compare cards on headline rewards alone.

A rough version of the framework is:

Net value = rewards - issuer fees - FX costs - conversion costs - spread - staking or capital lock-up burden

That is why two cards with the same advertised reward rate can perform very differently in practice.

Examples:

• A free card with lower rewards but 0% FX may beat a higher-reward card once cross-border fees are included.
• A card with token-denominated rewards may look strong on paper but carry meaningful volatility and holding risk.
• A premium card may only make sense above a certain spending level, and only if you actually value the attached perks.

We often describe this in editorial form rather than pretending every card can be reduced to one universal formula.

Our Review Pillars

We generally evaluate products across these core dimensions:

SpendNode Rating vs User Rating

On some product pages, you may now see a SpendNode Rating alongside user reviews.

These are not the same thing.

• User rating reflects approved user reviews submitted through the site
• SpendNode Rating is our editorial score for how strong a card is at its intended job

We keep them separate on purpose. A product can have:

• satisfied users in a narrow niche
• weak economics for the broader market
• strong self-custody design but limited rewards
• high headline rewards but poor clarity once fees, limits, or lockups are accounted for

Collapsing all of that into one crowd number would hide too much.

How SpendNode Rating Works

We do not use one universal rewards-heavy formula across every card.

Instead, we use a two-layer model:

1. Baseline categories

Every rated card is assessed across:

• cost efficiency
• product utility
• custody and trust model
• operational reliability and UX
• transparency and honesty

2. Product archetype

We then score the card in the context of what it is actually trying to be.

Current archetypes include:

• rewards / cashback
• self-custody spending
• premium perks
• travel / lounge access
• stablecoin spending

That matters because a self-custody card should not be dragged down just because it is not trying to win on cashback, and a premium card should not be judged like a free virtual card.

Our editorial rating is designed to answer:

How strong is this product for its intended use case once costs, trust assumptions, and real usability are accounted for?

Current Status of SpendNode Rating

SpendNode Rating is an editorial scoring system, not a fully automated sitewide engine.

That means:

• rated cards are scored manually by editors using the framework on this page
• the score is based on the same baseline categories and archetype lens each time
• the score is not generated from user reviews, affiliate relationships, or app-store sentiment
• the score can be revised as a product changes or as the framework is refined

We prefer that level of transparency over pretending that every score already comes from a perfect machine-readable formula.

The Rating Formula in Plain English

For now, the formula is best understood as a structured editorial model rather than one fixed universal equation.

The logic is:

SpendNode Rating = baseline category assessment + archetype-specific weighting + editorial review of whether the final outcome matches the product's real-world job

In practice, that means:

• every rated card is checked against the same baseline categories
• the weighting shifts depending on whether the card is mainly about rewards, self-custody, travel, premium perks, or stablecoin spending
• editors then review whether the outcome actually matches the product's role in the market

That last step matters because a purely mechanical score can still be misleading if the weighting produces an answer that does not reflect how people actually use the product.

Rankings and Editorial Independence

Our rankings are editorial, not pay-to-rank.

• A vendor cannot buy a higher position in a "best" page or comparison verdict.
• Affiliate relationships do not change the underlying fee math or product facts.
• If a card is weak, expensive, geographically narrow, or operationally messy, we say so.

For more on that side of the business model, see our affiliate disclosure.

How Often We Update

We use a layered update model rather than pretending every page is refreshed in the same way.

We use AI agents daily to check for changes in card data, identify which pages are affected, and alert editors when a sweep is needed. That helps us keep comparisons, country pages, and rankings aligned as fees, rewards, limits, and availability change.

Editors also review and verify updates daily against issuer documentation and structured source data before changes go live. AI agents speed up detection and page-level consistency checks, while editorial review remains responsible for accuracy and final sign-off.

• Ongoing: issuer announcements, product launches, partnership news, and material fee changes
• Periodic manual audits: rewards, FX fees, supported regions, custody wording, and card availability
• Editorial rewrites: when a page's framing becomes stale even if the raw card still exists

Where available, card and category pages also show a Last verified date. That date reflects the latest manual verification point recorded for that page or dataset.

What We Do Not Claim

There are limits to what any comparison site can know with certainty.

We do not claim that:

• every vendor term is perfectly current every day
• every user will get identical FX or spread outcomes
• every support experience will match ours
• every announced feature is fully rolled out globally

Where terms are unclear, we would rather say "not fully confirmed" than present false precision.

Why Crypto Cards Are Easy to Misread

Crypto cards sit at the intersection of:

• card networks
• custodians or wallets
• stablecoin or token funding
• fiat settlement
• regional compliance
• issuer-specific limits and reward systems

That makes them much easier to misread than a normal credit card or debit card. A methodology page on this topic should do more than repeat issuer marketing. It should explain how the pieces fit together and where the hidden tradeoffs live.

Report a Correction

If you find a fee, region, reward rule, or product detail that looks wrong or outdated, email hello@spendnode.io.

Useful correction reports include:

• the page URL
• the field that looks wrong
• the issuer source or screenshot
• the date you observed it

We would rather correct a page quickly than leave stale information live.