Skip to main content

Lesson 04 of 15

Building a FinTech AML Program: The Pillars

5 min read · AML·FT

Internal controls, a designated BSA officer, training, independent testing, and risk-based CDD — the pillars are universal, but applying them at fintech speed is the challenge. Learn where each pillar breaks and how a current risk assessment ties them together.

The pillars: your program skeleton

  • Every BSA program is built on the same pillars
  • MSB program rule: 31 CFR 1022.210; banks: 1020.210
  • Pillars are universal; the fintech twist is in how you apply them

Every BSA/AML program, at a bank or a money services business, is built on the same skeleton: the pillars. For an MSB, the requirement to have a written, risk-based AML program sits at thirty-one C-F-R ten-twenty-two point two-ten; for banks it's at ten-twenty point two-ten. The pillars themselves are the same well-worn list, and the exam-style point is that they're universal.

What's different in fintech isn't the list, it's how each pillar gets applied to a fast, digital, partner-dependent business. So let's walk the pillars, and at each one, name where fintechs stumble.

Pillar 1 and 2: controls and a BSA officer

  • A system of internal controls — written, risk-based, board-approved
  • A designated BSA/AML compliance officer with authority and resources
  • FinTech trap: a junior 'compliance person' with no authority
  • The officer must be empowered to halt a product

The first pillar is a system of internal controls: written policies and procedures, risk-based, approved by the board or equivalent governance, that actually govern how you onboard, monitor, and report. The fintech trap here is the document that exists but doesn't match the product, written once for a funding deck and never updated as five new features shipped. The second pillar is a designated BSA/AML compliance officer, a real, named person with the authority, seniority, and resources to run the program.

In fintech the classic failure is a single overloaded 'compliance person,' junior and under-resourced, who can flag a problem but can't stop a launch. The officer has to be empowered to say no, to slow a product down, to escalate to the board. If your compliance lead can't halt a risky feature, you don't really have this pillar.

Pillar 3 and 4: training and independent testing

  • Ongoing AML training, role-tailored, documented
  • Independent testing — audit by someone not running the program
  • FinTech trap: engineers make compliance decisions untrained
  • Independent test can be internal audit or a qualified outside firm

The third pillar is ongoing training: appropriate, role-tailored, and documented. In fintech this has to reach further than the compliance team, because product managers and engineers make compliance-relevant decisions all the time, in onboarding flows, in monitoring rules, in how data is stored. If the people building your money features have never been trained on what a Customer Identification Program requires or what triggers a suspicious activity report, your training pillar has a hole in it.

The fourth pillar is independent testing: a periodic, objective audit of the program by someone not responsible for running it, internal audit or a qualified outside firm. The independence is the point, the same principle behind any third line of defense. A fintech that has its own compliance team 'review their own work' has testing, but not independent testing, and an examiner will notice the difference.

Pillar 5: risk-based CDD and beneficial ownership

  • The 'fifth pillar': risk-based CDD + beneficial ownership
  • Source: the CDD Rule, 31 CFR 1010.230
  • Know your customer, risk-rate them, monitor on a risk basis
  • For legal-entity customers: collect beneficial owners

The fifth pillar, added by FinCEN's Customer Due Diligence Rule, is risk-based customer due diligence, including identifying the beneficial owners of legal-entity customers. The rule lives at thirty-one C-F-R ten-ten point two-thirty. In substance it means you have to understand who your customer is, develop a risk profile for them, monitor their activity against that profile on a risk basis, and, when the customer is a company, collect the humans who own or control it.

We'll spend a full lecture on CDD and beneficial ownership later, so here just slot it into the skeleton: it's a formal program pillar, not an optional nicety. Fintechs that built slick consumer onboarding sometimes forget that their business customers trigger a whole separate beneficial-ownership obligation.

Making the program risk-based and real

  • Start from a written enterprise AML risk assessment
  • Tie controls to the risks your specific product creates
  • Keep it current as products and volumes change
  • FFIEC manual is the examiner's yardstick — read it

The thread tying all the pillars together is that the program must be risk-based, and that starts with a written enterprise-wide AML risk assessment: an honest inventory of the money-laundering and sanctions risks your specific products, customers, geographies, and channels create. Your controls should then map to those risks, more control where risk is higher, less where it's lower. The fintech-specific discipline is keeping this current.

Fintechs change fast: a new payout corridor, a crypto on-ramp, a small-business product, each of those changes your risk and should update your assessment and your controls. The FFIEC BSA/AML Examination Manual is the examiner's yardstick for all of this; it's public, and reading it is the cheapest way to see your program through their eyes. A program that can't show a current risk assessment driving its controls looks, to an examiner, like a program that was copied, not built.

Recap and self-check

  • Pillars: controls, BSA officer, training, independent testing, CDD/BO
  • Universal list; fintech challenge is real application at speed
  • Risk assessment drives the whole thing; keep it current
  • Empowered officer + independent test are common weak spots

Let's recap. A fintech AML program rests on the same pillars as any BSA program: a system of internal controls, a designated and empowered BSA/AML officer, ongoing training, independent testing, and risk-based customer due diligence with beneficial ownership, all driven by a current, written risk assessment. The list is universal; the fintech challenge is applying it for real, at speed, across a partner stack.

Self-check: name your five pillars and, for each, point to the document and the person behind it. If your BSA officer can't stop a launch, or your 'independent' test is run by the people who built the program, you've found the weak pillar. Next, we zoom into the first place the program meets the customer: digital onboarding and your Customer Identification Program.

Sources

  • Bank Secrecy Act program requirements / 31 CFR Chapter X
  • FinCEN MSB AML program rule, 31 CFR 1022.210
  • CDD Rule, 31 CFR 1010.230
  • FFIEC BSA/AML Examination Manual

Test your knowledge

A few AML·FT questions on this material — pick an answer to see the explanation.

  1. Q1. After an MSB fintech files a SAR on a customer, the customer's relationship manager wants to warn the customer to 'clean up' their activity. Why is this prohibited?

  2. Q2. A common enforcement pattern against fast-growing fintechs involves a BSA/AML program that did not scale with the business. Which deficiency best fits this pattern?

  3. Q3. When a fintech relies on a sponsor bank under a banking-as-a-service (BaaS) arrangement, how should it view its own BSA/AML responsibilities?

  4. Q4. A company issues prepaid debit cards reloadable with cash at retail locations nationwide. Under FinCEN's MSB definition, which category is most likely to apply?

Ready to practice?

Put this lesson to work on real AML·FT questions.

Drill the full AML·FT bank →