Kansas City Fed grants Kraken Financial a one-year limited-purpose account

The Federal Reserve Bank of Kansas City on March 4, 2026 approved a limited-purpose account for Payward Financial, doing business as Kraken Financial, placing a crypto-focused Wyoming bank directly inside a part of the Federal Reserve account system. The approval ran for an initial one-year term and carried undisclosed restrictions tailored to the institution’s business model and risk profile.

That narrow wording matters. Kraken called the authorization a Federal Reserve “master account” and said it could settle directly through Fedwire. The Kansas City Fed itself described a “limited purpose account” and declined to disclose which Federal Reserve services were available. The verified development was therefore direct, conditional account access—not an unrestricted banking franchise or a general approval of Kraken’s exchange business.

Why the account mattered

Crypto trading venues normally depend on commercial-bank partners to move dollars between customers, exchanges and the banking system. Kraken said its banking subsidiary could use the new connection to reduce reliance on correspondent banks, initially for institutional client activity, with a phased rollout. It also said the bank operated under Wyoming’s Special Purpose Depository Institution charter and maintained liquid assets equal to or greater than client fiat deposits.

Those operational claims came from Kraken and were not independently quantified on March 4. Neither Kraken nor the Kansas City Fed published transaction volumes, expected settlement-time improvements, cost savings or a launch schedule beyond the phased approach. The announcement therefore supported an infrastructure story, not a measurable conclusion about revenue, liquidity or customer outcomes.

The institutional significance was clearer. The Kansas City Fed classified Kraken Financial as a Tier 3 applicant under the Federal Reserve Board’s Account Access Guidelines. That category covers legally eligible institutions outside the first two tiers and generally receives the strictest review. The Reserve Bank said each access decision depended on the applicant’s particular facts and a risk-based assessment; it did not announce a blanket path for other crypto companies.

A live policy dispute

The approval arrived while the Federal Reserve Board was considering a separate payment-account prototype. The Board had requested public input on December 19, 2025, and the comment period had closed on February 6, 2026. A contemporaneous Sullivan & Cromwell analysis noted that the proposed prototype contemplated payment-focused accounts with standard limitations, but the Kansas City Fed did not say whether Kraken’s account matched that model.

Banking groups immediately challenged the process. The Bank Policy Institute said on March 4 that approving Kraken before the Board finalized a framework raised consistency, transparency and anti-money-laundering concerns. That was an advocacy position from an organization representing large banks, not a finding that Kraken had violated a rule or that the Reserve Bank’s safeguards were inadequate. The Kansas City Fed said the account contained risk-based limits but kept their details confidential.

What the record did not establish

As of March 4, 2026, the public record did not identify every permitted service, disclose the restrictions, establish access to the discount window, or show production payment data. It also did not grant federal deposit insurance or convert the state-chartered SPDI into a conventional federally supervised bank. Describing the account as “limited purpose” preserves the central bank’s own formulation.

The lasting question on the event date was whether this one-year authorization would remain an isolated, closely controlled case or become a workable route for other digital-asset institutions. Answering that required later Federal Reserve policy, implementation data and renewal decisions; none should be assumed from the March 4 approval alone.