Court ends crypto bank’s five-year legal battle
A US federal appeals court has effectively ended Custodia Bank’s five-year legal fight for access to the Federal Reserve’s payment system. The Tenth Circuit Court of Appeals voted 7-3 on Friday not to hear the crypto-focused bank’s final appeal, closing the door on its challenge to the Fed’s authority over granting master accounts.
This decision marks the conclusion of a lengthy battle that began back in October 2020 when Custodia first applied for what’s essentially a direct line to the central bank’s payment rails. Without a master account, financial institutions have to rely on intermediary banks to settle transactions—something that creates additional costs and complexities, particularly for crypto firms trying to operate within traditional banking systems.
The legal arguments and their limits
Custodia’s argument centered on the Monetary Control Act, which the bank claimed entitled state-chartered institutions to access Federal Reserve services. They thought this meant they should get a master account automatically, or at least have a clear path to one. But multiple courts have now disagreed, ruling that the Fed retains discretion over these decisions.
I think what’s interesting here is how the legal interpretation played out. The bank saw the law one way, the courts saw it another. And when you’re dealing with financial regulation, especially with something as central as Fed access, the interpretation tends to favor the regulator’s discretion. That’s just how these things often go.
A dissenting voice and what it means
While only three judges sided with Custodia, one of them, Judge Timothy Tymkovich, wrote a pretty strong dissent. He called a master account “indispensable” for a bank’s operations and said being denied one was “akin to a death sentence.” That’s strong language from a federal judge.
He also pointed out something curious: three months after Custodia’s initial application, the Fed told the bank it was eligible and that there were “no showstoppers” with its paperwork. That creates a bit of a confusing picture, doesn’t it? The bank gets told everything looks good, then gets rejected, then spends years fighting in court only to have the door closed completely.
The Kraken development and possible paths forward
What makes this particularly noteworthy is the timing. Just earlier this month, Kraken became the first crypto platform to receive a master account from the Federal Reserve Bank of Kansas City. Now, Kraken’s account doesn’t include the full range of services traditional banks get—it’s what some are calling a “skinny” or limited master account—but it’s still access to the Fedwire payments system.
This raises questions about why one crypto firm gets access while another doesn’t. Is it about the specific business model? The regulatory approach? Or just different Fed districts making different decisions? The Kansas City Fed’s move with Kraken did raise hopes that US regulators might offer limited master accounts to crypto firms, but Custodia’s case shows it’s not a guaranteed path.
Perhaps the lesson here is that crypto firms need to work within the existing regulatory framework rather than trying to challenge its boundaries in court. Or maybe it’s that different approaches yield different results. Kraken went through the application process and got a limited account; Custodia applied, got rejected, sued, and lost.
The whole situation highlights the ongoing tension between innovative financial firms and established regulatory systems. Crypto companies want access to traditional banking infrastructure, but regulators are cautious about opening those gates too wide. And when courts get involved, they tend to defer to regulatory expertise—which is what happened here.
For Custodia, this means going back to the drawing board or finding alternative arrangements. For the broader crypto industry, it’s another data point in the complex relationship with traditional finance. The path forward isn’t clear, but it’s becoming increasingly apparent that legal challenges have their limits when it comes to changing regulatory access policies.
