FinCEN Lets Banks Trade Fraud Data Before Cash Vanishes

FinCEN fraud data sharing just moved from a legal hesitation point to an explicit permission slip: banks may exchange suspected fraud information in real time under Section 314(b), even before they identify laundered fraud proceeds.

That is the core shift in updated Financial Crimes Enforcement Network guidance, according to American Banker. The clarification matters because scam money often crosses institutions quickly, while each bank may see only one slice of the activity.

Treasury framed the update as part of a broader anti-fraud push. In its June 12, 2026 release, Treasury Secretary Scott Bessent said:

“Americans lose hundreds of billions of dollars to fraud each year. At Treasury, we follow the money, and we know financial institutions are often the first to see suspicious activity in real time.”

Why FinCEN’s real-time fraud data guidance could change a scam response

The reader-facing problem is simple: a victim’s bank may spot suspicious behavior, but the receiving bank may hold the next clue. If the two institutions don’t compare notes fast enough, the pattern can stay fragmented.

FinCEN’s updated fact sheet says suspected fraud can fall within the 314(b) safe harbor, which allows eligible financial institutions to share information for detecting and reporting money laundering, terrorist financing and related criminal activity. The key clarification is that a bank does not first need to identify specific fraud proceeds being laundered. Suspicion that the activity involves fraud can be enough under FinCEN’s reading.

That does not make the guidance a new fraud surveillance law. It is FinCEN’s interpretation of existing authority. That distinction is the legal pressure point.

The stakes are large enough to explain why Treasury moved. The Federal Trade Commission told a congressional committee in March that consumers reported $15.9 billion in fraud losses last year across 3 million reports, up from about $12 billion in 2024. The FTC also estimated that, including unreported losses, the real cost of fraud in 2024 could have reached $195.9 billion.

What banks can share under the Section 314(b) safe harbor

Section 314(b) is a legal shield for certain financial institutions that voluntarily share information with one another to identify and report illicit finance. FinCEN’s update makes explicit that suspected fraud can be part of that protected sharing when it is tied to the covered activity.

The fact sheet “expands upon and replaces” FinCEN’s December 2020 version. It adds fraud to the category of “specified unlawful activities” that can underlie money-laundering charges.

FinCEN says institutions may share several kinds of fraud-linked information, including:

• Transaction records: Data that helps connect activity across institutions.
• Video surveillance footage: Physical evidence tied to suspected activity.
• Cyber data: IP addresses, device geographic location and device identification numbers.
• Behavioral red flags: Patterns such as a customer adding a new payee and soon initiating a large transfer.
• Linked-account indicators: Multiple accounts sharing identifying details.
• Login anomalies: Access to the same account from geographically distant places.

For readers following how security signals get converted into action, this sits adjacent to the operational questions we covered in SIEM vs XDR vs SOAR Exposes Your Real Security Gap and SIEM Data Lake Architecture Breaks the SIEM Cost Trap. FinCEN’s guidance is narrower: it says which fraud-related signals eligible institutions may exchange under 314(b), not how banks should build their internal detection stack.

How real-time bank-to-bank sharing works when a payment looks suspicious

A practical 314(b) loop starts when one participating institution spots a suspicious signal. Under the updated guidance, it can contact another eligible participating institution and share relevant fraud indicators, if the sharing fits the safe harbor.

That second institution may then compare the information against its own records. The point is to turn isolated fragments into a fuller picture of whether the activity involves fraud, money laundering or another covered crime.

Speed matters because the source material identifies a common gap: a mule account at one bank can be tied to victims at another. Real-time sharing is meant to close that gap by helping institutions connect suspicious activity while it is still unfolding.

FinCEN’s clarification may also improve the factual base for later suspicious activity reporting. A bank that receives relevant information from another institution can see more than its own internal slice. Still, the guidance does not promise that funds will be recovered, transfers reversed or accounts frozen.

What changes when a new payee is followed by a large transfer?

FinCEN’s own red-flag example is concrete: a customer adds a new payee, then soon initiates a large transfer to that payee. On its own, one bank may see only an unusual transaction. Another bank may see related account activity, shared identifying details or login behavior from far-apart places.

Under the updated guidance, the first bank has clearer permission to share relevant indicators with the second bank if both are eligible participants and the sharing fits 314(b). That can help the institutions determine whether the activity is part of a broader fraud pattern.

This is where FinCEN fraud data sharing becomes operationally meaningful. The value is not a single magic data point. It is the combination of payment behavior, account links, cyber data and timing.

The FTC data explains why Treasury cares about bank payments specifically. American Banker reported that consumers’ largest reported losses last year came not from cryptocurrency but from money sent to scammers through bank payments.

Privacy and liability still constrain fraud data sharing

Banks are not getting a blank check to trade customer information. The safe harbor has boundaries.

FinCEN says any institution that wants to share or receive information under Section 314(b) must register with the agency. The information received under this sharing regime can be used only to fight money laundering, including the underlying fraud, not for unrelated purposes.

Two restrictions stand out:

• No SAR sharing: A bank cannot share a suspicious activity report or disclose that one exists.
• No general-purpose data pooling: The information must be tied to identifying and reporting covered suspicious activity.

There is also litigation risk. Daniel Stipano, a partner at Davis Polk & Wardwell and former longtime Office of the Comptroller of the Currency official, told American Banker:

“The safe harbor has never been tested judicially, so it is not clear whether a court would agree with Fincen's interpretation.”

That warning matters. FinCEN can say its interpretation protects banks, but a customer can still sue if they believe personal information was wrongfully disclosed. Regulators can also examine whether the sharing followed the rules.

Why banks want Congress to lock the protection into law

The Bank Policy Institute, which represents large, regional and foreign banks, welcomed the update. It called the guidance “a critical step in helping banks to disrupt fraud and scams in real-time” and pressed Congress and other agencies to “remove legal uncertainty” and “establish clear safe harbor protection for banks.”

That request goes to the weakness in the current setup. Guidance is not the same as statutory text. A later administration could revise FinCEN’s interpretation. A court could also disagree with it.

Himamauli Das, former acting director of FinCEN and now at K2 Integrity, said the fact sheet gives banks much of the clarity they have been seeking because it “unambiguously states that fraud is covered by the 314(b) safe harbor and provides legal reasoning to justify its conclusion.” But he also noted that guidance does not bind the way a law or regulation does.

For banks, the practical question is participation. The more institutions that register and use the 314(b) framework carefully, the more useful FinCEN fraud data sharing becomes. But if legal teams remain worried about privacy suits or judicial uncertainty, some banks may still move cautiously.

The next thing to watch is whether Congress turns FinCEN’s interpretation into explicit statutory protection. Until then, the guidance gives banks a stronger basis to share fraud signals now, but not the final word on how courts will treat that sharing later.

Disclaimer: This XOOMAR analysis is for informational and educational purposes only. It is not financial, investment, legal, tax, or professional advice. It does not provide buy, sell, hold, price-target, portfolio, or personalized recommendations. Verify information independently and consult qualified professionals before making decisions.

Impact Analysis

• Real-time sharing could help banks connect scam activity that moves quickly across institutions.
• The guidance reduces legal uncertainty for banks that want to compare suspected fraud signals.
• It strengthens Treasury’s anti-fraud push without creating a new fraud surveillance law.