ICBA Pushes Kansas City Fed to Tighten Kraken's Account or Let It Expire

Kraken described the March approval as a milestone that could provide direct payment infrastructure and improve Fedwire settlement. The June 18 letter tests that model from the other direction. A one-year, Fedwire-only account can be described as a controlled exception. It can also be described as the first step toward broader access. ICBA wants the Kansas City Fed to treat the first description as binding and the second as a risk to be contained.

ICBA draws its urgency from ICIJ reporting that major crypto firms supplied bitcoin liquidity to crypto ATM operators while authorities were scrutinizing scam risks. ICIJ reported that Kraken transferred at least $1.1 billion worth of Bitcoin to crypto ATM operators in recent years, including more than $700 million to Coinhub and at least $245 million to Byte Federal. Kraken told ICIJ it maintains robust compliance controls.

Those figures should be read as transaction-tracing claims, not adjudicated findings. They still give ICBA a way to connect the Kraken Fed account debate to crypto ATM fraud risk. Federal and state records make the kiosk concern easier to understand. The FBI's 2025 IC3 report showed 13,460 cryptocurrency ATM and kiosk complaints with about $389 million in losses, up 23% in complaints and 58% in losses from 2024. Victims age 60 and older accounted for roughly $257.5 million of those losses. FinCEN's August 2025 notice linked kiosks to fraud, cybercrime, drug trafficking, and non-compliant operators.

State-level actions reinforce the pattern. The D.C. attorney general alleged that 93% of Athena Bitcoin ATM deposits in the District during the relevant period were scam-related. Missouri issued civil investigative demands to kiosk operators including Athena and Byte Federal. California said Coinhub must pay $675,000, including $105,000 in restitution, after kiosk-law violations.

Those actions address the kiosk ecosystem, not Kraken Financial's account compliance. They still explain why ICBA is treating kiosk liquidity as a Fed-rails issue. If the Kansas City Fed views crypto liquidity relationships as relevant to account-access risk, the first-year review becomes a test of whether disclosed guardrails can absorb new fraud-risk evidence after approval.

The timing also helps ICBA. On May 20, the Fed Board requested comment on a payment-account proposal for legally eligible institutions that are not federally insured. The proposal would preserve eligibility rules while adding standard terms, including no intraday credit, no discount-window access, no interest on balances, overdraft controls, and illicit-finance risk mitigation. It also encouraged Reserve Banks to temporarily pause Tier 3 access decisions while policy work continues.

Governor Michael Barr dissented from that proposal, saying the safeguards were insufficiently specific against money-laundering and terrorist-financing risks at institutions the Fed does not supervise. He cited the absence of Fed examination provisions for AML and Bank Secrecy Act procedures. That dissent gives the ICBA letter a regulatory echo inside the Fed's own policy process.

No public source shows the Kansas City Fed has opened a termination process or found Kraken Financial out of compliance. The public record shows a pressure campaign, a limited account, an active Fed policy debate, and a set of fraud-risk allegations around the crypto ATM ecosystem.

The next concrete signal is whether the Kansas City Fed responds publicly, asks Kraken Financial for additional information, changes the account limits, or lets the one-year term proceed toward renewal under the existing guardrails. The June 18 letter changes the story from an access milestone into a live supervisory test.