The OCC granted Crypto.com conditional approval for a national trust bank charter on Feb. 23, 2026, expanding a list of similar conditional approvals previously issued to Ripple and other digital-asset firms. The practical significance is the creation of a clearer federal perimeter for custody and stablecoin reserve management, with direct implications for how institutional settlement and custody rails are designed.
These charters are not “live” authorizations yet; they remain conditional and depend on pre-opening requirements for capital, governance, compliance, and risk controls. Until those conditions are satisfied and verified, timelines and go-live scope remain subject to supervisory clearance rather than product roadmaps.
🚨NEW: @cryptocom joins @Ripple, @circle, @Paxos and @Fidelity in getting conditional approval for a @USOCC trust bank charter. @BitGo received full OCC approval to convert its state trust company into a nationally chartered trust bank late last year. https://t.co/TmlECHHSO4
— Eleanor Terrett (@EleanorTerrett) February 23, 2026
What was approved and who else is in the cohort
Crypto.com’s conditional approval is tied to Foris Dax National Trust Bank (d.b.a. Crypto.com National Trust Bank) and is described as supporting federally regulated custody, multi-chain staking including Cronos, and trade settlement for digital assets. The design intent is to bring core custody and settlement functions under OCC-supervised trust-bank controls.
The same reporting set describes other conditional approvals and conversions granted on or around Dec. 12, 2025, including Ripple National Trust Bank for RLUSD reserve custody and fiduciary services, Circle’s First National Digital Currency Bank for stablecoin and reserves, and Paxos, BitGo, and Fidelity conversions focused on custody and related services. Stripe’s Bridge also received conditional approval on Feb. 18, 2026 for custody and stablecoin orchestration, indicating the OCC is building a consistent charter pathway for multiple business models.
What “conditional” means operationally
OCC notices cited in the text emphasize pre-opening and ongoing supervisory expectations, including capital adequacy, board governance, comprehensive BSA/AML and consumer compliance programs, and robust operational risk management. The message is that regulatory acceptance hinges on bank-grade controls, not just on technical capability or market share.
For firms planning to rely on these entities, that conditional status should be treated as a gating variable rather than a certainty. The operational posture is “prepare to integrate,” but do not assume production-grade availability until supervisory milestones are met.
How custody topology and settlement rails change
Bringing custody and stablecoin reserves into federally chartered trust banks can simplify multi-jurisdiction licensing complexity and standardize the settlement and custody perimeter for institutional counterparties. For market makers and treasuries, that can reduce friction in onboarding and routing, because reserve custody and settlement are anchored to a federal supervisory framework.
For engineering and infrastructure teams, the shift raises the bar on integrations: authenticated custody APIs, hardened key-management interfaces, and explicit SLAs around custody and settlement availability. The filings’ emphasis on custody, trade settlement, and staking implies deeper expectations on audited operational procedures and resilience planning under OCC supervision.
There is also an inherent concentration trade-off: a smaller set of chartered entities acting as default custody anchors can improve predictability for reserve attestations and counterparty assessments while increasing single-point-of-failure risk. To manage that, teams will need redundancy plans, client diversity, and cross-institution failover topologies that preserve settlement continuity and service availability.
Final authorization depends on completion of pre-opening conditions and sustained compliance under supervision, so the approvals remain conditional for now. The near-term execution priority for devops and network architects is to prepare for bank-level custody endpoints while designing fallback routing and resilience controls for a more bank-centric custody landscape.