Study guide
18.2 Refreshing the Financial Crime Risk Assessment as the Business Scales
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.2 Refreshing the Financial Crime Risk Assessment as the Business Scales
Key Takeaways Explain This Topic AI
Enforcement actions against BaaS banks in 2023 and 2024 repeatedly cited growth that outpaced compliance staffing, systems and oversight.
A refresh uses current data on customers by risk rating, volumes by product and corridor, alert and SAR statistics, and fraud losses.
Capacity modelling links forecast customer growth to expected alert volumes and the analysts, tools and QA needed to handle them.
A refreshed risk assessment is shared with senior management, the board and partner banks, and it drives the budget and the control roadmap.
Last updated: October 2026
CAFCA sub-topic 5.2 emphasises the importance of reviewing and updating the risk assessment as part of scaling . Many FinTech financial crime failures share one storyline. The business grew quickly, the risk assessment stayed as it was written for a smaller firm, and the controls fell behind. Regulators' consent orders against BaaS sponsor banks in 2023 and 2024 repeatedly cited exactly this.
Why scaling changes the risk picture
Growth effect What happens Risk assessment impact
Volume More customers and transactions; more attention from criminals Inherent risk rises even if the customer mix stays the same
Customer mix Marketing reaches new segments, such as students, non-residents and small businesses New risk factors; the rating distribution changes
Geographic reach New countries, corridors and currencies Sanctions, corridor and licensing risk
Product breadth More features: credit, crypto, cards, instant payouts New typologies; product interactions such as rail arbitrage
Channels and partners Embedded finance and white-label deals Nested and third-party risk
Capacity strain Alerts grow faster than staff; backlogs build Control effectiveness falls, so residual risk rises
Technical debt Quick integrations, missing data fields, manual workarounds Data-quality gaps undermine screening and monitoring
How to refresh during growth
Refresh the data. Customer counts by segment and risk rating; volumes and values by product, channel and corridor; alert volumes and outcomes by scenario; SARs; fraud losses and chargebacks; QA results; complaints.
Re-score inherent risk for each factor using the new data, not last year's figures.
Re-test control effectiveness with current evidence: QA error rates, testing results, backlog ageing, data-feed completeness and audit findings.
Recalculate residual risk and compare it with the risk appetite . Flag any breaches.
Model capacity. Forecast customer growth, then expected alerts (alerts per 1,000 customers multiplied by growth), then the analysts needed at the expected productivity and quality, plus QA, training and tooling.
Decide on actions : hiring, automation and tuning, product limits, a slower rollout in high-risk areas, or exiting segments.
Report and approve. Present the findings to senior management and the board. Share them with partner banks as agreed, and tie them to the budget and roadmap.
A worked capacity example
A FinTech has 400,000 customers, generating 6 alerts per 1,000 customers each month: 2,400 alerts. Each analyst closes about 400 alerts a month at the required quality, so 6 analysts are needed. Marketing forecasts 1.2 million customers in 12 months. At the same alert rate that means about 7,200 alerts a month, or 18 analysts , before allowing for QA, leave, training or tuning. If the plan funds only 8 analysts, the refreshed assessment should show the expected backlog, the rise in residual risk, and the options to close the gap. Those options include tuning to cut false positives, automation, outsourced surge capacity (Chapter 18) and growth caps.
Signs that the assessment is out of date
The risk assessment still describes products or countries the firm launched or left months ago.
Alert or SAR volumes have changed sharply with no explanation in the assessment.
The partner bank's own analysis gives different risk levels from the FinTech's assessment.
Staffing plans assume last year's customer numbers.
New typologies reported by the FIU or the partner bank are not mentioned.
Control effectiveness ratings are based on opinion rather than recent testing or QA data.
Any of these signs should prompt an interim update rather than waiting for the annual cycle.
Frequency during scaling
An annual refresh is common practice, but fast-growing firms often need more frequent updates , for example quarterly checks of key metrics. They also need event-driven reviews when triggers occur (next section). The aim is to keep the assessment current , not to follow a calendar.
Communicating the refresh
Use a short executive summary covering what changed, where residual risk now exceeds appetite, and the decisions needed.
Explain trends with normalised figures (Chapter 14).
Give the partner bank enough detail to fulfil its own oversight duties.
Realistic exam scenario
A neobank's user base has grown tenfold in a year, but the risk assessment and staffing plan date from before the growth. Its sponsor bank cites a 60-day alert backlog. The MLRO should refresh the risk assessment with current data and quantify the capacity gap. The board should then approve a remediation plan with funding, interim growth limits on the highest-risk products, and agreed MI for the bank. Clearing the backlog by raising thresholds without analysis would be a further failure (Chapter 11).
Common exam traps
A risk assessment that never changes while the business grows.
Ignoring capacity : effective controls on paper are not effective in practice if the queue is months behind.
Treating growth as purely a commercial matter without considering financial crime.