Study guide

12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation

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

12.1 Common Payment Methods, Crypto, and High-Risk Transactions Such as Aggregation

Key Takeaways Explain This Topic AI

The FedNow Service launched in July 2023, joining the RTP network (2017) and the UK Faster Payments Service (2008) as real-time payment rails.

Wire transfers carry originator and beneficiary information under Travel Rule requirements, while many card and batch payments carry only limited counterparty data.

Aggregation, where one account or merchant ID carries many underlying payers or payees, hides the real originators and beneficiaries from the bank and monitoring tools.

Crypto payments settle on public ledgers, are pseudonymous and are generally irreversible, so screening must happen before funds leave the platform.

Last updated: October 2026

CAFCA sub-topic 3.4 asks you to know the common payment transaction methods , including cryptocurrency and other high-risk transactions such as aggregation . Monitoring and screening only work if you understand how money moves on each rail. That means knowing how fast it is, whether it can be reversed, and what data comes with it.

The main rails

Method How it works Speed and finality Data that travels with it Typical abuse

Card payments Four-party model: cardholder, issuer, network, acquirer and merchant Fast authorisation; settlement later; chargebacks possible Merchant name, merchant category code, card data Card testing, transaction laundering, stolen-card funding

Push-to-card payouts Funds are sent to a debit card through network push services Near real time Limited Rapid cash-out of fraud proceeds

ACH and other batch rails US ACH under Nacha rules (Same Day ACH added in 2016); UK Bacs; SEPA credit transfers and direct debits Same day to a few days; returns and reversals possible Limited originator and beneficiary fields Unauthorised debits, account takeover funding, mule pass-through

Wires Fedwire Funds Service (real-time gross settlement), CHIPS; SWIFT messaging for cross-border correspondent payments Same day; final Rich: originator and beneficiary under Travel Rule requirements Trade-based laundering, sanctions evasion through correspondents

Instant payments RTP (2017) and FedNow (July 2023) in the US; Faster Payments (2008) in the UK; SEPA Instant (2017); Pix in Brazil (2020); UPI in India (2016) Seconds, around the clock; final ISO 20022 data is often richer than legacy batch formats Authorised push payment scams; mule networks; rapid layering

Wallets and P2P Transfers between accounts on the same platform, or across apps Instant inside the platform Platform-specific; the counterparty may be another app Funnel accounts, multi-app hopping, scam payments

E-money and prepaid Stored value issued against funds received; open-loop cards or closed-loop gift cards Instant use Often light at load Anonymous or low-KYC loads, gift-card cash-out

Cash networks Retail reload points, ATMs, agents Instant credit Little or no customer data at the till Structuring and placement of street cash

Cheques and remote deposit capture Image deposit with delayed clearing Days; can be returned Payer data on the item Altered, counterfeit or duplicate cheques

Crypto On-chain transfers of crypto-assets and stablecoins Minutes; irreversible on-chain Public addresses only; identity needs VASP data and Travel Rule messages Ransomware, scam proceeds, sanctions evasion, mixers

Why rail knowledge matters for monitoring

Data richness drives detection. Monitoring can only use the fields it receives. A wire with full originator data allows counterparty screening. A batch credit with a vague description may not.

Speed drives control design. On instant rails, screening and fraud checks must run before release (Chapter 10). Batch rails leave time to review.

Finality drives loss. Funds that leave over final rails, such as instant payments, wires and crypto, are hard to recover. Reversible funding methods create return and chargeback risk (next section).

High-risk transactions: aggregation and nesting

Aggregation means one account, merchant ID or wallet carries the payments of many underlying parties. Common forms in FinTech:

Payment aggregators and payment facilitators , where many sub-merchants process under one master merchant account.

Collection or for-benefit-of accounts that pool customer funds before distribution.

Virtual account numbers that route many end-customers' payments into one master account.

Nested payment providers , where another PSP or MSB uses the FinTech's account to serve its own customers.

Why aggregation is high-risk:

Originators and beneficiaries disappear. The bank sees "Aggregator Ltd" rather than the 3,000 people behind it.

Monitoring loses context. A spike may be one bad sub-merchant hidden among good ones.

Responsibility can blur unless contracts and data flows make clear who does CDD on whom.

Controls include full due diligence on each sub-merchant or end customer by the party responsible, transaction-level data (not net settlement files), sub-merchant-level monitoring, contractual bans on unapproved nesting, and periodic audits (Chapters 2 and 17).

Other high-risk transaction types

Cross-border payouts to high-risk jurisdictions or through many intermediaries.

Cash loading and ATM withdrawals that bracket electronic movement.

Prepaid and gift cards bought in volume or with stolen credentials.

Crypto on- and off-ramps , especially to unhosted wallets or to high-risk exchanges.

Third-party funding , where a payment comes from an account in someone else's name.

Realistic exam scenario

A FinTech gives a corporate customer, which describes itself as a "travel booking platform", 500 virtual account numbers. Funds from thousands of payers arrive and are settled out daily to accounts in several countries. The bank partner sees only one account name. This is aggregation, and possibly nested payment services. The FinTech must confirm whether the customer is licensed to provide payment services. It must obtain sub-account-level data, apply CDD to the payers and payees as the contract requires, monitor at the virtual-account level, and get the bank's approval for the structure. Without these controls the structure could hide unlicensed money transmission.

Common exam traps

Treating all "instant" payments as low-value retail. Instant rails carry large business payments too.

Assuming crypto is untraceable. It is pseudonymous; analytics and VASP data can attribute flows (Chapter 13).

Ignoring the hidden parties behind aggregated accounts.