Define a reproducible desk-review boundary
On October 29, 2026, we read Kraken’s public fee schedule and its trading-fees support overview. This is a purposive two-page sample from one provider, selected because the calendar includes a Kraken product comparison. It is not a representative exchange survey, account test, fee quote or financial audit.
For each page, record the URL, check date, product scope, relevant claim, remaining question and evidence classification. “Documented” means the page states it; it does not mean CryptoTrades independently verified the provider’s execution or controls.
Evidence: Kraken fee schedule · How trading fees work on Kraken
Retain the discrepancy instead of averaging it away
The main schedule describes volume or assets-on-platform tier qualification. The support overview describes volume, pair and maker/taker status. The documents are not equally detailed on tier qualification. We recorded that difference and did not infer an account’s applicable rate.
Both pages are provider-authored sources. Agreement between them would not be independent corroboration. The account’s eligible product, jurisdiction and current quote remain outside this desk review.
| Page | Observed scope | Unresolved question |
|---|---|---|
| Fee schedule | Product tables and volume or asset-based tier description | Which account-specific tier applies? |
| Support overview | Order-book fee explanation; volume, pair and maker/taker factors | How does the overview map to current cross-platform tiers? |
Evidence: Kraken fee schedule · How trading fees work on Kraken
Separate evidence categories
Use “documented statement” for readable claims, “not assessed” for checks outside the sample, “unavailable” for evidence that could not be obtained and “conflict or scope difference” where sources do not align. None of these labels alone establishes good or bad service quality.
In this sample, execution quality, withdrawals, reserve adequacy and regional licensing are not assessed. We did not test trades, collect customer records or inspect private dashboards. Avoid expanding two public fee-page observations into a verdict on those subjects.
Repeat the method without turning it into a ranking
For another review, set the provider, product, jurisdiction and questions before collecting pages. Preserve exact URLs, date and short factual notes. Separate observation dates from page-update dates; if a source lacks an update date, record it as unknown.
Check a fee schedule, product terms, funding documentation and any relevant official register only when those checks fit the stated scope. Do not count the number of published pages as a transparency score, or interpret an inaccessible page as proof of misconduct.
| Field | Example or rule |
|---|---|
| Question | Which fee components are documented? |
| Source and time | Exact URL plus check date |
| Finding | Narrow paraphrase tied to a source |
| Classification | Documented, not assessed, unavailable or difference |
| Next check | Resolve applicability before using a rate |
Use the findings as a maintenance queue
The next editorial action is to recheck tier applicability before updating a product-specific fee claim. Sources & method links a machine-readable observation CSV; no live account rate is stored or implied.
Link the product comparison to this method and retain unresolved questions when editing. For users, the Compare framework is a starting point for checking their own scope, not a recommendation or certification. Fresh evidence can change the record without changing the method.
Sources & method
- Kraken fee schedule
Provider documentation checked 29 October 2026. Product and regional applicability must be checked again before use. Checked 2026-10-29.
- How trading fees work on Kraken
Provider explanation; differs in tier detail from the current fee schedule. Not an account-specific quote. Checked 2026-10-29.
- Download the two documentation observations (CSV)
Dated public-document statements and an unresolved scope difference. No account-specific quote, execution test or financial audit. Checked 2026-10-29.
Continue learning
Found an error? Contact the editorial team with the page and supporting source. Never send private account information.