Study guide

4.4 Sources of Guidance for Building Anti-Financial Crime Processes

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

4.4 Sources of Guidance for Building Anti-Financial Crime Processes

Key Takeaways Explain This Topic AI

Statutes and regulations bind firms directly, while FATF Recommendations bind countries and reach firms through national law.

FinCEN alerts and advisories give SAR key terms, such as FIN-2024-DEEPFAKEFRAUD, that firms enter in SAR field 2 and the narrative.

FATF updates its black and grey lists of high-risk jurisdictions three times a year, after its February, June and October plenaries.

In the UK, the JMLSG guidance is industry guidance approved by HM Treasury; the FCA considers it when judging compliance with the Money Laundering Regulations.

Last updated: October 2026

When a FinTech designs a new onboarding flow, monitoring scenario or SAR process, it needs a basis for each control. CAFCA sub-topic 1.7 asks which types of sources can guide that work. The underlying skill is judging authority. A blog post from a vendor is not equal to a regulator's rulebook.

The source hierarchy

Tier Examples How binding?

1. Law and regulation US Bank Secrecy Act and 31 CFR Chapter X; EU AML Regulation and directives; UK Money Laundering Regulations 2017 and POCA 2002; Singapore's MAS Notices Legally binding on the firm

2. Supervisory rules and guidance FFIEC BSA/AML Examination Manual; FCA Handbook and Financial Crime Guide; EBA guidelines (for example on ML/TF risk factors and remote onboarding); MAS guidelines Rules bind; guidance sets examiners' expectations

3. International standards FATF Recommendations, interpretive notes, guidance papers and mutual evaluation reports; Basel Committee papers Bind countries and shape national law; firms use them to interpret risk

4. FIU products FinCEN advisories and alerts with SAR key terms; UK Financial Intelligence Unit material; Egmont Group papers Practical red flags and reporting instructions

5. Industry guidance UK JMLSG Guidance (approved by HM Treasury); Wolfsberg Group principles and questionnaires; trade association papers Persuasive; some is formally recognised

6. Threat and typology reports FATF typology studies; national risk assessments; Europol reports; blockchain analytics firms' crime reports Evidence for risk assessments and scenario design

7. Enforcement actions Consent orders, final notices, penalty announcements Show what regulators treat as failure

8. Internal sources Business-wide risk assessment, audit and QA findings, SAR trends, loss data Firm-specific evidence; drives tuning

How each source is used in practice

Designing remote onboarding. In the EU, the EBA Guidelines on the use of remote customer onboarding solutions (EBA/GL/2022/15) set expectations for document and biometric checks. FATF's 2020 Guidance on Digital Identity explains assurance levels for digital ID systems.

Setting high-risk country lists. FATF publishes its "high-risk jurisdictions subject to a call for action" (the black list) and "jurisdictions under increased monitoring" (the grey list) after each plenary in February, June and October. National lists, such as the EU's list of high-risk third countries, may differ. Firms combine these with their own risk indicators.

Writing monitoring scenarios. FIU alerts describe current typologies and ask for specific key terms. FinCEN's 2023 pig-butchering alert asks filers to use FIN-2023-PIGBUTCHERING , and its 2024 deepfake alert asks for FIN-2024-DEEPFAKEFRAUD , in SAR field 2 and the narrative.

Answering partner-bank due diligence. The Wolfsberg Group, an association of global banks, publishes the Correspondent Banking Due Diligence Questionnaire (CBDDQ) and the Financial Crime Compliance Questionnaire (FCCQ). Bank partners often send these to FinTechs.

Benchmarking controls. Enforcement actions show which failures attract penalties: unmanaged growth, alert backlogs, weak partner oversight, and missing data feeds.

Judging a source

Before relying on a source, check five things:

Authority. Who issued it, and is it law, rule, guidance or opinion?

Jurisdiction. Does it apply where the firm is licensed and where its customers are?

Currency. Has it been replaced, withdrawn or amended? Guidance changes. For example, FinCEN withdrew its 2020 unhosted-wallet proposal in October 2026.

Applicability. Does it cover the firm's type of institution and product?

Consistency. Does it conflict with a higher-tier source? If so, the higher tier wins.

Record the sources behind each policy in a regulatory mapping or obligations register. Then, when a source changes, the affected procedures can be found and updated. That link also feeds the change triggers covered in Chapter 18.

A simple register row might read: Obligation : verify the identity of remote applicants. Source : national AML law article and EBA/GL/2022/15. Owner : Head of Onboarding (first line). Control : document check plus liveness plus database match. Test : monthly QA sample by second line. Last reviewed : date. Keep the register current. When a supervisor issues new guidance, the row shows at once which procedure, owner and test must change. This also gives evidence that the firm follows a defined review process. FinTechs that grow quickly often lose this traceability, and examiners then find controls that nobody can explain.

Internal sources belong in the same register. A rising rate of SARs filed on a single product, repeated audit findings on alert closure quality, or fraud losses concentrated in one channel are often better guides to where controls need work than any external publication. Treat them as evidence, and record what changed as a result.

Realistic exam scenario

A FinTech authorised in Ireland is designing onboarding for customers in Ireland and Germany. The project team has collected a FATF guidance paper, the EBA remote onboarding guidelines, a vendor white paper claiming "liveness is optional for low-risk users", and a Central Bank of Ireland supervisory statement. The compliance lead should base the design on the binding Irish AML law and the EBA guidelines, which supervisors apply. FATF guidance helps interpret risk. The vendor paper is commercial opinion and cannot override the guidelines.

Common exam traps

"FATF Recommendations directly bind private firms." They bind countries. Firms are bound by the national law that implements them.

Treating vendor marketing as regulatory guidance.

Using withdrawn or superseded guidance without checking whether it is current.

Ignoring internal sources. The firm's own SAR and loss data are often the best evidence for tuning.