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
CR

Exchange · Evidence assessment

Crypto.com

Custodial app and exchange within a broader product family

Crypto.com is not one uniform surface: the custodial App, order-book Exchange and self-custody Onchain wallet have different custody, pricing and legal terms.

Primary category

Multi-product custodial brand

This file centres on the App and Exchange; Onchain belongs in the wallet methodology.

Evidence state

Public sources reviewed

Assessment reflects the cited public record and product documents.

Decision focus

Exact product, region and route

Those three choices determine custody and total cost.

Editorial assessment

The decision in plain language.

Crypto.com can suit users who value a broad consumer ecosystem, but only after naming the exact product and region. The brand-level review is less useful than a route-level review because fees, custody and entities differ substantially between the App, Exchange and Onchain wallet.

Best suited to

Users who want an integrated consumer product family and are prepared to verify which surface and entity they will actually use.

Primary trade-off

Breadth creates classification complexity: a single brand impression can obscure different contracts, fee models and custody responsibilities.

Evidence-backed strengths

  • Clear product documentation distinguishes the custodial App from the self-custody Onchain wallet.
  • Exchange fee tables and regional App fee pages offer concrete starting points for cost comparison.
  • Some regional permissions can be checked against public regulator registers.

"Limitations to resolve"

  • A headline brand review cannot safely generalise across the App, Exchange and wallet.
  • The prominent proof-of-reserves material is based largely on a December 2022 procedure and should not be treated as a current audit.
  • Regional pricing and eligibility make global cost claims unreliable.

Evidence review

What the public record currently supports.

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

01

Product classification comes first

The Crypto.com App is a custodial consumer experience, the Exchange is an order-book venue and Onchain is presented as self-custody. A meaningful verdict has to state which of these products it covers.

S01S02

Evidence reviewed
02

Entity varies with product and market

Public documents name multiple Foris entities and a separate Onchain-wallet entity. Singapore and Dubai regulator registers provide checkable evidence for particular entities and permissions, not blanket approval of every Crypto.com service worldwide.

S02S03S08S09

Evidence reviewed
03

Cost is route-specific

The Exchange publishes tiered maker/taker fees, while the EEA App publishes its own limits and charges. We therefore compare a complete buy, transfer and withdrawal recipe instead of repeating one promotional fee.

S04S05

Evidence reviewed
04

Security and reserves need scope

Crypto.com describes account and custody controls, but provider claims need testing. Its reserve page and associated 2022 materials are dated evidence; they do not prove present-day solvency or replace audited financial statements.

S06S07

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

Crypto.com can work well for someone who wants a connected consumer ecosystem, but only after choosing between the custodial App, the order-book Exchange and the self-custody Onchain wallet. A brand-level verdict is too coarse to support a cost or safety decision.

Source register · retrieved 17 Aug 2026
02

Who should not choose it

Avoid treating it as one product if you need simple, portable pricing or one custody model. It is also a weak fit for anyone unwilling to verify regional eligibility and the exact Foris entity before using a card, app, exchange or onchain feature.

Source register · retrieved 17 Aug 2026
03

Product and legal-entity scope

This exchange dossier covers the custodial App and Exchange. Onchain is a separate self-custody product. Public registers support specific Foris entities and permissions in Singapore and Dubai; they do not authorise every branded service globally.

Source register · retrieved 17 Aug 2026
04

Custody and security controls

Crypto.com’s own comparison says the App controls the keys while Onchain leaves them with the user. The security page describes passkeys, MFA, withdrawal whitelisting and certification claims; the assessment records those as scoped provider evidence until reports and live control behaviour are matched.

Source register · retrieved 17 Aug 2026
05

Regulation and customer protection

The MAS directory identifies Foris DAX Asia Pte. Ltd. as a Major Payment Institution for digital payment token service, while VARA lists specific licensed activities for Foris DAX Middle East FZE. Both records are market- and entity-specific, not a global warranty.

Source register · retrieved 17 Aug 2026
06

Fees and total-cost recipe

Price the same EUR 1,000 purchase through the App and Exchange, then transfer or withdraw the same asset. Capture App quote/spread, Exchange maker/taker fee and fill, funding fee, conversion, withdrawal/network charge and the final amount received.

Source register · retrieved 17 Aug 2026
07

Funding, withdrawal and exit

App, Exchange and Onchain transfers may feel integrated but cross product and custody boundaries. The test must record which ledger holds the asset, any internal-transfer rule, available withdrawal networks, whitelist delay and external arrival.

Source register · retrieved 17 Aug 2026
08

Execution, API or wallet permissions

The Exchange provides an order book and APIs; the App is closer to a quoted brokerage flow. These surfaces need separate execution tests, and Onchain permissions must not be folded into the exchange result.

Source register · retrieved 17 Aug 2026
09

Privacy and telemetry

App KYC, device security, contacts and linked-product functions create a different data surface from Onchain. The live review should map each permission and third-party route by product rather than asserting that the brand is uniformly private or invasive.

Source register · retrieved 17 Aug 2026
10

Support and dispute route

Run separate cases for App and Exchange because identity, evidence and escalation may differ. Save the applicable terms, case transcript, response owner and the external complaint path available for the named entity.

Source register · retrieved 17 Aug 2026

Fit boundary

Four situations, before a brand preference.

Fits

You value connected App, Exchange and onchain routes.

The ecosystem can reduce product discovery friction when each boundary is understood.

Fits

You will compare the App quote against the Exchange receipt.

The two surfaces create a useful matched total-cost scenario.

Does not fit

You want one custody and pricing model.

App, Exchange and Onchain allocate keys and costs differently.

Does not fit

You assume one licence covers the brand globally.

MAS and VARA records are entity-, activity- and market-specific.

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

App versus Exchange receipt

Fixed inputs: Same eligible EEA account, EUR 1,000, same asset and five-minute quote window.

Capture: Funding cost, preview, spread reference, trading fee, fill and amount available to withdraw.

S2

Product-boundary transfer

Fixed inputs: App balance, Exchange balance and external self-custody destination with one supported network.

Capture: Custody state, internal-transfer rules, whitelist controls, fees, holds and external transaction.

S3

Support escalation

Fixed inputs: One non-urgent fee or withdrawal-policy question tied to the named entity.

Capture: Channel, response ownership, evidence demands, answer accuracy and written escalation route.

S4

Privacy boundary by product

Fixed inputs: Fresh App and Onchain installs with default permissions recorded; no valuable assets.

Capture: Identity requirement, device/contact permissions, telemetry controls, linked-product data flows and deletion/export route.

Incident and change timeline

What changed the risk picture.

  1. The prominent reserves material is rooted in a December 2022 procedure.

    Do not convert an old scoped procedure into a present-day full financial audit.

  2. VARA lists the issuance date for the Dubai VASP licence.

    Use the register’s named entity, activities and conditions rather than a brand-wide regulated claim.

  3. Product-boundary, security and regulator pages re-retrieved.

    The account protocol can now lock product, market and entity before scenario work.

Alternatives

Choose by responsibility, not fame.

Coinbase

A narrower custodial route and listed-company disclosures are more important than a broad product ecosystem.

Trust Wallet

The primary need is multi-chain self-custody and the user accepts seed, signing and release responsibility.

Evidence confidence

Medium confidence, with a visible stop gate.

Supported
Product-boundary documents and two official regulator registers establish useful scope; current fee and security pages support attributable claims.
Unresolved
Matched App/Exchange costs, current reserve assurance, regional support, telemetry and external withdrawal outcomes are the variables most likely to change the conclusion.
What would change the conclusion
A clearer unified cost disclosure, current scoped assurance artefact and strong reproducible exit results would improve the conclusion; product/entity ambiguity or failed exit controls would weaken it.

Method applied

How this file is challenged.

  1. Select App, Exchange or Onchain before collecting evidence.
  2. Name residence, Foris entity and permission from an authoritative register.
  3. Run matched cost and asset-path scenarios without mixing custody models.
  4. Keep security certifications, reserve procedures and runtime controls in separate evidence columns.

Dossier change log

Material editorial changes.

Added a product-boundary decision chain with matched App/Exchange cost, custody transfer and dispute scenarios; official registers were rechecked.

FAQ

Questions that decide whether the product fits.

Is Crypto.com Onchain covered by the exchange verdict?

No. It is self-custodial and requires the wallet method.

Does a Dubai licence cover every Crypto.com service?

No. The VARA register names one entity, listed activities and conditions in Dubai.

Is the proof-of-reserves page a current financial audit?

No. Read the procedure date and scope; it does not replace audited financial statements or prove future solvency.

Can App and Exchange fees be compared from one table?

No. They use different transaction surfaces; compare timestamped receipts for the same asset, amount and account region.

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.