Square Accused of FREEZING Customers’ Money

web browser showing the Federal Trade Commission website header
Photo: Jarretera / Shutterstock

In digital payments, the real test is not whether a platform can detect fraud fast, but whether it can separate true risk from ordinary commerce while giving legitimate customers clear paths to get their money back—an operational problem the FTC’s probe of Block has now placed under a microscope.

The Short Version

  • The FTC opened a formal investigation into Block (parent of Square and Cash App) after more than 1,500 consumer complaints about frozen or deactivated accounts.
  • Agency filings reportedly describe customers unable to access or transfer funds following freezes, with allegations totaling up to $2.5 million since 2022.
  • The inquiry is proceeding through a Civil Investigative Demand and a federal court enforcement action—this is a compulsory process, not just letter-writing.
  • Block says it is cooperating in good faith; Square’s terms do permit temporary holds and freezes to manage risk and compliance.

What the FTC is actually investigating

According to multiple reports, the Federal Trade Commission initiated its probe after receiving more than 1,500 consumer complaints alleging they were locked out of Square or Cash App accounts and could not get timely help to recover legitimate funds. The agency formalized its inquiry with a Civil Investigative Demand (CID) issued January 22, 2026, and, when disputes over production followed, sought judicial enforcement in the Northern District of California, docketed as FTC v. Block, 4:26-mc-80299. The reported petition focuses on whether customers—some of whom had completed identity and bank verification—were left unable to access or transfer their balances after account deactivation or freezes, with aggregate inaccessible funds alleged to reach up to $2.5 million since 2022.

Compulsory process matters. A CID is not a press release; it is a legally enforceable demand for documents and testimony. The categories reportedly sought—organizational charts, personnel directories, consumer complaints, relevant policies and procedures, and the identities of employees with first-hand knowledge—are aligned with a classic unfair or deceptive acts and practices (UDAP) investigation. That scope signals the FTC is not only interested in incident counts, but in whether internal controls, staffing, and escalation playbooks kept pace with growth and changing risk.

What freezes are for—and where they fail in practice

Account freezes are not exotic; they are a baseline tool to contain fraud, money laundering alerts, sanctions red flags, chargebacks, and unauthorized transfers. Square’s own agreements reserve broad discretion to freeze, limit, or hold funds—including up to 180 days during an investigation and to protect security interests and setoff rights—subject to applicable law. In other words, the mere existence of a hold is not evidence of wrongdoing by the platform. The question, always, is proportionality and process: were the triggers well-founded, were notices intelligible, did verifications unlock accounts when criteria were met, and did customers have a functional appeal path?

Across the payments sector, that is where frictions accumulate. Consumer finance regulators have consistently flagged delayed transfers, account holds or closures, and opaque explanations as common sources of harm, particularly when communication breaks down and customers cannot predict when funds will be released or how to escalate a dispute. That pattern forms the backdrop for the FTC’s interest in staffing levels, complaint-handling, and the effectiveness of remediation when the system gets a case wrong.

Block’s response and the limits of what is known today

Block has publicly said it is working in good faith with FTC staff, responding on an accelerated timeline, and addressing a handful of remaining requests; that posture does not resolve the merits, but it does undercut any claim that the company is stonewalling. The reports, to date, establish an investigation and summarize allegations—not an adjudicated violation. There is no public record yet of a final FTC complaint or order in this matter, and the $2.5 million figure is presented as an allegation from the petition rather than a validated ledger of individual customer accounts. Those constraints are typical early in a regulatory case, especially where consumer data and risk models are confidential.

Still, the FTC’s move to court to enforce a CID is not routine puffery; it is a sign the agency considers the requested materials central to evaluating whether customer assistance and internal controls matched the platform’s obligations as it scaled. If the docket proceeds, unsealed filings—CID exhibits, staff declarations, internal policy histories—will either shore up the allegations or narrow them to particular practices and periods.

Mechanics: how risk controls intersect with customer access

Risk programs in real-time payments rely on layered defenses: behavioral scoring of transactions, device and identity verification, sanctions screening, chargeback and dispute monitoring, and manual review for anomalies. Each layer can trigger a hold. Sensible design requires two guardrails. First, escalation logic must match the risk—swift for true anomalies, but just as swift in reversing course when evidence clears the customer. Second, customer communications must map to the decision tree: what happened, what is needed from the user, what timelines apply, and precisely how to appeal.

This is where staffing and tooling matter. A platform that thins out its support and escalation teams without reengineering the workflow will see queues grow, clock-based holds default to their maximums, and “your account is under review” become a dead end rather than a bridge to resolution. The FTC’s document asks—org charts, complaint files, policies, and named custodians—are designed to test whether that degradation occurred and whether it was foreseeable as volumes and fraud patterns shifted.

Where the genuine disagreement lies

There is no serious dispute that platforms can and sometimes must freeze accounts; the disagreement is whether Block’s freezes were proportionate, well-explained, and promptly reversible once customers satisfied verification. On one side, the FTC frames a pattern of inadequate assistance affecting a large volume of users, some verified, with nontrivial sums effectively trapped for periods long enough to trigger complaints. On the other, Block cites contractual authority to impose holds and describes cooperative engagement with regulators. Those terms do give the company tools to manage risk; they do not immunize poor execution if customers were left in limbo without a workable remedy.

History in adjacent cases offers a clue. Payment and wallet providers that scaled quickly have, at times, paid to resolve disputes over sustained holds and confusing remediation pathways, even while retaining the right to freeze in legitimate risk scenarios. Meanwhile, consumer complaint data show that when explanations are thin and timelines uncertain, customers perceive the platform—not an unseen fraudster—as the actor depriving them of funds, which magnifies reputational and regulatory exposure.

What this means for consumers, merchants, and platforms

For consumers and small merchants, three practices improve outcomes regardless of platform: maintain linked external accounts with tested transfer paths; complete identity and bank verification early; and keep written records of notices, ticket numbers, and support interactions. If a freeze extends beyond the platform’s stated review window without clarity, escalate in writing and, where appropriate, to regulators who can compel an audit trail.

For platforms, the lesson is operational discipline. Build release criteria that are as explicit as your freeze criteria; instrument “unlock” workflows to measure time-to-resolution; and staff for peaks, not averages, so investigations don’t age out to 30-, 90-, or 180-day defaults. Calibrate notices so they say what triggered the hold, what evidence will clear it, and who owns the case. Those are not niceties—they are the difference between a defensible compliance hold and an unfair practice claim when regulators audit outcomes at scale.

How to read the next filings

If the court enforces the CID, look for three kinds of documents. First, internal policy change logs and staffing plans that show whether support and risk teams were reduced during periods of rising complaints. Second, redacted case samples tracing the lifecycle from freeze to resolution, including when verified users remained locked out and why. Third, management and investor decks that may reveal how leadership measured complaint backlogs, time-to-unlock, and the trade-offs chosen between fraud loss and customer harm. Together, those records will determine whether this was a narrow operations lapse or a systemic failure to provide workable relief at scale.

Sources:

reclaimthenet.org, bloomberg.com, diariobitcoin.com, ground.news, digitaltransactions.net, tradingview.com, seekingalpha.com, tokenpost.com, squareup.com, law360.com, files.consumerfinance.gov