DIGITAL ASSET RISK

Crypto products can result in total loss. A rating is not proof of solvency, safety or local availability.

Read the safety standard
K

Exchange · Evidence assessment

Kraken

Custodial exchange with retail and professional trading surfaces

Kraken offers custodial exchange services through region-specific entities and separately publishes a self-custody wallet. Its strongest public case is the breadth of security and fee documentation, not immunity from operational or regulatory risk.

Primary category

Custodial exchange

Kraken Wallet is a separate self-custody product.

Evidence state

Public sources reviewed

Assessment reflects the cited public record and product documents.

Decision focus

Security controls and funding path

The exact entity, rail and interface change the risk/cost picture.

Editorial assessment

The decision in plain language.

Kraken deserves consideration from users who want detailed account-security controls and a professional order-book interface. Its entity map, funding holds and transaction route still need to be matched to the individual user; proof-of-reserves should be read as a dated point-in-time procedure, not a full solvency audit.

Best suited to

Security-conscious traders willing to use the professional interface and verify regional terms before funding.

Primary trade-off

A capable trading surface is paired with regional complexity and funding or withdrawal conditions that vary by method.

Evidence-backed strengths

  • Granular account controls include passkeys, multiple forms of 2FA and a Global Settings Lock.
  • A published fee schedule separates professional maker/taker pricing from instant-purchase convenience paths.
  • Kraken publishes proof-of-reserves materials and clearly distinguishes its exchange from its wallet.

"Limitations to resolve"

  • The applicable contracting entity and available products vary by market.
  • Certain near-instant funding methods can create temporary withdrawal holds.
  • A proof-of-reserves snapshot does not establish all liabilities, controls or future solvency.

Evidence review

What the public record currently supports.

Each conclusion is bounded by its product, jurisdiction and source type.

01

Exchange and wallet are different products

The exchange is custodial, while Kraken Wallet is described as self-custodial. Users should decide whether they are assessing an account held by an intermediary or software for controlling their own keys before comparing features.

S01S02S03

Evidence reviewed
02

Security controls are unusually explicit

Kraken documents passkeys, sign-in and funding 2FA, device management, withdrawal protections and Global Settings Lock. These controls are meaningful only when configured correctly; they do not eliminate phishing, endpoint compromise or platform risk.

S04

Evidence reviewed
03

Fees depend on interface and volume

Professional trading uses a maker/taker schedule, while instant purchase and funding routes can carry different pricing. A decision-ready cost test must include deposit method, spread or trading fee, network choice and exit cost.

S06S07

Evidence reviewed
04

Proof of reserves needs careful language

Kraken published a 30 June 2026 snapshot and a user-verification process. It is useful evidence about specified assets and liabilities at a date, but its agreed-upon-procedures scope is narrower than a complete financial-statement audit.

S05

Evidence reviewed

Decision dossier

From evidence to an accountable decision.

Ten separate modules prevent product scope, legal status, cost, control and remedy from collapsing into one brand impression. Sources were retrieved on .

01

Answer first

Kraken is a credible professional shortlist candidate when granular account security, order-book trading and a comparatively explicit fee schedule are priorities. The decision still depends on the regional entity, funding rail and whether the user will actually configure the available controls.

Source register · retrieved 17 Aug 2026
02

Who should not choose it

It is less suitable for users who want a single global contract, instant funding with no possible withdrawal hold, or a proof-of-reserves badge that can substitute for broader solvency and governance evidence.

Source register · retrieved 17 Aug 2026
03

Product and legal-entity scope

The custodial Kraken exchange, region-specific contracts and Kraken Wallet must be separated. This dossier uses global and EEA terms as documentary boundaries; the user’s residence and product determine the responsible entity and available services.

Source register · retrieved 17 Aug 2026
04

Custody and security controls

Exchange balances are custodial. Kraken documents passkeys, sign-in and funding 2FA, device controls, withdrawal safeguards and Global Settings Lock; each has value only if the test account enables it and recovery does not bypass it too easily.

Source register · retrieved 17 Aug 2026
05

Regulation and customer protection

A regulator record or settlement applies to named entities, products and dates. The 2023 US staking settlement is relevant history, while a dated proof-of-reserves procedure addresses specified assets and liabilities rather than the full control, liquidity and legal-protection question.

Source register · retrieved 17 Aug 2026
06

Fees and total-cost recipe

Compare Kraken Pro maker/taker execution with the convenience purchase route using the same EUR 1,000 or USD 1,000 asset purchase. Add funding cost, spread, trading fee, network withdrawal charge and any hold cost; do not report the published trading tier as total cost.

Source register · retrieved 17 Aug 2026
07

Funding, withdrawal and exit

Cash methods publish different fees, minimums, processing times and potential holds. A complete route records when funds become tradable and when the purchased asset becomes withdrawable, because those timestamps can diverge.

Source register · retrieved 17 Aug 2026
08

Execution, API or wallet permissions

The professional interface and APIs support more controlled order choices, but depth and latency are market- and time-specific. Repeatable market and limit orders, cancellation and API-key scope tests are specified in the reproducible scenarios.

Source register · retrieved 17 Aug 2026
09

Privacy and telemetry

A custodial account requires identity and transaction processing; the next run must document consent, security telemetry, payment-provider involvement and account-data export/deletion routes for the selected entity.

Source register · retrieved 17 Aug 2026
10

Support and dispute route

Use the applicable terms to identify complaint and dispute channels, then run one non-urgent support case. Record bot-to-human transitions, evidence requests, case ownership, response quality and the final escalation instruction.

Source register · retrieved 17 Aug 2026

Fit boundary

Four situations, before a brand preference.

Fits

Granular account and withdrawal controls are priorities.

The documented security stack creates concrete controls to configure and test.

Fits

You want a professional order book with a published fee schedule.

Kraken Pro supports a reproducible execution-and-cost protocol.

Does not fit

You expect one contract and product set worldwide.

Entity, terms and service availability vary by market.

Does not fit

You treat proof of reserves as a solvency guarantee.

A dated procedure does not cover every liability, control or future condition.

Reproducible scenarios

The next evidence, already specified.

These are protocols, not claimed results. Inputs remain fixed so later observations can be repeated or challenged.

S1

Funding-hold clock

Fixed inputs: Named entity, one cash rail, fixed amount and fully verified test account.

Capture: Quoted versus actual availability for trading and withdrawal, fees, notices and release time.

S2

Security configuration and recovery

Fixed inputs: Passkey, authenticator 2FA, funding 2FA and Global Settings Lock enabled on a no-value account.

Capture: Control activation, recovery dependencies, delay warnings and attempted sensitive-setting change.

S3

Pro execution

Fixed inputs: Fixed pair, notional, UTC observation window, market order plus passive limit order.

Capture: Displayed depth, quoted spread, fee tier, fill, slippage, cancellation and API-versus-interface result.

S4

Privacy and complaint route

Fixed inputs: Named EEA or global entity, default account settings and one non-urgent policy question.

Capture: Consent/telemetry controls, data-request route, case ownership, final response and external escalation option.

Incident and change timeline

What changed the risk picture.

  1. US entities settled SEC charges concerning staking-as-a-service.

    Product permissions and entity scope can change; do not generalise from the spot exchange to every earning product.

  2. Kraken’s reviewed proof-of-reserves snapshot date.

    Useful point-in-time evidence must be labelled with assets, procedure and date rather than described as continuous solvency proof.

  3. Terms, security, fee and funding sources re-retrieved for this dossier.

    Scenario inputs now need to be frozen before live observations begin.

Alternatives

Choose by responsibility, not fame.

Coinbase Advanced

A listed-company disclosure trail and a more familiar fiat onboarding surface outweigh Kraken’s security-control depth.

Binance

Broader market and API coverage is essential and the local entity and product are clearly available; governance history must still be weighed.

Evidence confidence

Medium confidence, with a visible stop gate.

Supported
Terms, security controls, fee schedules, funding tables and a dated reserves procedure are publicly traceable.
Unresolved
Live holds, execution, recovery, privacy and support outcomes for a fixed market are the variables most likely to change the conclusion.
What would change the conclusion
A contract/entity change, deterioration in withdrawals, or reproducible evidence that recovery bypasses configured controls would materially lower the assessment; sustained matched execution and support evidence could raise it.

Method applied

How this file is challenged.

  1. Bind residence and product to one contract.
  2. Freeze the funding rail, security state, market and fee tier.
  3. Capture documentary claims and runtime observations separately.
  4. Treat reserve procedures as dated evidence with explicit exclusions.

Dossier change log

Material editorial changes.

Expanded the integrated security, funding-hold, execution and dispute scenarios and refreshed the linked primary/provider records.

FAQ

Questions that decide whether the product fits.

Does proof of reserves prove Kraken is solvent?

No. It can support a specified asset-and-liability snapshot and user inclusion check, but not every off-chain liability, control or future condition.

Can an instant deposit delay withdrawal?

Some funding methods may carry a temporary hold. The exact method and current support table must be checked before funding.

Is Kraken Wallet covered here?

No. Kraken Wallet is self-custodial and belongs under the wallet method.

Which control matters most?

No single control wins. A passkey or 2FA is strongest when withdrawal settings, recovery and Global Settings Lock do not create an easier bypass.

Applicable scorecard

Exchange scoring framework.

Weights are published in advance. An evidence gate can still block the final calculation.

Security & custody25%

Asset controls, account security, incidents and custody structure.

Regulation & transparency15%

Legal entities, regulatory records, disclosures and governance.

Fees & total cost15%

Trading, spread, deposits, withdrawals and realistic trade paths.

Liquidity & execution15%

Depth, spreads, order types, uptime and observable execution quality.

Funding & withdrawals10%

Fiat rails, crypto transfers, limits, holds and geographic access.

Markets & features10%

Assets, pairs, trading surfaces, APIs and supported workflows.

Usability & support10%

Product clarity, accessibility, service channels and response paths.

Source register

Documents behind the assessment.

Primary records establish legal and regulatory facts. Product documents establish current contractual or functional claims; they do not prove solvency or future performance.

Change control

Assessment history.

Material changes remain visible. A log entry records editorial work and the evidence behind each change.

C01

· Editorial assessment updated from cited primary records and product documentation.