Study guide
17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties
ACAMS Certified AML FinTech Compliance Associate CAFCA
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: CAFCA Exam Overview and Study Strategy
1.1 CAFCA Exam Format, Official Domains, and Study Strategy
2 Chapter 2: Domain 1: FinTech Business Models and Their Vulnerabilities
2.1 Neobanks, Challenger Banks, and Digital Banking Models 2.2 Payment Processors, Gateways, and Merchant Acquirers 2.3 Buy Now, Pay Later (BNPL) and Alternative Credit 2.4 BaaS Architecture, Embedded Finance, and Program Structures
3 Chapter 3: Domain 1: Financial Crime Types and the Regulatory Perimeter
3.1 Types of Financial Crime and Predicate Offences 3.2 Licensing, Registration, Charters, and Regulatory Sandboxes 3.3 Virtual Asset Service Provider (VASP) Framework & FinCEN MSB Rules
4 Chapter 4: Domain 1: Global AML Frameworks and Sources of Guidance
4.1 U.S. Regulatory Architecture: BSA, PATRIOT Act, and AMLA 2020 4.2 European Union Regulatory Framework: AMLD6, the AML Package, and MiCA 4.3 International Standards: UK FCA, Singapore MAS, and Hong Kong HKMA 4.4 Sources of Guidance for Building Anti-Financial Crime Processes
5 Chapter 5: Domain 1: Risk Management Framework, Risk-Based Approach, and Data Protection
5.1 Risk Management Framework: Lines of Defence, Policies, Assurance, and the MLRO 5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk 5.3 Handling Sensitive Information: PII, SPII, Privacy Laws, and Breach Reporting
6 Chapter 6: Domain 1: Bank Partners and Internal Threats
6.1 Regulatory Expectations and Enforcement on Sponsor Banks 6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking 6.3 Controlling Internal Threats: Insider Fraud, Collusion, and Data Misuse
7 Chapter 7: Domain 2: CIP, KYC, CDD, and EDD
7.1 Customer Identification Program (CIP) Under USA PATRIOT Act §326 7.2 The FinCEN CDD Rule & Beneficial Ownership Standards 7.3 KYC to EDD: Applying CDD and Enhanced Due Diligence Across Customer Types
8 Chapter 8: Domain 2: Identity Verification, Data Sources, and Device Data
8.1 Digital Onboarding & Electronic KYC (eKYC) Foundations 8.2 Biometric Face Matching and Liveness Detection 8.3 Verification Data Sources and How to Judge Their Reliability 8.4 Device Fingerprinting, Geolocation, and Behavioral Biometrics
9 Chapter 9: Domain 2: Onboarding Screening, Risk Ratings, and Fraud Red Flags
9.1 Screening at Onboarding: Sanctions Lists, PEPs, and Known Fraudsters 9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work 9.3 Detecting Synthetic Identity Fraud and Ineligible Applicants 9.4 Deepfakes, Generative AI Threats, and Scam Typologies
10 Chapter 10: Domain 3: Payment Screening
10.1 OFAC Sanctions Regimes & the 50 Percent Rule 10.2 Real-Time vs. Batch Screening Architecture in High-Velocity Rails 10.3 Screening Logic: Fuzzy Matching, Phonetics, and PEP Controls
11 Chapter 11: Domain 3: Transaction Monitoring Systems and Red Flags
11.1 Hybrid Transaction Monitoring: Rules Engines vs. Machine Learning 11.2 FinTech Typologies: Mule Networks, Funnel Accounts, and Rapid Pass-Through 11.3 Fraud-AML Convergence: BIN Attacks, ATO, and Credential Stuffing 11.4 Model Risk Management Under SR 11-7 & System Optimization
12 Chapter 12: Domain 3: Payment Methods and Transaction Risk Characteristics
12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation 12.2 Transaction Risk Characteristics: Reversibility, Convertibility, Fund Integrity, and Privacy Coins 12.3 Wallet Types, Custody Architectures, and Counterparty Risks 12.4 Stablecoins, On/Off Ramps, and Asset-Referenced Tokens
13 Chapter 13: Domain 3: Monitoring Crypto Transactions
13.1 Blockchain Analytics & Transaction Tracing 13.2 The FATF Travel Rule for Virtual Assets 13.3 DeFi, Mixers, and Smart Contract Sanctions
14 Chapter 14: Domain 3: Alert Investigation, Audit Trails, and Monitoring MI
14.1 The Alert Investigation Process: From Unusual to Suspicious and When to Escalate 14.2 Building an Audit Trail for Suspicious Activity Reviews 14.3 Communicating Monitoring Results: KPIs, KRIs, OKRs, and Management Information
15 Chapter 15: Domain 4: Investigations and Customer Communication
15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach 15.2 Reviewing KYC, Transactions, Open Sources, and Documents to Build an Investigation 15.3 Analytical Principles in Investigations: Avoiding Confirmation Bias and Other Traps
16 Chapter 16: Domain 4: SARs and STRs
16.1 SARs and STRs: What They Are, When and Where to File, and Why They Matter 16.2 Writing Effective SAR and STR Narratives
17 Chapter 17: Domain 4: Law Enforcement, Regulators, and Banking Partners
17.1 Operational AML Governance and Third-Party Risk Management 17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties 17.3 Types of Law Enforcement Requests: Subpoenas, Court Orders, 314(a), and International Requests 17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms
18 Chapter 18: Domain 5: Scaling Anti-Financial Crime Strategies
18.1 Assessing New Products and Features Before Launch 18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales 18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review 18.4 Record Retention Rules and Secure Data Storage 18.5 Outsourcing Controls: Surge Capacity, RegTech, and Independent Testing
17.2 Working With Law Enforcement, Banking Partners, Regulators, and Other Third Parties
Key Takeaways Explain This Topic AI
Requests that claim to come from law enforcement should be verified through official contact details before any data is released, because fake emergency requests are a known fraud.
Public-private partnerships such as the UK's JMLIT (2015) and FinCEN Exchange (2017) let firms and agencies share intelligence on priority threats.
UK FCA Principle 11 requires firms to deal with regulators openly and cooperatively and to disclose anything the regulator would reasonably expect notice of.
US financial institutions registered under section 314(b) may share information with each other about possible money laundering or terrorist financing under a safe harbour.
Last updated: October 2026
CAFCA sub-topic 4.5 asks how to work and communicate with third parties , such as law enforcement, banking partners and regulators. These relationships decide whether intelligence turns into action, whether a partner bank keeps confidence in the programme, and whether a supervisor sees the firm as cooperative or evasive.
Law enforcement
Inbound requests. Run all law enforcement contact through a single point of contact , such as a law enforcement liaison or subpoena response team, with a logged intake.
Verify the requester. Confirm identity and authority through the agency's official switchboard or portal, not the phone number or email in the request. Fraudsters impersonate police and agencies, including with fake "emergency" requests.
Confirm the legal basis and scope. Is it a compulsory order, a voluntary request, a 314(a) search, or a request for SAR supporting documentation? (Chapter 17 lists the types.)
Apply privacy and confidentiality rules. Disclose what the law requires or permits. Voluntary disclosure must have a lawful basis under privacy and financial privacy laws.
Meet deadlines and produce accurately. Quality-check productions, log what was sent, and use secure transfer.
Respect non-disclosure. Many requests carry confidentiality terms. Do not tell the customer.
Review the relationship. A request is not itself proof of wrongdoing. US examiners say a subpoena alone should not automatically trigger a SAR, but it should prompt a risk review of the customer.
Proactive engagement. Firms add value through public-private partnerships. Examples include the UK's Joint Money Laundering Intelligence Taskforce (JMLIT, 2015) , FinCEN Exchange (2017) in the US, and Singapore's AML/CFT Industry Partnership (ACIP, 2017) . They also use fraud recovery channels such as the FBI's Internet Crime Complaint Center and FinCEN's Rapid Response Program for urgent international wire recalls.
Banking partners
In BaaS, sponsorship and correspondent models, communication with the bank is set by contract (Chapter 6):
Referral protocols : what the FinTech must escalate to the bank (unusual activity, potential SAR matters, sanctions hits, law enforcement requests), within what time, and in what format.
Information sharing : FinCEN-registered US institutions can share information about possible money laundering or terrorist financing under section 314(b) , with a safe harbour. Joint SARs are possible between institutions involved in the same transaction. A SAR itself, and information that would reveal it, may be shared only where the rules expressly allow it.
Incident notification : data breaches, control failures, outages and regulatory contact, as the agreement requires.
Consistent customer messaging : agree who tells the customer what, so that the bank and the FinTech do not contradict each other or tip off.
Regulators
Candour and cooperation. In the UK, FCA Principle 11 requires firms to deal with regulators openly and cooperatively and to tell the FCA about anything it would reasonably expect to hear about. Other supervisors expect the same in substance.
Timely self-reporting of material breaches, as rules and licence conditions require.
Examination management : one coordinator, accurate document productions, management responses to findings, and remediation plans with realistic dates and owners. Never overpromise dates you cannot meet.
Consistency : the information given to the regulator, the partner bank and the board must tell the same story.
Other third parties
Card networks and payment schemes have rules on fraud reporting, high-risk merchants and data security.
Other FinTechs and VASPs : share information through lawful channels, such as 314(b), Travel Rule messaging and industry fraud-sharing schemes. In the UK, the Economic Crime and Corporate Transparency Act 2023 removed civil liability for breach of confidence for certain sharing between regulated firms to prevent economic crime.
Vendors : incident notification, audit cooperation and data handling under contract (Chapter 18).
Communication principles that apply to every party
- Principle In practice
- Verify Confirm identity and authority before sharing
- Lawful basis Know which law or contract allows the disclosure
- Minimise Share what is needed, securely
- Protect SAR confidentiality Never reveal a SAR outside permitted channels
- Document Log requests, decisions and what was sent
- Be accurate and timely Correct mistakes quickly; meet deadlines
- Realistic exam scenario
A support agent receives an email from a Gmail address signed "Special Agent, FBI". It asks for full account details and recent IP logs for three customers "within the hour" for an emergency. The agent should not respond with data. The request goes to the law enforcement liaison, which verifies it through the FBI's official channels. Production follows only if the request is genuine and lawful. If the request proves fake, it may itself indicate an attempt at account takeover or data theft and should be escalated to security.
Common exam traps
Sending data in reply to an unverified request.
Telling the customer about a law enforcement request.
Over-sharing with the partner bank by forwarding SAR copies where the rules do not permit it.
Hiding problems from the regulator until the next examination.