Study guide

9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work

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

9.2 Customer Risk Ratings: Factors, Data Sources, and How Scoring Models Work

Key Takeaways Explain This Topic AI

Customer risk ratings typically combine customer, geography, product, channel and expected-activity factors into a weighted score with defined thresholds.

Override rules ensure that some facts, such as PEP status or a confirmed sanctions nexus, set a minimum rating or a prohibition regardless of the score.

Dynamic models re-score customers when their behaviour or data changes, such as new alerts, SAR filings or a change of country.

Risk scoring tools should be documented, tested and validated, and each rating must be explainable to examiners and partner banks.

Last updated: October 2026

CAFCA sub-topic 2.6 covers risk ratings : the types of risk factors, what information to include, how to access it from internal and external sources, and how risk algorithms work . The rating is where CDD turns into action. It decides who gets EDD, how closely monitoring watches each customer, how often KYC is refreshed, and who must approve the relationship.

Risk factors

Factor group Examples of inputs Higher-risk signals

Customer Individual or entity type, occupation or industry, ownership complexity, PEP status, adverse media, age of relationship Cash-intensive or high-risk industries; nominee structures; PEPs; negative news

Geography Residence, nationality, place of incorporation, countries of counterparties FATF-listed countries, sanctions-adjacent regions, high-risk corridors

Products and services Products used: P2P, cross-border, cash load, crypto, virtual cards, credit Anonymity, speed, cross-border reach, cash

Delivery channel Remote, via an embedded partner, via an agent or intermediary Non-face-to-face without strong eKYC; third-party introducers

Expected and actual activity Declared volumes and values, actual behaviour, alert and SAR history Activity far above the baseline; repeated alerts; SAR filed

Where the information comes from

Internal : application data, KYC documents, beneficial ownership certifications, transaction history, device and IP data, alert and case outcomes, SAR records, fraud claims, complaints.

External : screening results (sanctions, PEP, adverse media), registries, bureau data, country risk sources such as FATF lists and national risk assessments, consortium fraud data.

Keep a data dictionary that names each input, its source, how often it refreshes, and who owns its quality. Poor data quality is the most common reason ratings fail.

  • How rating algorithms work
  • 1. Weighted scorecards (most common)

Each factor gets a score, for example from 1 (low) to 3 (high), and a weight. The total maps to bands.

Worked example. Weights: customer 20%, geography 30%, product 25%, channel 15%, activity 10%. A sole trader (customer score 2) in a medium-risk country (geography 2) using cross-border payouts (product 3), onboarded fully remotely with strong eKYC (channel 2), with expected activity in line with the trade (activity 1):

  • Factor Score Weight Weighted
  • Customer 2 0.20 0.40
  • Geography 2 0.30 0.60
  • Product 3 0.25 0.75
  • Channel 2 0.15 0.30
  • Activity 1 0.10 0.10
  • Total 2.15

If the policy bands are low below 1.8, medium from 1.8 to 2.4, and high above 2.4, this customer is medium risk.

2. Override and knock-out rules

Some facts must decide the outcome whatever the score. A foreign PEP sets the rating to at least high. A confirmed sanctions nexus means prohibit or exit. A SAR filed in the past year may set a minimum of high. Any manual override must be justified, approved and logged.

3. Dynamic re-scoring

Ratings should update when inputs change: new alerts, a SAR, an address change to a high-risk country, a new product, or activity well above the baseline. A rating fixed at onboarding goes stale fast in FinTech.

4. Statistical or machine learning models

Some firms predict the risk of SAR-worthy activity from historical outcomes. They need clear features, explainability (for example, showing the top contributing factors for each customer), bias testing and independent validation. Supervisors and partner banks will ask why a customer is rated low.

What the rating drives

A rating matters only if it changes treatment. A typical mapping looks like this:

  • Rating Due diligence Monitoring Review cycle Approval
  • Low Standard CDD Standard scenarios Event-driven, plus a periodic refresh Automated within policy

Medium Standard CDD plus extra purpose and activity questions Some lower thresholds Periodic, for example every two years Analyst

High EDD, including source of funds and wealth where relevant Enhanced scenarios and tighter thresholds At least annually Senior compliance or management

Prohibited Do not onboard; exit existing relationships Not applicable Not applicable MLRO decision

The review cycles shown are examples of common practice, not legal requirements. Firms set them in policy based on their own risk assessment.

Governance of the model

Document the methodology, weights, thresholds and the rationale for each.

Test before launch : does the distribution make sense, and do known high-risk customers land in the high band?

Validate periodically and review the outcomes. Track whether SARs come mainly from "low-risk" customers, which would suggest miscalibration.

Control changes to weights and thresholds with approval and an audit trail.

Report the rating distribution and migrations in MI (Chapter 14).

Realistic exam scenario

After a scoring update, 97% of a neobank's customers are rated low. Yet 40% of last quarter's SARs involved customers who were rated low at the time. The pattern suggests the model under-weights behavioural signals or lacks dynamic re-scoring. Compliance should open a model review, test re-weighted options with below-the-line analysis, add behaviour-based triggers such as alerts and velocity, and record the change with validation evidence. Simply moving the band thresholds until the distribution "looks right" without analysis is not defensible.

Common exam traps

Static ratings that never change after onboarding.

Unexplained weights : "the vendor set them" is not a rationale.

Manual downgrades without approval or evidence.

Ignoring override rules , for example a foreign PEP rated low because the other factors scored low.