Predicate crimes sit at the foundation of every money laundering prosecution worldwide. Before a financial institution, merchant, or individual can be charged with laundering, regulators and prosecutors must first establish that an underlying criminal act generated the proceeds in question. Without this upstream offense, there is no dirty money to clean — and no laundering charge to bring.
For payment businesses, understanding predicate crimes is not an academic exercise. The proceeds of drug trafficking, fraud, human trafficking, and dozens of other offenses flow through payment rails every day. Merchants and platforms that fail to recognize the typologies associated with these crimes risk becoming unwitting conduits — and facing the regulatory consequences that follow.
How Predicate Crimes Works
The lifecycle of a predicate crime runs from the original illegal act through to the integration of clean funds into the legitimate economy. Each stage creates distinct signals that a well-calibrated compliance program should be able to detect. Understanding this chain helps merchants and developers know exactly where their systems must intervene.
Commission of the Underlying Offense
A criminal commits a designated illegal act — drug trafficking, fraud, bribery, cybercrime, human trafficking, or any of the other offenses recognized under the applicable jurisdiction's AML statute. This act generates proceeds that are inherently illicit. The crime itself may occur entirely outside the payment system, but the money it produces will eventually need to move.
Proceeds Enter the Financial System
The criminal attempts to place the illicit proceeds into the financial system, often through cash-intensive businesses, peer-to-peer transfers, cryptocurrency on-ramps, or merchant accounts. This placement stage is where payment platforms have the greatest exposure — and the greatest opportunity to detect suspicious activity before funds are layered further.
Layering Through Transactions
Once inside the financial system, the proceeds are moved across multiple accounts, jurisdictions, or instruments to obscure their origin. This may involve refund manipulation, fictitious invoicing, split transactions designed to stay below reporting thresholds (structuring), or round-tripping funds through related entities. Each hop makes the predicate crime harder to trace.
Integration as Legitimate Revenue
At the final stage, the now-layered funds are integrated into the legitimate economy — appearing as business income, investment returns, or asset purchases. Once integrated, tracing proceeds back to the predicate crime requires forensic financial investigation. Payment platforms that failed to act during placement or layering have already missed the critical intervention window.
Regulatory Reporting Obligation Triggered
At any stage where a payment platform identifies a transaction that may involve predicate crime proceeds, it is legally obligated to file a Suspicious Activity Report (SAR) with the relevant financial intelligence unit — FinCEN in the United States, the NCA in the United Kingdom, or the equivalent authority in the applicable jurisdiction. Failure to file can itself constitute a criminal offense.
Why Predicate Crimes Matters
The scale of predicate crime proceeds flowing through global payment systems is substantial, and regulators have made clear that compliance gaps carry serious consequences. For payment businesses, the business case for robust predicate crime awareness is both legal and financial.
The United Nations Office on Drugs and Crime (UNODC) estimates that between $800 billion and $2 trillion in illicit proceeds are laundered globally each year — representing 2–5% of global GDP. Not all of this flows through formal payment networks, but a significant portion does, particularly as criminals exploit the speed and anonymity afforded by digital payments. A 2023 report from the Egmont Group found that financial intelligence units globally received over 3.1 million suspicious activity reports in a single year, many tied to fraud, drug trafficking, and cybercrime proceeds — three of the most common predicate categories for payment-sector exposure.
The Financial Action Task Force (FATF), which sets the global standard for anti-money laundering (AML) compliance, has increasingly focused its mutual evaluations on whether countries and their financial sectors are effectively detecting predicate crime proceeds — not just filing reports. Jurisdictions that underperform face grey-listing, which triggers correspondent banking restrictions and reputational damage that cascades to every business operating in that market.
Regulatory Exposure Is Not Hypothetical
In 2022 and 2023 alone, global AML enforcement actions against payment companies and banks totalled over $5 billion in fines. The majority cited failures to detect predicate crime typologies — particularly fraud, drug proceeds, and human trafficking — within transaction monitoring systems.
Predicate Crimes vs. Money Laundering
These two terms are often conflated, but they describe legally distinct concepts with different implications for compliance programs. Understanding the boundary between them helps merchants and developers design more targeted controls.
| Dimension | Predicate Crime | Money Laundering |
|---|---|---|
| Definition | The original illegal act generating illicit proceeds | The act of concealing, layering, or integrating those proceeds |
| Legal relationship | Must be established first for a laundering charge | Cannot exist without a predicate crime |
| Examples | Drug trafficking, fraud, bribery, cybercrime | Shell company layering, structuring, trade-based laundering |
| Criminal charge | Separate offense (e.g., wire fraud, trafficking) | Standalone AML violation with its own penalties |
| FATF coverage | 21 designated categories | Criminalized across all 200+ FATF member jurisdictions |
| Reporting trigger | Indirectly — behavioral patterns signal proceeds | Directly triggers SAR filing obligations |
| Merchant exposure | Processing proceeds unknowingly | Knowingly facilitating layering or integration |
| Detection tool | Typology-based transaction monitoring | Threshold alerts, velocity rules, network analysis |
The practical takeaway: a fraud ring hitting your platform is a predicate crime event. The refund cycling those fraudsters use to clean their proceeds is the laundering layer. Both expose you, but they require different detection logic.
Types of Predicate Crimes
The FATF Forty Recommendations designate 21 categories of predicate offenses that all member countries must criminalize. Payment businesses encounter certain categories far more frequently than others, and transaction monitoring rules should be weighted accordingly.
High-frequency in payments:
- Fraud and financial crime — card fraud, identity theft, advance fee schemes, refund abuse, and account takeover all generate proceeds that flow directly through payment rails. This is the predicate category most commonly encountered by ecommerce merchants.
- Drug trafficking — proceeds from narcotics sales are frequently laundered through high-volume, low-ticket merchant accounts in sectors like food delivery, digital goods, or subscription services.
- Cybercrime — ransomware payments, data breach monetization, and business email compromise (BEC) fraud generate proceeds that move rapidly through cryptocurrency, wire transfers, and payment platforms.
- Human trafficking — escort services, massage businesses, and certain gig-economy platforms have been identified as high-risk channels for trafficking proceeds.
Emerging and regulatory-priority categories:
- Tax crimes — included as a predicate offense since FATF's 2003 revision; proceeds from VAT carousel fraud and offshore evasion schemes are increasingly a focus.
- Environmental crime — illegal logging, waste trafficking, and protected species trade generate significant proceeds and are a growing FATF priority.
- Corruption and bribery — politically exposed persons (PEPs) routing bribe proceeds through payment accounts is a well-documented typology.
- Terrorism financing — distinct from other predicate crimes in that proceeds may be legitimately sourced but used for illegal purposes, requiring different detection logic.
Best Practices
For Merchants
Merchants rarely think of themselves as AML obligated entities, but in many jurisdictions — particularly those with broad definitions of "financial institution" or "payment service" — they carry direct compliance obligations. Even where they do not, their acquiring bank or payment processor will impose requirements contractually.
- Know your predicate exposure by vertical. A digital goods marketplace faces different typologies than a physical retail store. Map the predicate crime categories most likely to generate proceeds in your sector and tune your fraud and chargeback rules accordingly.
- Conduct enhanced due diligence on high-risk customers. Customers with unusual transaction patterns — high refund rates, rapid account cycling, mismatched shipping and billing data — may be using your platform to process predicate crime proceeds. Combine KYC verification with behavioral monitoring.
- File SARs promptly when red flags appear. Many merchants believe SAR filing is their acquirer's job. In jurisdictions where merchants qualify as reporting entities, the obligation is direct. When in doubt, consult legal counsel and err on the side of reporting.
- Train customer-facing staff on predicate crime typologies. Fraud team members who can recognize structuring patterns, refund cycling, or account takeover proceeds are your first line of defense.
For Developers
Developers building payment infrastructure, fraud tools, or compliance systems need to translate predicate crime typologies into concrete detection logic.
- Build typology-specific rule sets, not just threshold alerts. A $9,999 transaction is a classic structuring signal for drug proceeds, but drug trafficking also shows up as high-volume, low-value transactions across many accounts. Design rules that capture behavioral patterns, not just single-transaction flags.
- Implement graph-based network analysis. Predicate crime proceeds often involve rings of related accounts. Graph analytics that map fund flows across entities can surface laundering networks that per-account rules miss entirely.
- Log transaction context for SAR narrative support. When a SAR must be filed, compliance teams need narrative-quality data: timestamps, IP addresses, device fingerprints, merchant category codes, and counterparty details. Build this into your event logging from day one, not as an afterthought.
- Integrate sanctions screening at onboarding and on an ongoing basis. Many predicate crime actors appear on OFAC, UN, or EU sanctions lists. Screening only at account opening misses individuals who are listed after the account is established.
- Version-control your AML rule sets. Typologies evolve. A rule that caught drug proceeds typologies in 2022 may not catch cybercrime proceeds typologies in 2026. Treat your monitoring logic as a living artifact with regular review cycles.
Common Mistakes
Even sophisticated payment businesses make predictable errors when building predicate crime controls. These five mistakes are the most costly.
1. Treating predicate crimes as a fraud problem, not a compliance problem. Fraud and AML teams often operate in silos. A fraud ring that is caught and blocked has still generated SAR-triggering activity — if no SAR is filed because the fraud team handled it as a chargeback dispute, the compliance obligation was missed.
2. Mapping monitoring rules only to dollar thresholds. Structuring — breaking transactions into amounts below reporting thresholds — is a defining feature of predicate crime proceeds. Rule sets that only flag large individual transactions will systematically miss structured activity.
3. Ignoring merchant category code (MCC) risk signals. Certain MCCs — adult entertainment, pawn shops, precious metals dealers, money service businesses — are disproportionately associated with predicate crime proceeds. Failing to apply enhanced scrutiny to these categories is a documented FATF examination finding.
4. Filing SARs only after loss is confirmed. The legal obligation to file a SAR is triggered by suspicion, not certainty. Waiting for a confirmed fraud loss before filing means the report is late — and the window for financial intelligence units to act on the information has closed.
5. Assuming the acquiring bank handles all AML obligations. Acquirers are reporting entities, but they rely on merchants to surface predicate crime signals from transaction-level data. Merchants who treat AML as entirely outsourced to their processor leave systematic gaps that regulators — and prosecutors — have increasingly targeted.
Predicate Crimes and Tagada
Tagada operates as a payment orchestration layer, routing transactions across multiple acquirers and processors. This position in the payment stack creates both exposure and opportunity when it comes to predicate crime proceeds.
How Tagada Helps Manage Predicate Crime Risk
Because Tagada sits above multiple processing connections, it can apply consistent AML rule sets across all payment routes — ensuring that a transaction flagged for predicate crime typologies is not simply rerouted to a less-scrutinized acquirer. Merchants using Tagada can configure routing logic that automatically declines or escalates transactions matching high-risk predicate crime patterns, and can centralize SAR-ready transaction logs across all their processing relationships in a single data layer — simplifying both compliance reporting and forensic investigation when required.