Study guide

18.1 Assessing New Products and Features Before Launch

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.1 Assessing New Products and Features Before Launch

Key Takeaways Explain This Topic AI

FATF Recommendation 15 requires firms to assess ML/TF risks before launching new products, business practices, delivery mechanisms or technologies, and to manage those risks.

Moving from domestic to international payments adds sanctions, Travel Rule, corridor-risk and licensing considerations.

New distribution channels such as embedded-finance partners or agents add third-party, data-visibility and nested-customer risk.

A post-launch review at set intervals checks whether actual usage, alerts and losses match the pre-launch risk assessment.

Last updated: October 2026

CAFCA sub-topic 5.1 asks how to assess new products and additional features , their potential risks and the necessary controls. The outline names the elements that present particular risks: products moving from domestic to international , new types of accounts , changes to payment processes , and added distribution channels . Scaling FinTechs ship features constantly. Compliance has to be part of the product lifecycle, not a sign-off at the end.

The legal anchor

FATF Recommendation 15 requires countries and financial institutions to identify and assess the money laundering and terrorist financing risks that arise from new products and new business practices , including new delivery mechanisms and new or developing technologies. The assessment should take place before launch , and appropriate measures should manage and reduce the risks. National rules and supervisory guidance build on this, and partner banks usually require a formal approval.

A new product approval (NPA) process

Stage Financial crime activities

1. Concept Early compliance involvement: does the feature create a new regulated activity? Is a licence or partner approval needed (Chapter 3)?

2. Risk assessment Assess customers, geographies, features, channels and transaction characteristics (reversibility, convertibility, speed, anonymity). Rate inherent risk

3. Control design Map the controls: CDD level, screening points, monitoring scenarios and thresholds, limits and holds, fraud controls, reporting routes, MI

4. Data and systems Confirm that every new transaction type and field reaches screening and monitoring; update the data dictionary

5. Testing User acceptance testing that includes compliance cases, such as a test sanctions hit, a test alert and a test hold

6. Approval Sign-off by compliance or the MLRO, plus partner-bank approval where required; record residual risk against appetite

7. Controlled launch Pilot or phased rollout with customer caps and value limits

8. Post-launch review At, for example, 30, 90 and 180 days: compare actual usage, alerts, SARs and losses with assumptions; tune controls

The four elements the outline highlights

Change New risks Typical controls

Domestic to international (cross-border payouts, multi-currency, foreign customers) Sanctions and high-risk corridors; Travel Rule data; correspondent and payout-partner risk; foreign licensing; FX-based layering Multi-list screening; corridor risk ratings and limits; payout-partner due diligence; Travel Rule messaging; local licence analysis

New account types (business accounts, joint accounts, accounts for minors, multi-currency, crypto) Beneficial ownership and KYB; legal capacity issues; different expected activity Entity CDD and beneficial ownership; new risk-rating factors; new monitoring baselines

Changing payment processes (instant payouts, push-to-card, card loading, crypto withdrawals, removing holds) Irreversible exits; rail arbitrage; shorter detection windows Real-time screening; holds for reversible funding; velocity limits; pre-release fraud scoring

New distribution channels (embedded-finance partners, agents, affiliates, white-label, API access) Less visibility of end customers; nested customers; partner misconduct; marketing that misrepresents Partner due diligence; contract flow-down; data feeds; partner-level monitoring; marketing approval

A one-page product risk summary

Many firms record the assessment on a short template that the approval committee can read in minutes:

  • Field Example entry
  • Feature Instant payouts to debit cards in 5 countries
  • Who can use it Verified customers with 30 days' tenure
  • Key risks Fraud cash-out; mule networks; sanctions corridors
  • Controls Screening before release; velocity limit; 24-hour hold after card loads; payout-partner due diligence
  • Data for monitoring Card BIN country, payout amount, device ID
  • Residual risk vs appetite Medium, within appetite after controls
  • Launch conditions 10,000-customer pilot; daily cap per user
  • Review dates 30, 90 and 180 days

The template makes approvals consistent and gives auditors a clear trail from risk to control.

Questions that uncover hidden risk

Who could abuse this feature, and how? Think about mules, scam victims, fraudsters and sanctions evaders.

Does it allow value to leave faster, further or more anonymously than before?

Does it allow third parties to fund or receive?

Will monitoring see the transaction, and with what data?

What happens if a control fails at three in the morning on a public holiday?

Does any marketing language promise something the controls will block?

Realistic exam scenario

A neobank plans to add instant international payouts to 20 countries in eight weeks. The product team has already built the feature. Compliance is asked to "approve by Friday". The right response is to run the product risk assessment now. That covers corridor ratings, screening against all applicable lists, Travel Rule and partner requirements, licensing in the payout countries, monitoring ingestion and new scenarios, and limits. Then propose a phased launch, perhaps to five lower-risk corridors with value caps, while the remaining controls are completed. Approval without assessment, or a flat refusal, are both poor answers. The risk-based answer is a controlled launch.

Common exam traps

Involving compliance only at the end of development.

Assuming existing controls automatically cover a new feature.

Skipping the post-launch review.

Forgetting partner-bank approval and licensing checks.