Block's $764M DOJ Deal: Fintech's AML Wake-Up Call

Block agreed in principle to a $764M DOJ deferred prosecution for BSA violations — exposing the AML gaps common to fast-growing fintechs. What compliance teams must fix now.

Emily Carter
By Emily CarterAI Strategy Consultant at Joinble
·12 min read
Share
Block's $764M DOJ Deal: Fintech's AML Wake-Up Call
imageUse this imagedownloadDownload

In October 2026, Block — parent of Cash App and Square — disclosed that it had agreed in principle to a deferred prosecution agreement with the US Department of Justice. The charge: failure to maintain an effective anti-money laundering programme under the Bank Secrecy Act. The price: approximately $764 million. The deal is not yet final, pending court approval and a text acceptable to all parties, but the terms are clear enough to treat as settled for compliance purposes.

This is not the first enforcement action Block has faced. The arc stretches back two years and encompasses multiple regulators, multiple states, and multiple failures that accumulated in the same underlying programme. Understanding that arc is more instructive than the headline number.

The Enforcement Timeline

Block's AML exposure did not arrive in a single examination. It was built, layer by layer, through a series of regulatory findings that each identified the same structural problem: a compliance programme that had not scaled with the business.

Date Action Regulator Amount
April 2025 Consent order and civil penalty NYDFS $40M
July 2026 Multistate attorney general settlement 46 US state AGs $45M
October 2026 Preliminary DPA (BSA/AML programme failure) DOJ ~$764M
March 2026 Investigation closed without enforcement SEC —

The NYDFS action was the most granular. New York regulators documented four specific failures: weak transaction monitoring, an unresolved backlog of alerts, inadequate KYC practices particularly for Bitcoin transactions, and the absence of any formal process for refreshing customer KYC information. That last point is worth pausing on — not a failure of initial onboarding, but a failure of the ongoing monitoring obligation that the BSA imposes after onboarding is complete.

The DOJ's deferred prosecution agreement follows from the same underlying programme, escalated to the federal level and carrying criminal exposure that the civil penalties did not.

What the BSA's AML Programme Requirement Actually Demands

The Bank Secrecy Act requires covered financial institutions — which includes money services businesses such as Cash App — to maintain an anti-money laundering programme with four minimum components: internal policies and procedures, a designated compliance officer, ongoing employee training, and independent testing. Each component is well-established. What regulators tested in the Block case was whether the programme was operative at scale, not whether it existed on paper.

The distinction matters. Block's programme existed. Cash App onboarded hundreds of millions of accounts between 2013 and 2026. The company published terms of service, trained staff, and produced compliance documentation. What it did not do — at sufficient scale and with sufficient operational rigour — was maintain the monitoring functions that allow a programme to detect and report suspicious activity in real time, as a live book of accounts changes rather than as a static documentation exercise.

The specific documentation failures NYDFS found illustrate the gap:

  • Alert backlog: Suspicious activity alerts generated by the transaction monitoring system were not being reviewed and resolved at a pace that matched alert generation. The queue grew. Unreviewed alerts represent a window of undetected exposure.
  • KYC refresh absence: No formal process existed for systematically refreshing customer risk profiles as customer behaviour evolved. This is what the perpetual KYC framework addresses — the obligation does not end at account opening.
  • Bitcoin KYC gaps: The programme applied weaker KYC logic to cryptocurrency transactions than to fiat transfers, despite the BSA's requirements applying equally. Regulators have consistently found this gap across fintech and crypto businesses.

The Fintech Scaling Problem

Block is not unique in this failure mode. It is the most prominent recent example of a pattern that has appeared in enforcement actions across the fintech sector for the past five years.

Fintech businesses grow through frictionless onboarding. The user acquisition model — fast signup, minimal documentation, instant access — is structurally in tension with BSA compliance, which requires documented identification, risk scoring, and ongoing monitoring before a customer account reaches full transaction capability.

Fast growth compounds this tension. A compliance programme sized for two million accounts may be formally adequate when it is built. When the same programme, with incremental scaling, is asked to cover sixty million accounts, it may be nominally present but operationally insufficient. Alert volumes that a team of fifty analysts can review become unmanageable at six times the account count without a commensurate increase in monitoring capacity — human or automated.

The Block enforcement record shows this clearly. The company is not accused of deliberately facilitating money laundering. The charge is that it failed to maintain a programme adequate to detect and report it — a failure of architecture rather than intent. Under the BSA willfulness standard, that distinction matters legally but does not reduce the enforcement consequence.

Bank of America's $1.2 billion FinCEN penalty in October 2026 rested on the same conceptual foundation: a programme that existed but that did not produce the outputs the BSA requires at operational scale. The American Express $350 million OCC action one week earlier documented a comparable gap at an institution with a very different business model. The enforcement pattern is not sector-specific. It is a function of monitoring programmes that have not kept pace with the transaction books they are supposed to cover.

The Alert Backlog Problem Is an Architecture Problem

The NYDFS finding that Block maintained an unresolved alert backlog is technically understandable and operationally indefensible.

Transaction monitoring systems generate alerts based on rule triggers — unusual transaction volumes, geographic anomalies, velocity spikes, structuring patterns. Rule-based systems applied to a rapidly growing account base generate alerts at a volume proportional to the account count. Analyst teams do not scale at the same rate. The result, without architectural intervention, is a backlog that grows faster than it is resolved.

An unreviewed alert is not the same as a reviewed alert that found no suspicious activity. It is a gap in coverage. When a SAR-eligible transaction is captured in an alert that is never reviewed, the SAR is never filed, the reporting obligation is not met, and the regulator's ability to identify patterns across the financial system is compromised. This is what BSA reporting requirements protect against, and it is precisely the failure the NYDFS found.

The architectural response to alert backlog is not more analysts. It is a monitoring layer that resolves a higher proportion of alerts before human review — through automated investigation, contextual risk scoring, and disposition logic that reduces the volume requiring manual triage. This is what AI agents in bank compliance are designed to address. Joinble's autonomous compliance agents operate on this architecture: continuous transaction monitoring with automated alert triage, so that the unreviewed queue approaches zero rather than accumulating at scale.

The KYC Refresh Gap Is a Risk Management Gap

The absence of a KYC refresh process is a subtler failure than alert backlog, and in some ways a more systemic one.

A customer's risk profile at account opening reflects the information available at that moment: identity documents, declared occupation, expected transaction behaviour, and the transaction patterns of the first few months. That profile is accurate when it is created. It becomes less accurate — and less defensible — as the account ages and customer behaviour evolves.

A customer whose initial profile was low-risk may, over time, begin transacting in ways that the original profile would not have predicted: higher volumes, new counterparty types, different geographic footprint. Without a programme that systematically reviews and updates risk profiles, the original low-risk classification persists while actual risk has changed. The compliance programme is monitoring against an outdated model.

The KYC guide for 2026 covers the ongoing monitoring obligation in detail. The regulatory baseline is not ambiguous: customer due diligence includes periodic review and risk rescoring, with frequency calibrated to the customer's risk tier. What the NYDFS found at Block was not that the company had a bad policy on this point — it was that no formal policy existed.

Five Questions for Fintech Compliance Programmes

The Block enforcement arc maps to five questions that any fintech compliance function should be able to answer with documentation:

1. What is your unresolved alert age distribution? The question is not how many open alerts you have. It is how old the oldest ones are, and what threshold triggers escalation or escalated SLA management.

2. When was your last KYC refresh cycle completed, and at what coverage rate? For a programme operating at scale, 100% refresh at scheduled intervals is a documentation requirement, not a goal. What percentage of your highest-risk tier has been reviewed in the last 12 months?

3. Does your monitoring logic apply equally to fiat and crypto transaction flows? The BSA does not distinguish. If your cryptocurrency monitoring uses lighter rule sets than your fiat monitoring, that gap is visible to regulators.

4. How does your alert volume change as your account base grows? If the relationship is roughly proportional and your analyst capacity has not grown at the same rate, you have a structural alert backlog forming, even if today's queue looks manageable.

5. What was your SAR filing rate in the last four quarters, and does it reflect your actual risk population? A declining SAR rate at a growing fintech is not a sign of improving compliance. It is a leading indicator of degraded detection.

What the DPA Means for the Sector

A deferred prosecution agreement is not a conviction. If Block meets its obligations over the three-year deferral period — including completing a monitored remediation programme and cooperating with the DOJ — the charge is dismissed. The company retains its operating licences.

What the DPA does impose is a formal compliance monitor, documented remediation milestones, and the sustained involvement of the DOJ in the company's compliance programme for three years. For a business the size of Block, that operational constraint is significant in ways the financial penalty is not.

For the fintech sector, the significance is different. A $764 million enforcement action against one of the most prominent payment fintechs in the United States makes concrete, with a specific dollar figure, the cost of allowing a compliance programme to lag a growing account base. The number will appear in every fintech board meeting that discusses compliance investment in 2027 and beyond.

The case for investing in automated monitoring infrastructure is no longer theoretical. It is documented in federal enforcement with a nine-figure price tag.

FAQ

What is a deferred prosecution agreement? A DPA is an agreement between a prosecutor and a defendant in which the government files a charge but agrees to defer its prosecution — typically for two to three years — provided the defendant meets specified conditions such as paying penalties, cooperating with investigators, and completing a compliance remediation programme. If the conditions are met, the charge is dismissed. It is distinct from a plea agreement in that no conviction is entered if the DPA terms are satisfied.

What does the Bank Secrecy Act require of fintech companies? The BSA applies to money services businesses, which includes mobile payment platforms such as Cash App. Required elements include: a written AML programme with internal controls; a designated compliance officer; ongoing employee training; independent testing; and a customer identification programme. The SAR filing obligation applies when the company detects a transaction of $5,000 or more that it knows, suspects, or has reason to suspect involves illicit activity.

Why was Cash App's KYC approach a specific problem? NYDFS found that Cash App applied weaker KYC logic to Bitcoin transactions than to fiat payments, despite the same legal obligations applying to both. Additionally, the absence of a formal KYC refresh process meant that customer risk profiles were not updated as customer behaviour evolved — a direct violation of the ongoing monitoring component of the BSA's customer due diligence requirement.

Can AI tools solve alert backlog problems? Automated triage and AI-assisted investigation can materially reduce the volume of alerts requiring manual review by resolving lower-risk alerts through contextual scoring before human analysts see them. This addresses the structural alert backlog problem — not by replacing analysts but by ensuring they spend time on confirmed anomalies rather than routine queue triage. The FINRA guidance on AI in compliance programmes, published in 2026, provides the regulatory framework for deploying these tools in a BSA-compliant manner.

What is the difference between a willful and a non-willful BSA violation? Under US law, a willful BSA violation does not require proof that the institution intended to facilitate money laundering. It requires demonstrating that the institution was aware of its BSA obligations, was aware of a compliance gap, and failed to act to close it. Prior regulatory findings — such as a consent order or MRA — establish the awareness prong. Continuing to operate with documented gaps after a formal regulatory finding is precisely the fact pattern that produces a willfulness finding.

How should growing fintechs prevent the Block outcome? The practical measures are: scale monitoring capacity in proportion to account growth rather than on a lag; implement formal KYC refresh cycles with documented coverage metrics; ensure monitoring logic applies equally to crypto and fiat flows; set SLA controls on alert age so queues cannot grow unreviewed; and conduct independent programme testing at minimum annually. Automated monitoring infrastructure becomes economically necessary at scale — human-only review cannot keep pace with large account bases growing at fintech rates.

Emily CarterEmily Carter
Share

Related Articles

Digital Hawala: The Fintech Threat KYC Must Catch Now
Compliance21 Sep, 2026

Digital Hawala: The Fintech Threat KYC Must Catch Now

FATF's new report names hawala and underground banking as top ML channels in 80% of jurisdictions. Here is what KYC teams in fintech must catch.

iGaming KYC Under AMLR: The 2027 Compliance Wake-Up
Compliance07 Sep, 2026

iGaming KYC Under AMLR: The 2027 Compliance Wake-Up

The EU AMLR's €2,000 gambling threshold takes effect July 2027. Deepfake attacks in iGaming surged 700% in 2026. Here's what operators must do now.

Ikano Bank's AML Fine: The EDD Failures KYC Teams Must Fix
Compliance29 Jun, 2026

Ikano Bank's AML Fine: The EDD Failures KYC Teams Must Fix

Sweden's Finansinspektionen fined Ikano Bank SEK 140M in June 2026. These three EDD failures are what regulators are now targeting across the EU.