Study guide

15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach

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

15.1 Talking to Customers During Investigations and Offboarding: Financial Crime Risk vs Policy Breach

Key Takeaways Explain This Topic AI

Customers can be asked about payment purpose, counterparties and source of funds, framed as routine account checks.

US law prohibits disclosing a SAR or any information that would reveal one; UK law creates tipping-off and prejudicing-an-investigation offences.

FinCEN 314(a) requests are confidential and must not be disclosed to the customer or any third party.

A policy breach can be explained to the customer; an exit driven by suspected financial crime uses neutral contractual wording and no hints about suspicion.

Last updated: October 2026

CAFCA sub-topic 4.1 covers appropriate customer communication : what questions can be asked, and what can be disclosed during investigations and offboarding. Sub-topic 4.7 covers communicating for financial crime risk versus violation of company policy . Front-line staff, support agents and investigators all talk to customers, so one careless sentence can ruin an investigation and expose the firm to criminal liability.

What you can ask

Requests for information (RFIs) are a normal part of CDD and investigations. Typical lawful questions:

What was the purpose of a payment, and what is the relationship with the counterparty?

Where did these funds come from ? Can you provide a contract, invoice, payslip, sale agreement or bank statement?

What does your business sell, to whom, and through which channels? Is this level of activity expected to continue?

Please confirm or update your identity and address details.

How to ask:

Frame it as routine : "As part of our regular account reviews, we need some information about recent activity."

Be specific about what you need , but do not say why you are asking.

Do not lead the customer towards an answer ("Was this money from your parents?").

Set a deadline and explain what happens if the information is not provided, for example restrictions under the terms.

Record the request and the response in the case file.

What you must never disclose

Do not disclose Why

That a SAR or STR has been, or may be, filed Tipping off: US 31 U.S.C. 5318(g)(2); UK POCA section 333A; EU AML rules

That an internal investigation or alert review is under way, where that could prejudice it UK POCA section 342 (prejudicing an investigation) and similar laws elsewhere

That law enforcement or FinCEN has made an inquiry (including a 314(a) request or a subpoena with non-disclosure terms) Confidentiality of the request; risk of evidence destruction

Internal risk scores, monitoring rules or the source of any intelligence Helps criminals evade controls

Phrases to avoid include "our AML team flagged you", "we're required to report this", "the police asked about your account" and "your transactions look like money laundering".

Offboarding communication

When a relationship ends:

Follow the contract and the law. Give the notice required by the terms and any applicable consumer or payment-services rules, unless immediate termination is permitted, for example where fraud is suspected.

Use neutral wording : "We have decided to close your account in line with section X of our terms." Many jurisdictions allow firms not to give a detailed reason where giving one would be unlawful or would tip off.

Handle the remaining balance lawfully. Funds may be returned to the customer or to the source. They may need to be frozen if they are blocked under sanctions, subject to a court or law enforcement order, or, in the UK, suspected criminal property needing a DAML before release.

Keep scripts consistent. Support agents should have approved wording and an escalation route for customers who ask "Is this because of a report?". An appropriate answer is: "We can't discuss our internal reviews, but here is how to collect your funds and make a complaint."

Coordinate with law enforcement. If law enforcement has asked the firm to keep an account open (a "keep open" request), the firm may comply under its policy, but the decision remains the firm's. Get the request in writing, as FinCEN guidance recommends.

Financial crime risk versus a breach of company policy (4.7)

Situation Example What to tell the customer

Policy or terms breach only Using a personal account for a business; a prohibited merchant category; excessive chargebacks; acceptable-use violations The specific breach, the clause concerned, and any remedy (open a business account, stop the activity)

Suspected financial crime Possible mule activity, laundering, scam proceeds, sanctions evasion Neutral contractual exit or restriction message, with no reference to suspicion or reporting

Both A prohibited merchant type that also looks like transaction laundering Rely only on the true, non-sensitive reason, worded carefully, or the neutral clause. Never invent a false reason

Even where only a policy breach is involved, consider whether it also raises suspicion before explaining it in detail. A detailed explanation might reveal the detection logic. Escalate unclear cases to the MLRO or legal team before contacting the customer.

Realistic exam scenario

A wallet customer whose outbound transfers are restricted calls support and demands to know whether "the bank reported me to the government". The agent should not confirm or deny anything about reporting. Instead the agent should explain that the account is under review in line with the terms, list any information requested and the deadline, and give the complaint route. The call note goes into the case file. Saying "we can't confirm a SAR" in a way that implies one exists would also be risky. Stick to approved wording.

Common exam traps

Explaining the real reason for a suspicion-driven exit "to be transparent". This can be tipping off.

Refusing to ask the customer anything for fear of tipping off. Neutral RFIs are allowed and useful.

Inventing false reasons for an exit. Use the neutral contractual basis instead.

Forgetting that 314(a) and law enforcement requests are confidential.