Study guide
3.2 Licensing, Registration, Charters, and Regulatory Sandboxes
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
3.2 Licensing, Registration, Charters, and Regulatory Sandboxes
Key Takeaways Explain This Topic AI
FinTech regulation is activity-based: the services performed, not the brand or technology, determine the licence and the AML duties.
In the United States, money transmitters register with FinCEN as MSBs and also need state licences, while banks hold federal or state charters.
EU and UK e-money and payment institutions are licensed separately from banks and must safeguard customer funds instead of lending them.
The UK FCA and MAS launched regulatory sandboxes in 2016; a sandbox relaxes some rules under conditions but does not suspend AML/CFT obligations.
Last updated: October 2026
CAFCA sub-topic 1.3 asks you to explain the regulatory principles that apply to different FinTech business models: registration, licensing and banking charters . It also asks how AML requirements differ between models and why sandboxes exist. Exam questions usually describe a product and ask which permission or obligation applies, or whether a proposed shortcut is lawful.
Principle 1: regulation follows the activity
Regulators look at what the firm actually does. Holding deposits, moving money for others, issuing stored value, safekeeping or exchanging crypto-assets, lending, and arranging investments are each regulated activities. A firm can perform several activities at once. Marketing labels such as "we are just software", "decentralised" or "a platform" do not change the analysis.
Main routes to market
Model United States EU / UK AML/CFT obligations come from
Own banking licence National charter (OCC) or state charter, with FDIC insurance and a Federal Reserve or state supervisor Credit institution authorisation (in the UK, PRA and FCA) Full bank AML programme: CIP, CDD and beneficial ownership, SARs, sanctions
Partner-bank (BaaS) model No licence for the FinTech's banking products; the partner bank holds the charter Agent or distributor arrangements with a licensed institution Mostly the partner's programme, delegated by contract (Chapters 2 and 17)
Money transmission / payments FinCEN MSB registration plus state money transmitter licences Payment institution (EU PSD2; UK Payment Services Regulations 2017) Firm's own AML programme as an MSB or obliged entity
E-money Usually money transmission or prepaid access under state law E-money institution (EU EMD2; UK Electronic Money Regulations 2011) Firm's own programme, plus safeguarding of customer funds
Crypto-assets MSB registration, state licences (for example the New York BitLicense or a limited purpose trust charter) MiCA CASP authorisation (EU); FCA AML registration for cryptoasset firms (UK) Firm's own programme, including the Travel Rule
Lending / BNPL State lending licences or partner-bank origination Consumer credit authorisation Varies; partner banks often impose their programme
Three exam points follow from this table:
Registration is not licensing. FinCEN MSB registration is a federal registration. It is not a licence and it does not replace state licences. In the US, nearly every state licenses money transmitters, and the CSBS Money Transmission Modernization Act model law (2021) is gradually standardising those rules.
E-money and payment institutions are not banks. They cannot take deposits or lend out customer balances. They must safeguard customer funds, usually in segregated accounts or with an insurance or guarantee arrangement. That is why "your money is FDIC/FSCS protected" claims from non-banks are a classic misrepresentation risk.
AML requirements differ by model. In the US, the CDD Rule's beneficial ownership requirements apply to banks, broker-dealers, mutual funds and futures firms. MSBs instead have their own AML programme rule (31 CFR 1022.210). Payment processors that meet FinCEN's exemption are not money transmitters at all. In the EU and UK, almost every licensed FinTech is an obliged entity under the same AML rules.
Passporting and cross-border reach
Within the EU, an authorised payment institution, e-money institution or CASP can passport its licence to other member states. A UK firm lost EU passporting rights after Brexit and needs local authorisation. Supervisors still expect AML controls that reflect each host country's risks, so passporting a licence does not passport a risk assessment.
Regulatory sandboxes and innovation hubs
A regulatory sandbox lets a firm test an innovative product with real customers, under close supervisory oversight, within agreed limits. The UK FCA launched the first widely copied sandbox in 2016, and the Monetary Authority of Singapore launched its FinTech Regulatory Sandbox the same year. The Global Financial Innovation Network (GFIN), set up in 2019, coordinates cross-border testing between regulators.
What a sandbox does and does not do:
A sandbox can A sandbox cannot
Provide restricted or tailored authorisation for a limited test Waive anti-money laundering, sanctions or counter-terrorist financing laws
Cap customer numbers, transaction values or duration Permit anonymous accounts or skipping customer identification
Give informal steers and regulatory feedback Guarantee a full licence after the test
Require consumer disclosures, redress and an exit plan Protect the firm from enforcement for breaches during the test
Regulators set eligibility criteria such as genuine innovation, consumer benefit, a real need to test, and readiness to test. They require a test plan with safeguards and a transition or exit strategy. An innovation hub gives informal guidance without live testing. For CAFCA, the key message is that financial crime rules continue to apply inside a sandbox. Supervisors often look more closely at onboarding and monitoring during a test because the product is new.
Realistic exam scenario
A UK start-up plans an e-money wallet with instant international payouts. The founders propose applying to the sandbox so that they can "launch without KYC for the first 5,000 users and add checks later." The compliance lead should explain that a sandbox could restrict scale or provide tailored authorisation, but cannot remove customer due diligence, sanctions screening or reporting duties. The test plan must include CDD, monitoring and a suspicious activity reporting process from day one.
Common exam traps
"FinCEN registration is enough to operate nationwide." State licensing is separate.
"Sandbox participants are exempt from AML." They are not.
"An EMI can lend customer balances like a bank." It must safeguard them.
"The partner bank model means the FinTech has no AML role." The FinTech performs delegated controls under contract, and the bank remains accountable.