Custodia Bank Fed Access 🔥 What Supreme Court Means (2026)
Custodia Bank Fed access denied—now what? Get clarity on Fed master account rules, crypto bank regulation, and Fed payment system impact for banks & Kraken Financial.

Custodia Bank's Supreme Court Setback Leaves Fed Access Uncertain
Custodia Bank's push for direct access to the Federal Reserve's payment system has hit another legal stop. The US Supreme Court declined to hear the Wyoming-chartered bank's appeal, leaving in place a lower-court ruling that gives Federal Reserve banks discretion to reject master account applications. The Court didn't decide the underlying dispute on the merits - it simply declined review, so the appellate decision remains the operative result.
And that distinction matters. Custodia's case wasn't only about whether a crypto-focused bank could use Fed payment services. It raised a bigger question: if a state-chartered bank meets the eligibility criteria, does a Federal Reserve bank have to provide a master account? The appeals court said no. That means approval isn't automatic just because an applicant has a state bank charter or can clear basic requirements.
For banks serving digital-asset businesses, the decision makes direct payment access harder to treat like an entitlement. For customers and companies, it also helps explain why some institutions still rely on correspondent banks or operate with more limited access. Here's what the Supreme Court's move does, how Custodia's case got this far, and what it could mean for other crypto-focused banks.
What did the Supreme Court decide
The Supreme Court declined to hear Custodia Bank's appeal. The immediate effect is simple: the federal appeals court's decision against the bank stays in place. That earlier ruling held that Federal Reserve banks aren't required to grant master accounts to every institution that can apply.
This also isn't the same thing as a broad Supreme Court win for one side or the other on crypto banks getting Fed access. The justices didn't issue a new opinion answering that wider question. They declined to review the case, leaving the lower court's reasoning untouched. Practically speaking, Custodia didn't get the remedy it wanted, and the discretion recognized by the appeals court still matters for future applications.
Eligibility is not the same as approval
One headline shortcut to avoid: eligibility doesn't automatically mean approval. A bank can qualify to apply for a master account without having a guaranteed right to receive one. The appeals court's view leaves room for Federal Reserve banks to evaluate applications instead of treating eligibility as a straight path to access.
That creates a real gap between holding a state bank charter and getting direct access to central-bank payment services. A state regulator can authorize a bank to operate, but that doesn't necessarily compel a Federal Reserve bank to provide a master account. The two questions are handled under different authorities and responsibilities.
In March, US Circuit Judge Timothy Tymkovich criticized the appeals court's decision in a dissent. He argued that broad discretion could let Federal Reserve banks override state banking decisions. As he put it, Without a master account, a bank cannot operate in the modern banking system.
That was a dissenting view, not the controlling outcome - but it captures the core tension at the center of the dispute.
What the decision does not establish
The Supreme Court's refusal doesn't mean every crypto-focused application will be denied. It also doesn't mean Custodia has zero options moving forward. The path forward could include another application or a request for more limited access under a different proposal.
The narrower takeaway is more practical: a bank can't assume a state charter alone entitles it to a Federal Reserve master account. Applicants still have to plan for Fed review - and the possibility of denial. For institutions whose business depends on direct access to Fed payment rails, that changes the assumptions behind "what should be possible."
Why does a Fed master account matter
A master account is held at a Federal Reserve Bank. It gives an eligible institution a direct relationship with Fed payment services, rather than requiring it to route everything through another bank. For a bank handling customer deposits and payments, that can change how money moves, how many intermediaries are involved, and how much operational control the institution has.
Custodia pursued a master account to process payments directly instead of relying on third-party institutions. That's more than a technical preference. When a bank depends on another institution for essential payment functions, it also depends on that partner's risk policies, operational capacity, and willingness to stay involved. Over time, that dependency can affect service continuity and how confidently a bank can design products around predictable settlement.
Direct access versus correspondent banking
Without a master account, a bank can use a correspondent or partner institution to access payment networks. That can work - especially for a new, smaller institution still building out its operations. But it also adds another layer of dependency. The partner bank can set terms, limit services, or decide the relationship no longer fits its risk appetite.
For a crypto-focused bank, that problem can feel especially sharp. The bank may serve customers whose activity involves digital assets, while its payment partner may take a different view of crypto-related risk. If the partner tightens or changes those policies, the bank's access to ordinary payment services can become less reliable even if the bank itself remains licensed.
Still, direct access isn't automatically the best option for every institution. A master account comes with responsibilities and scrutiny. The institution has to manage liquidity, compliance, operational resilience, and risk controls at a level that supports its role in the payment system. Intermediation can add cost and dependency; direct access can improve control, but it also raises the bar for the bank running the account.
Why the distinction matters to customers
Most customers never see the plumbing. They notice deposits, withdrawals, and transfers - not the chain of institutions that carries the money. But that chain affects reliability. If a bank's access depends on a third party, decisions made by that third party can spill over into the customer experience even when customers have no direct relationship with the third party.
For digital-asset companies, that can complicate basic treasury work. Businesses still need conventional banking and payment rails for things like converting between dollars and digital assets, paying employees, and settling with customers. A crypto-facing business model doesn't remove the need for dependable fiat settlement.
So the practical question isn't "is direct access better?" It's whether the bank has a resilient, compliant way to move funds that fits what its customers need. Custodia argued that direct access was necessary to operate effectively. The appellate ruling, however, left approval with the Fed rather than treating access as an automatic consequence of state-level authorization.
How did Custodia's case reach the Supreme Court
Custodia is a Wyoming-chartered bank founded by Caitlin Long. It applied for a Federal Reserve master account in 2020. After waiting about two years for a decision, the bank sued the Federal Reserve in 2022. In January 2023, the Federal Reserve Bank of Kansas City rejected the application, citing concerns tied to Custodia's crypto-focused business model.
The case then moved through the federal courts. In October 2025, a federal appeals court ruled against Custodia, concluding that Federal Reserve banks didn't have to grant master accounts to every eligible institution. In March, the court declined to reconsider that decision, and Custodia asked the Supreme Court to hear the case. The Supreme Court declined, leaving the appeals court ruling in place.
The argument over state and federal authority
The case drew support from groups and lawmakers who were concerned about how far the Fed's discretion could go. The Blockchain Association argued that letting the Fed reject applications could weaken the authority of state banking regulators. Senator Cynthia Lummis and former Senator Patrick Toomey also filed a brief supporting Custodia's appeal.
At the heart of the dispute is a split of responsibilities. State regulators charter and supervise state banks. Federal Reserve banks control access to their own accounts and services. If the Fed can deny access even to a state-chartered institution that meets eligibility requirements, then state approval doesn't settle the question of how the institution participates in the national payment system.
That doesn't make the state charter meaningless - it just answers a different question. The charter determines whether the institution can operate as a bank under state law. The master account question is about direct access to Federal Reserve services. Custodia's case tried to narrow the gap between those two decisions, but the appeals court ruling left it open.
Why the risk rationale matters
When the Kansas City Fed rejected Custodia's application, it cited risks connected to Custodia's crypto-focused model. That matters because it places the dispute inside a broader supervisory concern: how to assess an institution whose activities may involve a fast-changing asset sector while still relying on the same core banking infrastructure as other banks.
The legal process didn't create a single universal "crypto risk" test, and the Supreme Court's refusal didn't endorse every reason given for Custodia's rejection. What the rulings establish is about the Fed's authority to reject an application - not a claim that every crypto-related business carries the same level of risk. Those distinctions will still shape how other applicants are evaluated, based on their own circumstances and controls.
What does the decision mean for crypto banks
The decision makes one point hard to miss for institutions planning around Fed access: don't build a business model on the assumption that a state charter guarantees a master account. Custodia's approach didn't produce that guarantee. If a bank wants direct access, it needs a plan for regulatory review, the chance of rejection, and what happens operationally if it has to use an intermediary instead.
That doesn't mean direct access is off the table. Other crypto-focused institutions are pursuing different paths. In March, Kraken Financial received approval from the Federal Reserve Bank of Kansas City for a restricted account. The account was approved for an initial one-year period and allows Kraken Financial to send and receive payments through the Fedwire system. It doesn't provide every service that comes with a full master account.
Restricted access is a different trade-off
Kraken Financial's restricted account is a reminder that "Fed access" isn't a single all-or-nothing label. A restricted account can provide access to certain payment functions while limiting the scope or duration of the arrangement. For some operations, that's enough. It's also not interchangeable with a full master account.
If an institution is weighing restricted access, the decision should start with a practical service map:
- Which payment flows does the bank need to control directly?
- Which functions can go through a partner without creating unacceptable dependency?
- What limits, review periods, or conditions come with restricted access?
- What happens to customers and counterparties if access is reduced or not renewed?
- Can the institution meet the compliance and operational obligations that come with broader access?
A restricted account can be a useful bridge - or it can be a stable fit - depending on what the bank actually needs. It may also leave key workflows dependent on other banks. The comparison isn't "restricted access versus no compromise." It's the cost, control, and resilience of each option.
Build a payment plan that survives a denial
For crypto banks and the companies that rely on them, payment access belongs in operational risk planning. That means identifying the critical dollar flows, mapping every intermediary, and documenting fallback arrangements before a disruption happens. If one partner handles all fiat settlement, that's a concentration risk whether the relationship feels stable today or not.
A good plan separates what the institution needs from what it would prefer. Direct Fed access may reduce certain dependencies, but it's not the only way to keep payments running. Using multiple banking relationships, communicating clearly with customers, and running tested switching procedures can reduce the impact if a provider changes its policies.
None of that guarantees access or eliminates regulatory risk. It does make the business less exposed to a decision it can't control. According to the source report, Custodia may still apply again for a master account or seek limited access under a separate proposal. For other institutions, the lesson is to pursue access while also building operations that can handle a different outcome.
Conclusion
Custodia's Supreme Court setback leaves the broader practical question open for future applicants: how much discretion should the Fed have when evaluating a bank that is eligible to apply for a master account? The immediate legal result is narrower. The appeals-court ruling stands, and a state charter doesn't automatically guarantee direct payment access.
For crypto banks, the reasonable response isn't to abandon the pursuit of Fed access, but also not to assume it will be granted. Look at both direct and restricted options, understand what correspondent banking dependencies mean in practice, and build a payment plan that can handle denial or changed terms. In this part of financial infrastructure, resilience depends less on chasing one preferred route and more on having a workable alternative.