The clearest signal from the Custodia case is not that crypto banks are shut out of the Federal Reserve forever. It is that the Fed has now won clear legal backing to decide who gets a master account, even as it starts testing a narrower access model for crypto firms.
Custodia’s five-year push ended with a 7-3 denial
Custodia Bank first applied for a Federal Reserve master account in October 2020, seeking direct access to the central bank’s payment infrastructure instead of relying on intermediary banks. That matters because a master account can reduce settlement friction, cut counterparty exposure, and make a crypto-focused bank operationally more competitive.
The application was rejected in early 2023 after the Fed raised concerns about Custodia’s crypto-heavy business model, its risk controls, and broader systemic risk. Custodia then argued in court that the Monetary Control Act entitled an eligible state-chartered bank to Fed services, but the U.S. Court of Appeals for the Tenth Circuit rejected its petition for rehearing by a 7-3 vote, leaving the Fed’s discretion intact.
The majority’s position was straightforward: the Federal Reserve must be able to deny access when it sees risk to the payments system or financial stability. In dissent, Chief Judge Timothy Tymkovich argued that denying a master account is “akin to a death sentence” for a bank’s operations, which sharpened the practical point even as he lost on the legal one.
The ruling affirmed gatekeeping power, not a blanket crypto ban
The easy misread is to treat this as a final court-backed ban on crypto firms touching Fed infrastructure. The actual holding is narrower and more important: regional Federal Reserve Banks have broad room to approve or deny master accounts, and courts are not forcing them to say yes just because an institution has a state charter.
That distinction changes how the market should read future developments. The legal barrier for forcing access is now higher, but a policy pathway still exists if the Fed itself chooses to create one, which turns attention away from courtroom strategy and toward supervisory design, application criteria, and implementation by individual Reserve Banks.
Kraken’s March 4 account changed the practical picture
Just before the appeals decision, the Federal Reserve Bank of Kansas City granted Kraken a limited master account on March 4, 2026. The account reportedly provides partial access to Fedwire rather than the full service bundle available to traditional banks, which makes it less a breakthrough in equal treatment than a proof of concept for restricted access.
The national Federal Reserve Board is also developing a “skinny” master account framework for crypto firms, though there is still no application timeline. That is why the Custodia loss and Kraken approval should be read together: one confirms the Fed can say no, while the other shows it may say yes under tighter, purpose-built terms.
Full account versus limited account: the difference that now matters
For crypto banks and market participants, the operational gap between outright denial, a skinny account, and a full master account is now more important than broad rhetoric about access.
| Pathway | Current example | What it appears to allow | Main constraint |
|---|---|---|---|
| Full master account | What Custodia sought | Direct access to Fed payment rails and core account functions | Fed retains discretion to deny based on risk and policy concerns |
| Limited or “skinny” master account | Kraken, via Kansas City Fed on March 4, 2026 | Partial Fedwire connectivity or narrower payment access | Not equivalent to full banking access; framework still incomplete |
| No master account | Custodia after the ruling | Continued operation through correspondent banks or alternative arrangements | Higher cost, slower settlement, more operational dependency |
That comparison matters for liquidity and business viability. A firm with no account stays dependent on correspondent banks and their risk tolerance, while a skinny account may improve payment efficiency without fully solving access, reserve management, or product expansion limits. For investors and operators, that means “Fed access” is no longer a binary headline; the scope of access is the real variable.
The next checkpoint is policy language, not another broad legal theory
The immediate question is how the Federal Reserve formalizes the skinny account framework and whether regional Reserve Banks apply it consistently. Because the system is regional, the same category of crypto applicant may not face identical treatment in Kansas City and elsewhere, which introduces a form of regulatory fragmentation even inside the Fed structure.
Firms watching this area should focus on the eventual criteria: what business models qualify, what risk-control standards are required, which payment functions are included, and whether access can be expanded over time. Until those details are published, Kraken’s approval is a useful signal but not a standard that other crypto banks can confidently underwrite against.
Quick checks for readers following the story
Does Custodia’s loss end all Fed access options for crypto firms?
No. It ends Custodia’s attempt to force access through this legal route, but it does not prevent the Fed from offering limited access under a new policy.
Why is Kraken’s account important if it is limited?
Because it shows the Fed system is willing to test partial access instead of only choosing between full approval and total exclusion.
What is the main risk in overreading this moment?
Treating one limited approval as a settled nationwide framework when the Federal Reserve has not yet published final criteria or an application timeline.
About the Author
