- Clear public distinction between custodial App and self-custody Onchain
- Exchange fee and feature documentation is accessible
- Some region-specific regulatory records are directly verifiable
EXECUTION EVIDENCE FILE
Crypto.com
Three product surfaces—App, Exchange and Onchain—whose custody, fees and legal providers must not be collapsed into one review.
- REVIEW DATE
- EVIDENCE STATUS
- partially verified
- CONFIDENCE
- medium
Written by Beacon Ratio Editorial TeamIndependently reviewed by Beacon Ratio Review TeamPublished by Beacon Ratio Team
EDITORIAL ASSESSMENT
Crypto.com documents a broad exchange toolset, but the first analytical task is separation: App brokerage, Exchange order book and Onchain self-custody have different costs and responsibilities. Live execution remains unbenchmarked.
- SUITABLE FOR
- Readers prepared to select a specific Crypto.com product, region and legal entity before comparing price or functionality.
- PRIMARY TRADE-OFF
- Breadth across retail, exchange and onchain interfaces is convenient, but creates more scope for misleading all-brand fee and safety claims.
- Fees differ materially by product, tier and region
- Margin and derivatives are qualification-dependent
- The linked PoR work is a December 2022 AUP snapshot
From interface claim to executable test.
Three execution contexts
The App is a custodial brokerage surface, the Exchange is a distinct trading venue, and Onchain is self-custody. Their controls, quotes and fees cannot be averaged into a single Crypto.com execution result.
Sources: Crypto.com App versus Crypto.com Onchain ↗ · Crypto.com Onchain Terms ↗
Published fee evidence
The Exchange schedule reviewed on 9 July 2026 showed a Level 1 example of 0.250% maker and 0.500% taker. The EEA App published different figures, confirming that product and region must remain attached to every fee.
Sources: Crypto.com Exchange Fees & Limits ↗ · Crypto.com App Fees & Limits — EEA ↗
Order and leverage boundary
The Exchange documents spot and, where eligible, margin and derivatives. Feature documentation proves an interface exists; it does not show liquidity, realised slippage, uptime or universal availability.
Sources: Crypto.com Exchange Fees & Limits ↗
Security and reserve claims
Crypto.com lists account controls and security certifications. Its public PoR page points to a December 2022 agreed-upon-procedures snapshot, which is historical inclusion evidence rather than a current audit or solvency opinion.
Sources: Crypto.com security disclosures ↗ · Crypto.com Proof of Reserves ↗
Execution conclusion
The documented Exchange is testable, but no Beacon Ratio account-opening, funding, order, API or withdrawal observation exists. The correct editorial state is reviewed public evidence with hands-on verification planned.
Sources: Crypto.com App versus Crypto.com Onchain ↗ · Crypto.com Exchange Fees & Limits ↗ · Crypto.com security disclosures ↗
Where this product fits—and where it does not.
Readers prepared to select a specific Crypto.com product, region and legal entity before comparing price or functionality.
Readers who want a single all-brand fee, custody or regulatory verdict, or who are unwilling to verify whether the Exchange is available in their market.
Clear public distinction between custodial App and self-custody Onchain
Coinbase offers a simpler two-path retail/Advanced comparison; Kraken provides a more explicit public funding matrix. A separate wallet should be considered when self-custody, not ecosystem continuity, is the priority.
- REVIEW SCOPE
- Crypto.com App brokerage, Crypto.com Exchange order book and Crypto.com Onchain wallet are three separate research subjects joined only for navigation. This brief does not transfer one product's fees, entity or controls to another.
- ENTITY / CONTROL BOUNDARY
- The App is custodial, Onchain is user-custodied, and the Exchange has its own trading surface. Region-specific legal entities and permissions must be attached to the chosen product.
Concrete routes, not generic personas.
Primary decision route
An eligible user compares an App purchase quote with an Exchange spot order, then either withdraws to an external address or transfers to Onchain while keeping every product boundary visible.
App route
Fiat funding → App quote → custodial balance → withdrawal. Open question: Embedded spread, payment-rail cost, transfer treatment, withdrawal fee and settlement delay.
Exchange route
Funded balance → spot order-book execution → external withdrawal. Open question: Depth, slippage, API errors, internal-transfer conditions and network completion.
Alternative route
Coinbase offers a simpler two-path retail/Advanced comparison; Kraken provides a more explicit public funding matrix. A separate wallet should be considered when self-custody, not ecosystem continuity, is the priority.
Decision factors with evidence state and the next test attached.
| Decision factor | Current finding and adjacent evidence | Evidence state | Verification protocol |
|---|---|---|---|
| Product and entity scope | App, Exchange and Onchain change custody, identity and execution. A regulator record for one entity or market cannot authorise every product globally. Sources: Crypto.com App versus Crypto.com Onchain ↗ · Crypto.com Onchain Terms ↗ | Documented | Bind the account screen, terms and regulator record to one region and product. |
| Custody and keys | The App holds keys for the user; Onchain gives the user signing control. An internal transfer between surfaces is therefore a custody transition, not just navigation. Sources: Crypto.com App versus Crypto.com Onchain ↗ · Crypto.com Onchain Terms ↗ | Documented | Trace ownership, address and recovery state at each transition with an empty or minimal-value wallet. |
| Security and assurance | Crypto.com publishes security controls and certification claims; scope and current validity must be confirmed instead of converting badges into an outcome. Sources: Crypto.com security disclosures ↗ | Mixed | Validate certificate scope and observe account-control defaults and recovery. |
| Regulatory evidence | Permissions are entity- and jurisdiction-specific. The present file does not infer global authorisation from a brand licensing page. | Mixed | Match a regulator entry to the contract and product actually offered to the account. |
| Depth, slippage and API | Exchange documentation shows an order-book surface, not realised depth or API continuity. App quotes must be compared separately because they are not exchange fills. Sources: Crypto.com Exchange Fees & Limits ↗ · Crypto.com App Fees & Limits — EEA ↗ | Planned verification | Archive matched quotes, book levels, order events and timestamped API responses. |
| Identity and data | The custodial App requires identity checks; Onchain can operate without the same account, but embedded services and network providers can create separate data flows. Sources: Crypto.com App versus Crypto.com Onchain ↗ · Crypto.com Onchain Terms ↗ | Mixed | Observe network destinations and disclosures for each product without assuming wallet anonymity. |
| Support and disputes | Support may bridge multiple products, but recovery authority differs sharply when the user controls the keys. Sources: Crypto.com App versus Crypto.com Onchain ↗ · Crypto.com Onchain Terms ↗ | Planned verification | Test one product-classification enquiry and record whether escalation preserves the correct custody boundary. |
| Reserves and change control | The linked PoR material is bounded historical evidence, not a continuous audit. Dynamic product availability and fees require dated refreshes. Sources: Crypto.com Proof of Reserves ↗ · Crypto.com Exchange Fees & Limits ↗ | Mixed | Recheck PoR date, covered assets, fee page and market availability before release. |
Fee schedules are inputs, not outcomes.
| Scenario | Route | Documented inputs | Open question |
|---|---|---|---|
| App route | Fiat funding → App quote → custodial balance → withdrawal | Region-specific displayed fee/limits and final quoted amount. Sources: Crypto.com App Fees & Limits — EEA ↗ · Crypto.com App versus Crypto.com Onchain ↗ | Embedded spread, payment-rail cost, transfer treatment, withdrawal fee and settlement delay. |
| Exchange route | Funded balance → spot order-book execution → external withdrawal | Published maker/taker tier and displayed withdrawal inputs. Sources: Crypto.com Exchange Fees & Limits ↗ · Crypto.com App versus Crypto.com Onchain ↗ | Depth, slippage, API errors, internal-transfer conditions and network completion. |
How this file becomes a measured result
Create independent App, Exchange and Onchain protocols. Match region, entity, asset and timestamp; collect quoted price, order fill, explicit fee, funding charge, transfer treatment, withdrawal fee and network settlement.
What the documents can support
Medium for documented product separation and selected public security or regulator records; insufficient for live quotes, order-book quality, API reliability, support and withdrawal execution.
Conclusion-change gates
- A region-specific entity or product permission changes.
- Current live fee material differs from the archived schedule.
- Matched App and Exchange routes establish repeatable total-cost or reliability differences.
Evolution stays visible.
Rechecked App/Onchain boundary, Exchange fee surface and security disclosures; expanded three-product route tests.
Created the first product-separated evidence file.
A region-specific entity or product permission changes. Current live fee material differs from the archived schedule. Matched App and Exchange routes establish repeatable total-cost or reliability differences.
Questions that change the decision.
Is Crypto.com Onchain the same custody product as the App?
No. The official comparison describes Onchain as user-custodied and the App as custodial.
Can one fee table cover the whole brand?
No. Product, region, tier, payment rail and withdrawal path all affect total cost.
Has the Exchange been latency-tested here?
No. Order and API observations remain scheduled, not completed.
What would change this conclusion?
A region-specific entity or product permission changes.
6 records reviewed
Provider pages establish provider statements. Terms, filings and regulator records retain their narrower legal or historical scope. Dynamic sources were retrieved on 16 August 2026.
- productRetrieved 2026-08-16Crypto.com App versus Crypto.com Onchain ↗
- termsRetrieved 2026-08-16Crypto.com Onchain Terms ↗
- productRetrieved 2026-08-16Crypto.com Exchange Fees & Limits ↗
- productRetrieved 2026-08-16Crypto.com App Fees & Limits — EEA ↗
- technicalRetrieved 2026-08-16Crypto.com security disclosures ↗
- productRetrieved 2026-08-16Crypto.com Proof of Reserves ↗