Study guide
17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms
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
17.4 How Banking Partners' Terms of Service Relate to the FinTech's Own Terms
Key Takeaways Explain This Topic AI
BaaS customers are usually bound by both the partner bank's deposit or cardholder agreement and the FinTech's own terms of service, which must not contradict each other.
The bank's prohibited-activity list, rights to request information, and rights to restrict, freeze or close accounts need to appear in the FinTech's customer terms.
Under the FDIC's deposit insurance advertising rule (12 CFR Part 328), non-banks must not misrepresent deposit insurance and should name the insured bank holding the funds.
Changes to customer-facing terms or marketing in a BaaS programme normally need the partner bank's prior review and approval under the programme agreement.
Last updated: October 2026
CAFCA sub-topic 4.8 asks how banking partners' terms of service relate to the FinTech's terms . This matters in investigations and offboarding. The FinTech can restrict, question or exit a customer only if the documents the customer agreed to give it that right, and those rights must match what the bank requires.
The document stack
Document Between Typical content
Programme agreement Bank and FinTech Roles and responsibilities; compliance obligations; approvals; audit rights; data access; termination
Deposit account or cardholder agreement Bank and end customer The legal account relationship; the bank's rights and the customer's rights
- FinTech terms of service FinTech and end customer App use, fees, features, acceptable use, communications
- Privacy notices Bank and customer; FinTech and customer What data is collected, shared and kept
- Marketing and disclosures FinTech to the public Product claims; deposit-insurance statements; naming the bank
The FinTech's terms usually incorporate or link the bank's agreement. Where the two conflict, the programme agreement normally requires the FinTech to fix its terms. The bank, as the regulated entity, cannot accept customer terms that undermine its controls.
Clauses that must line up for AML purposes
Clause area What the bank needs How the FinTech terms reflect it
Prohibited activities Lists of restricted or prohibited uses (for example gambling, unlicensed money transmission, certain crypto activity, business use of consumer accounts) Same restrictions in the acceptable-use section; clear consequences
Information requests The right to request information and documents about the customer and their transactions Customer agrees to provide information when asked, within stated periods
Restriction, freezing and closure Rights to hold, reject or reverse transactions, freeze funds and close accounts, including without notice where the law allows Matching rights in the FinTech terms, with consistent notice periods
Sanctions Prohibition on sanctioned persons and countries Representation and warranty from the customer; right to block
Data sharing Consent or a legal basis to share data between bank, FinTech and vendors Privacy notices and terms that explain the sharing
Deposit insurance No misrepresentation; name the bank; insurance covers only bank failure Accurate disclosures under 12 CFR Part 328 in the US
Disputes and errors Who handles disputes and error resolution under consumer law A clear process and the responsible party
- Programme termination A transition plan if the programme ends Notice of how funds will be returned or moved
- Why it matters in practice
Investigations : an RFI is easier to enforce, and refusal can lead to restriction, when the terms say the customer must provide information.
Holds and freezes : a FinTech that promises "instant withdrawals, always" cannot easily apply a fraud hold the bank requires. The marketing and the terms create conflicting expectations and complaint risk.
Exits : when the bank decides to exit a customer, the FinTech must carry out the exit consistently with both documents, without disclosing confidential reasons (Chapter 15).
Programme failure : the 2024 collapse of middleware provider Synapse showed what happens when customers do not understand which bank holds their money and how records are kept. Clear terms and disclosures reduce harm.
Who acts, and who tells the customer
When the bank and the FinTech share a customer, the agreement should settle three practical questions in advance:
Who decides to restrict or close? The bank usually keeps the final say over its own accounts, even where the FinTech recommends the action.
Who carries it out? The FinTech often applies holds in its app, while the bank applies them on its core system. Both must happen at once to avoid gaps.
Who communicates? Usually the FinTech, as the customer-facing brand, using wording the bank has approved. A message such as "Your bank closed this account" can mislead or invite questions that risk tipping off. Agreed neutral wording avoids both problems.
Document these points in the programme agreement and the operating procedures, and test them in incident simulations.
Change control
Most programme agreements require the bank's prior review and approval of changes to customer-facing terms, fee schedules, product features and marketing materials. A FinTech that changes its terms on its own, for example by allowing transfers to crypto exchanges that the bank prohibits, breaches the agreement and exposes both parties.
Realistic exam scenario
A FinTech's app terms say that customers may "send money anywhere in the world instantly". The bank's cardholder agreement prohibits transfers to certain jurisdictions and allows the bank to hold suspicious transfers. A customer complains that a held payment breaks the FinTech's promise. The FinTech should apply the hold, because the bank's agreement and the law allow it. It should then correct its terms and marketing with the bank's approval, so that the documents line up, and log the complaint. Releasing the payment to honour the inaccurate marketing would undermine the bank's controls.
Common exam traps
Assuming the FinTech's terms override the bank's agreement. The bank's controls must be preserved.
Changing terms or marketing without bank approval.
Marketing that implies the FinTech is a bank or is FDIC-insured.
Promising features, such as instant unconditional withdrawals, that conflict with required controls.