- Clear public distinction between simple and Advanced fee mechanics
- Public-company filings add incident and financial-risk context
- Hosted custody and self-custody Wallet are explicitly separable
EXECUTION EVIDENCE FILE
Coinbase
A documented split between simple brokerage and order-book execution, with regional entity and incident boundaries that matter to any cost or reliability claim.
- 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
Coinbase presents two materially different execution paths: convenience-led Simple transactions and Coinbase Advanced order-book trading. The documents are strong enough to map the route, but not to award an execution score without matched live orders, funding and withdrawal tests.
- SUITABLE FOR
- Readers who want a clearly documented custodial platform and can choose deliberately between a quoted retail transaction and an order-book interface.
- PRIMARY TRADE-OFF
- The simpler route reduces interface work but can combine a displayed Coinbase fee with spread; Advanced exposes maker/taker mechanics but asks more of the trader.
- Exact Advanced tiers can require account context and change with volume
- No Beacon Ratio fill, spread, latency or withdrawal benchmark has been run
- Licensing and cash protection cannot be generalised across markets
From interface claim to executable test.
Execution surface
Simple Buy, Sell and Convert use a quoted transaction path; Advanced uses an order book. Those are different test subjects, so a single headline fee would conceal the choice a user actually makes.
Sources: Coinbase pricing and fees disclosures ↗ · Coinbase Advanced fees ↗
Cost path
Coinbase says a Simple transaction can include a Coinbase fee and spread, while Advanced applies maker/taker pricing without an embedded spread. Total cost still needs funding, slippage and withdrawal added to the trade fee.
Sources: Coinbase pricing and fees disclosures ↗ · Coinbase Advanced fees ↗
Custody boundary
Coinbase.com hosted balances are custodial, whereas Coinbase Wallet is a separate self-custody product. The US agreement says supported assets are held for customers' benefit, but crypto is not FDIC or SIPC insured.
Sources: Coinbase User Agreement — United States ↗ · What Coinbase does with digital assets ↗
Operational evidence
The May 2025 filing describes data obtained through paid overseas support personnel and says passwords and private keys were not compromised. It is material evidence about the support chain, not a measurement of present order-engine availability.
Sources: Coinbase Form 8-K — May 2025 support-chain incident ↗
Decision boundary
Public records support a credible execution test plan, not a numeric verdict. We still need region-matched account eligibility, fee tier, API timing, rejection behaviour and a completed withdrawal route.
Sources: Coinbase User Agreement — United States ↗ · Coinbase Advanced fees ↗ · Coinbase Form 8-K — May 2025 support-chain incident ↗
Where this product fits—and where it does not.
Readers who want a clearly documented custodial platform and can choose deliberately between a quoted retail transaction and an order-book interface.
Readers who need anonymous access, deterministic low-latency execution, a universal fee promise, or one conclusion that applies to every Coinbase entity and product.
Clear public distinction between simple and Advanced fee mechanics
Kraken Pro is the closest documented alternative for a user prioritising a visible order-book path and withdrawal-hold disclosure; a self-custody wallet is an exit tool, not a substitute venue.
- REVIEW SCOPE
- Coinbase retail hosted account and Coinbase Advanced, with the US agreement as the legal reference. Coinbase Wallet, institutional Prime, derivatives and non-US entities are outside this file unless explicitly named.
- ENTITY / CONTROL BOUNDARY
- The reviewed US agreement names Coinbase, Inc. Hosted crypto remains under Coinbase-controlled keys, while the separate unhosted Wallet changes the control model entirely.
Concrete routes, not generic personas.
Primary decision route
A US retail user funds USD, compares a Simple quote with an Advanced marketable order, then withdraws the acquired asset to a self-controlled address.
Convenience route
Bank funding → Simple quote → hosted balance → external withdrawal. Open question: Effective spread versus a contemporaneous market, settlement hold, slippage after quote acceptance and final withdrawal charge.
Order-book route
USD balance → Advanced marketable order → external withdrawal. Open question: Queue position, realised slippage, rejected quantity, API overhead and exit cost at the test timestamp.
Alternative route
Kraken Pro is the closest documented alternative for a user prioritising a visible order-book path and withdrawal-hold disclosure; a self-custody wallet is an exit tool, not a substitute venue.
Decision factors with evidence state and the next test attached.
| Decision factor | Current finding and adjacent evidence | Evidence state | Verification protocol |
|---|---|---|---|
| Scope and entity | Simple transactions and Advanced order-book trading are different execution products. The US agreement cannot be exported to another jurisdiction without its local terms. Sources: Coinbase User Agreement — United States ↗ · Coinbase Advanced fees ↗ | Documented | Capture the agreement and entity shown to the funded test account. |
| Custody and keys | Coinbase controls hosted-wallet keys and records customer balances; Coinbase Wallet is separately unhosted. Title language does not remove outage, legal-order or operational access constraints. Sources: Coinbase User Agreement — United States ↗ · What Coinbase does with digital assets ↗ | Documented | Complete a small withdrawal and record every approval, hold and status transition. |
| Security and reliability | The 2025 filing is evidence of a support-chain data incident, not proof about current matching-engine resilience. The agreement also declines to guarantee uninterrupted access or order acceptance. Sources: Coinbase Form 8-K — May 2025 support-chain incident ↗ · Coinbase User Agreement — United States ↗ | Mixed | Measure login, acknowledgement, cancel and support escalation across normal and volatile windows. |
| Regulatory evidence | A public-company filing and a named US contracting entity improve traceability, but they do not establish the permissions or protections of every regional service. Sources: Coinbase User Agreement — United States ↗ · Coinbase Form 8-K — May 2025 support-chain incident ↗ | Documented | Bind every regulatory claim to the account entity and product used. |
| Depth, slippage and API | Advanced exposes order-book mechanics; Simple presents an executable quote. Neither public help page establishes depth at the chosen notional, queue position, reject rates or API tail latency. Sources: Coinbase pricing and fees disclosures ↗ · Coinbase Advanced fees ↗ | Planned verification | Run matched notionals and retain book snapshots, client/server timestamps and raw order events. |
| Identity and data | The US agreement permits identity, bank, device and fraud-prevention inquiries. This is a regulated hosted-account data path, not a privacy-minimised wallet flow. | Documented | Map actual onboarding fields, vendors and retention disclosures without submitting unnecessary data. |
| Support and disputes | The agreement contains complaint and arbitration routes; the 2025 incident makes support-vendor access a material operational dependency. Sources: Coinbase User Agreement — United States ↗ · Coinbase Form 8-K — May 2025 support-chain incident ↗ | Mixed | Open a harmless support case and record routing, authentication and resolution time. |
| Incidents and change control | Terms, pricing and supported assets can change. A dated source snapshot is therefore part of the result, not administrative decoration. Sources: Coinbase User Agreement — United States ↗ · Coinbase pricing and fees disclosures ↗ | Documented | Diff terms and fee pages before publication and after any material product change. |
Fee schedules are inputs, not outcomes.
| Scenario | Route | Documented inputs | Open question |
|---|---|---|---|
| Convenience route | Bank funding → Simple quote → hosted balance → external withdrawal | Displayed Coinbase fee and any quoted spread; bank and network charges disclosed at authorisation. Sources: Coinbase pricing and fees disclosures ↗ · Coinbase User Agreement — United States ↗ | Effective spread versus a contemporaneous market, settlement hold, slippage after quote acceptance and final withdrawal charge. |
| Order-book route | USD balance → Advanced marketable order → external withdrawal | Maker/taker framework and account-volume tier logic. Sources: Coinbase Advanced fees ↗ · Coinbase User Agreement — United States ↗ | Queue position, realised slippage, rejected quantity, API overhead and exit cost at the test timestamp. |
How this file becomes a measured result
Freeze legal entity, account tier, asset pair, notional, funding rail and observation window; archive the quote, best bid/ask, order events, fill, explicit fees, settlement hold and withdrawal receipt. Run Simple and Advanced as separate products.
What the documents can support
Medium for the documented US product split, custody wording and 2025 incident record; insufficient for live spread, depth, latency, uptime, support resolution and present withdrawal performance.
Conclusion-change gates
- A region-matched live route materially contradicts the documented fee or hold model.
- Coinbase changes the applicable entity, custody terms or Advanced fee construction.
- Repeated order or withdrawal tests establish reproducible tail-latency or support findings.
Evolution stays visible.
Rechecked US terms, Simple pricing, Advanced fees and the SEC incident filing; added execution scenario and total-cost gates.
Opened the first multi-source public-evidence file without a numeric rating.
A region-matched live route materially contradicts the documented fee or hold model. Coinbase changes the applicable entity, custody terms or Advanced fee construction. Repeated order or withdrawal tests establish reproducible tail-latency or support findings.
Questions that change the decision.
Is Coinbase Simple cheaper than Advanced?
The documents do not support a universal answer. Simple and Advanced use different price construction, so a same-time, same-notional fill comparison is required.
Does hosted custody mean Coinbase owns the assets?
The reviewed US terms describe customer title and Coinbase-controlled keys. That is still custodial access and must be read with the full terms and jurisdiction.
Has Beacon Ratio tested Coinbase execution?
No. The live funding, order, API, support and withdrawal protocol is planned.
What would change this conclusion?
A region-matched live route materially contradicts the documented fee or hold model.
5 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.
- termsRetrieved 2026-08-16Coinbase User Agreement — United States ↗
- productRetrieved 2026-08-16Coinbase pricing and fees disclosures ↗
- productRetrieved 2026-08-16Coinbase Advanced fees ↗
- productRetrieved 2026-08-16What Coinbase does with digital assets ↗
- filingRetrieved 2026-08-16Coinbase Form 8-K — May 2025 support-chain incident ↗