Study guide

18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review

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

18.3 Changes That Should Trigger a Financial Crime Risk Assessment Review

Key Takeaways Explain This Topic AI

New products, new countries, new customer segments and new distribution partners are standard triggers for a financial crime assessment review.

Regulatory and sanctions changes, such as the US revocation of the Syria sanctions programme on 1 July 2025, require screening rules and procedures to be updated.

Acquiring a company or a customer portfolio means inheriting its customers and risks, so it should trigger due diligence and a review of the combined risk.

A trigger register records each event, its impact assessment, the decision taken and the owner, so that reviews are traceable.

Last updated: October 2026

CAFCA sub-topic 5.3 asks about the types of changes that should lead to a financial crime assessment review . A scheduled annual review is not enough for a FinTech that changes every sprint. The firm needs a defined list of triggers and a light, proportionate process for assessing each one.

The trigger list

Trigger category Examples Minimum response

Products and features New account type, crypto, credit, instant payouts, removing a hold New product approval assessment (Chapter 18); update the risk assessment

Markets and geographies Entering a new country; adding payout corridors; serving non-residents Corridor and country assessment; licensing; sanctions lists; local rules

Customer segments Onboarding businesses, minors, MSBs or VASPs, high-risk industries New CDD standards and rating factors; monitoring baselines

Channels and partners New embedded-finance partner; agents; white-label deals; API resellers Partner due diligence; nested-risk analysis; data feeds

Technology and vendors New identity verification vendor, screening tool or monitoring system; AI models Validation and parallel running; gap analysis; model governance

Corporate events Merger, acquisition of a portfolio, change of ownership or control Due diligence on acquired customers; integration plan; combined risk review

Material growth or volume shifts Customer base doubles; a corridor spikes; a new marketing campaign Data refresh; capacity modelling (Chapter 18)

Regulatory change New laws and rules (for example the EU AML Regulation from July 2027, implementing rules under the US GENIUS Act, FinCEN exceptive relief or withdrawn proposals) Obligations-register update; policy and procedure changes

Sanctions and FATF changes New designations or programmes; lifted programmes; FATF list changes after each plenary Update screening configuration, high-risk country lists and EDD rules

Typology intelligence New FIU alert, national risk assessment or partner-bank intelligence New or tuned scenarios; training

Internal events Audit or exam findings; a large fraud loss; data breach; control failure; spike in SARs on one product; enforcement Root-cause analysis; targeted reassessment; remediation

Partner requirements Sponsor bank changes its risk appetite or prohibited list Update the policy and customer terms to match (Chapter 17)

Example: sanctions programme changes

Sanctions change in both directions. On 30 June 2025 , US Executive Order 14312 revoked the Syria sanctions programme with effect from 1 July 2025 . OFAC removed the Syrian Sanctions Regulations and delisted hundreds of persons, while keeping targeted measures against Assad-linked and other actors under a new programme. A FinTech that kept Syria as a comprehensively sanctioned country in its geofencing and screening rules would block lawful activity. One that removed every Syria control would miss the persons who remain designated. The change is a trigger: review the rules, update the configuration, keep the lists that still apply, and record the decision. The same applies when new programmes start or existing ones tighten.

A proportionate trigger process

Identify : product, legal, sanctions and operations teams log triggers in a trigger register . Make it part of change management and new product approval.

Assess impact : a short assessment asks which risk factors change, which controls are affected and whether residual risk moves against appetite.

Decide the scope : a targeted update of one section, or a full refresh if the change is material.

Act : update controls, procedures, training and MI.

Record : the decision, the owner, the date and the evidence. Examiners ask how the firm learned of a change and what it did.

Calibrate the process so that it is used. If every minor release needs a full reassessment, teams will avoid logging triggers. If nothing ever does, the register becomes decoration. A short screening question in the release checklist works well in practice: "Does this change who can use the product, where money can go, how fast it moves, or what data we capture?" A yes routes the change to compliance.

Who owns trigger monitoring

Compliance or the MLRO owns the process and the final assessment.

Product and engineering must notify compliance of feature changes through the release process.

Legal and regulatory affairs watch for law changes.

Sanctions teams watch list and programme updates.

Partnership teams report new and changed partners.

Realistic exam scenario

A payments FinTech acquires a smaller competitor with 80,000 business customers in three new countries. The deal closes on Monday, and integration is planned for six weeks later. This is a trigger for due diligence on the acquired portfolio: risk ratings, CDD quality, open alerts and SAR history, and sanctions exposure. It also triggers a review of the combined risk assessment covering the new countries and segments, and a remediation plan for gaps before the customers move onto the main platform. The partner bank should be told as the contract requires.

Common exam traps

Waiting for the annual cycle after a major change.

Forgetting lifted sanctions. Lifting a programme is a trigger too, and stale rules create compliance and fairness problems.

Acquiring customers without reviewing their CDD.

No record of what triggered a review and what changed.