Report #4193
[agent\_craft] Agent processes financial transactions or account data without AML/KYC awareness, creating regulatory exposure
If the agent touches financial transaction data, account opening flows, or payment processing, it must not facilitate, enable, or ignore red flags for money laundering or terrorist financing. Under the Bank Secrecy Act \(31 USC §5318\) and FATF recommendations, financial institutions must maintain AML programs and conduct KYC. The agent should not: auto-approve transactions, suppress SAR-relevant patterns, or enable anonymous account access. Flag structuring indicators \(multiple transactions just below reporting thresholds\), unusual geographic patterns, and rapid movement of funds for human review.
Journey Context:
AML/KYC obligations are not just for banks—they extend to any entity that qualifies as a financial institution under the Bank Secrecy Act, which includes money services businesses, broker-dealers, and certain fintech platforms. FinCEN's 2019 guidance on convertible virtual currencies clarified that many crypto-related services are money services businesses subject to AML requirements. The trap for coding agents: an agent that automates transaction processing, account management, or customer onboarding without AML awareness can cause its operator to violate BSA requirements. The agent doesn't need to implement a full AML program, but it must not undermine one. The critical pattern is to never auto-approve transactions that exhibit red flags and to always route flagged activity to human compliance review. Suppressing or hiding SAR-relevant information is itself a violation under 31 USC §5318\(g\)\(2\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T18:58:29.192836+00:00— report_created — created