Study guide

6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking

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

6.2 How Banks Risk-Rate FinTechs: Onboarding, Ongoing Oversight, and De-Risking

Key Takeaways Explain This Topic AI

Banks often assess a FinTech in three ways at once: as a high-risk customer type, as a third party under risk management guidance, and as a nested or correspondent-like channel.

Wolfsberg Group questionnaires such as the CBDDQ and FCCQ are common tools banks use to collect a FinTech's financial crime programme information.

The US Treasury's April 2023 De-risking Strategy, required by AMLA section 6215, highlighted MSBs, non-profits and small correspondent relationships as most affected.

In September 2026, the US banking agencies and the NCUA proposed new third-party risk guidance to replace the 2023 interagency guidance, which remains in effect until finalised.

Last updated: October 2026

CAFCA sub-topic 1.8 asks how FinTechs are risk-categorised by more traditional institutions and how to maintain those relationships through onboarding, ongoing review and the threat of de-risking . Almost every FinTech depends on banks for accounts, card issuing, settlement or sponsorship. Losing a bank can stop the business overnight.

Three lenses banks use

Lens Why the bank uses it What it drives

High-risk customer type MSBs, payment service providers, VASPs and third-party payment processors appear as higher-risk business types in supervisory manuals Enhanced due diligence on the FinTech's licences, ownership, management, AML programme and expected activity

Critical third party In BaaS and program-manager models, the FinTech performs bank functions such as onboarding, servicing and first-line monitoring Full third-party lifecycle management under bank guidance: planning, due diligence, contracting, ongoing monitoring and termination

Nested or correspondent-like channel The FinTech's own customers' payments flow through the bank, often in aggregated form Questions about the end-customer base, nested providers, visibility of originators and beneficiaries, and data feeds

The US interagency third-party guidance of June 2023 still applies. In September 2026 the OCC, Federal Reserve, FDIC and NCUA proposed replacement guidance, with comments due in November 2026. Banks therefore expect FinTech partners to work within a lifecycle approach, whatever the final text.

Factors that move a FinTech's risk rating

Licensing and regulatory status : licensed, registered, relying on an exemption, or in a sandbox.

Business model and products : cross-border payouts, cash loading, crypto, high-risk merchants, lending.

Customer base : consumers or businesses, geographies, non-residents, PEP exposure, high-risk industries.

Programme maturity : policies, MLRO capability, screening and monitoring tools, QA, independent testing, audit findings.

Growth and scale : rapid growth without matching compliance staffing is a well-known red flag in enforcement actions.

Ownership and funding : opaque investors, sanctions exposure, financial stability.

History : enforcement, complaints, chargeback or fraud ratios, previous bank exits.

Data and transparency : will the bank see raw transaction and customer data?

Nesting : does the FinTech serve other payment firms, which creates a further layer of customers?

Onboarding with a bank

Expect the bank to send a due diligence questionnaire. Many banks use or adapt the Wolfsberg Group Correspondent Banking Due Diligence Questionnaire (CBDDQ) or Financial Crime Compliance Questionnaire (FCCQ). The bank will also review policies, test sample files, interview management, examine independent audit or SOC reports, and agree contractual controls. A FinTech that prepares a data room in advance gets through onboarding faster: licences, policies, risk assessment, the last independent test, MI samples, organisation chart, and screening and monitoring tool details.

Ongoing oversight and keeping the relationship

What the bank needs What the FinTech should provide

Visibility Agreed MI: customer counts by risk rating, alert volumes and ageing, SAR referrals, fraud and chargeback rates, complaints

No surprises Advance notice of new products, countries, partners and vendors. Many contracts require prior approval

  • Responsiveness Fast, complete answers to requests for information about specific customers or payments
  • Evidence of control QA results, independent testing, remediation tracking, model validation for scoring tools

Shared escalation Named contacts, joint incident procedures, agreed timelines for suspicious activity referrals

Relationship failures usually start with information asymmetry . The bank learns about a risk from an examiner or the media before it hears from its partner.

De-risking

De-risking is the wholesale ending or restriction of relationships with whole categories of customers to avoid risk instead of managing it case by case. FATF has warned that de-risking can push activity into less transparent channels and harm financial inclusion. The US Treasury's 2023 De-risking Strategy , published in April 2023 under section 6215 of the AML Act of 2020, found that small MSBs, non-profits working in high-risk regions, and foreign banks with low correspondent volumes were the most affected. In August 2025 a US executive order directed regulators to address politicised or unlawful debanking.

Supervisors expect risk-based decisions about individual relationships. They do not expect zero tolerance by category. A bank can still exit a FinTech whose risk it cannot manage. FinTechs reduce that risk by showing controls that work, keeping honest MI, and fixing issues quickly.

Realistic exam scenario

A partner bank's annual review notes that the FinTech's cross-border payouts doubled without notice. Its alert backlog is 45 days, and two new payout corridors were added without approval. The bank warns that it may restrict the programme. The FinTech's best response is to acknowledge the gaps and provide accurate data. It should pause new corridors pending approval, present a resourced backlog plan with milestones, and agree enhanced MI and an independent review. Disputing the findings or delaying the data increases the chance of exit.

Common exam traps

"Being a bank's customer means the bank does our compliance." The FinTech still runs its own obligations and any delegated controls.

Launching features first and telling the bank later.

Treating de-risking as required by regulators. Supervisors expect relationship-level risk management, not blanket exits.