Study guide
5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk
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
5.2 Risk-Based Approach, Risk Assessment, Risk Appetite, and Types of Risk
Key Takeaways Explain This Topic AI
FATF Recommendation 1 requires countries and firms to identify, assess and understand ML/TF risks and to apply a risk-based approach.
A business-wide risk assessment scores inherent risk by customer, product, geography and channel, then subtracts control effectiveness to find residual risk.
A risk appetite statement is board-approved and combines qualitative limits with measurable metrics, tolerances and escalation triggers.
Since an April 2026 final rule, the OCC and FDIC no longer criticise banks on the basis of reputation risk, though reputation remains a real business risk.
Last updated: October 2026
CAFCA sub-topic 1.6 asks for the definitions and key components of the risk-based approach (RBA) , risk assessment and risk appetite , why they exist, and when to review them. Sub-topic 1.10 adds the types of risk a FinTech faces. The exam often frames these as decisions. Should the firm accept a new customer segment? Is a control proportionate? What happens when a metric breaches appetite?
The risk-based approach
FATF Recommendation 1 requires countries, and through national law financial institutions, to identify, assess and understand their money laundering and terrorist financing risks. Resources and controls should be matched to those risks: enhanced measures where risk is higher, and simplified measures where risk is demonstrably lower and the law allows it. The RBA is not a licence to accept any risk, and it does not demand zero risk. It is a disciplined way to allocate limited controls and to explain those choices to supervisors and partner banks.
The business-wide risk assessment
Most regimes call it the business-wide or enterprise-wide risk assessment (BWRA or EWRA). It has three layers:
Inherent risk : the risk before controls, scored by factor:
Customers : retail versus business, PEPs, MSB or crypto clients, high-risk industries, non-resident customers.
Products and services : instant P2P, cross-border payouts, cash loading, virtual cards, crypto on- and off-ramps, credit.
Geographies : where customers live and where funds come from and go, including FATF-listed and sanctioned jurisdictions.
Delivery channels : fully remote onboarding, embedded partners, agents, API access.
Transactions : volumes, values, velocity and anonymity features.
Control effectiveness : how well CDD, screening, monitoring, training and governance reduce each risk. Use evidence such as QA error rates, testing results and audit findings, not opinion.
Residual risk : what remains after controls. Compare it with appetite. Residual risk above appetite needs action: stronger controls, product limits, exiting a segment, or formal acceptance by the right authority.
Good assessments use both quantitative data (customer mix, volumes by corridor, alert and SAR statistics, fraud losses) and qualitative judgement (national risk assessments, FIU alerts, typology reports). They document the methodology so that the result can be repeated and challenged.
Risk appetite
A risk appetite statement (RAS) is the board's statement of the type and amount of risk the firm is willing to accept in pursuit of its objectives. For financial crime it usually combines:
- Element Example
- Zero-tolerance statements No shell banks; no unlicensed money transmitters; no sanctioned-country business
- Qualitative limits Crypto ramps only for verified customers in approved countries
Quantitative metrics High-risk customers no more than 8% of the active base; payouts to grey-listed countries below a set share of volume
Tolerances and triggers Alert backlog older than 30 days above a set number escalates to the risk committee
Risk appetite is not the risk assessment. The assessment measures risk. The appetite states what is acceptable. Monitoring compares the two and drives decisions.
When to review
Refresh the assessment and appetite:
On a fixed cycle , often annually for the business-wide assessment. Some laws, such as the EU AML package, specify review expectations.
When a trigger occurs : a new product or feature, entry into a new country, a new delivery channel or partner, a major change in customer mix, an enforcement action or audit finding, a new national risk assessment or FATF listing, or a significant incident. Chapter 18 covers triggers in detail.
Types of risk (sub-topic 1.10)
Risk type Meaning FinTech example
Regulatory / compliance Breach of laws, rules or licence conditions Fines or licence restrictions after a weak onboarding programme
Legal Litigation, contract disputes, liability Claims by scam victims or by the partner bank under indemnities
Operational Failed processes, people, systems or external events Screening outage; vendor failure; insider fraud
Financial Direct losses and capital or liquidity effects Chargebacks, fraud write-offs, penalties, reserve shortfalls
Business / strategic Threat to the business model or growth plan Partner bank exits the programme; payment network suspends the FinTech
Reputational Loss of trust among customers, partners and investors Media coverage of mule accounts on the platform
These risks are linked. A single financial crime failure can produce all six. In the US, the OCC and FDIC adopted a final rule in April 2026 under which they no longer criticise or take adverse action against banks on the basis of "reputation risk" as a separate supervisory category. For a FinTech, reputation still affects partners, investors and customers, so it stays in the firm's own assessment.
Realistic exam scenario
A payments FinTech's annual assessment shows that payouts to two grey-listed jurisdictions have grown from 6% to 19% of volume. Monitoring alert volumes on those corridors have also doubled. The board's appetite metric caps such corridors at 10%. Compliance should report the breach to the risk committee, propose options with their trade-offs, and document the decision. The options include corridor limits, enhanced due diligence for those payees, temporary caps, or exiting the corridor. Ignoring the breach because "revenue is strong" is not a risk-based approach.
Common exam traps
RBA means "no controls for low risk". Wrong. Low-risk customers still get core CDD, screening and monitoring.
Confusing inherent and residual risk.
A static assessment. It must change when the business changes.
Appetite set by the product team alone. Appetite is a board-level decision.