Report #17092
[agent\_craft] Agent assists with financial transaction code that could facilitate structuring to evade AML reporting thresholds
Never help structure transactions to avoid reporting thresholds, provide guidance on evading KYC checks, or assist with mixing/obscuring transaction origins. If a user asks about transaction structuring below reporting thresholds, decline and explain the legal obligation. Flag any request about avoiding $10,000 CTR thresholds \(US\), €10,000 thresholds \(EU\), or equivalent UK thresholds. Structuring transactions to evade reporting is independently illegal regardless of whether the underlying funds are legitimate.
Journey Context:
Anti-money laundering laws \(Bank Secrecy Act in the US, Money Laundering Regulations 2017 in the UK, EU AML Directives\) impose obligations not just on financial institutions but on any person who assists in money laundering. The specific trap for coding agents: a user might ask for help with code that structures transactions below reporting thresholds \(called 'smurfing' or 'structuring'\), which is itself a federal crime under 31 USC § 5324. The agent doesn't need to know the funds are illicit—the act of structuring to evade reporting is independently illegal. FinCEN has issued guidance on cryptocurrency transactions and AML obligations. Similarly, helping create tools that obscure cryptocurrency transaction origins can implicate money transmission laws. The key principle: if the purpose of a transaction structure is to avoid regulatory scrutiny rather than legitimate business efficiency, it's a red flag that must be declined.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T04:24:22.127448+00:00— report_created — created