GLBA and money transmitter testing requirements
GLBA sets US federal rules for how financial institutions protect and share consumer financial information, and state money transmission laws license companies that move customer funds. Testing verifies access controls, encryption, privacy notice and opt-out flows, receipts, refunds, and obligation reports. FintechAssuranceLabs delivers partner bank due diligence test evidence packs and programme control and limit checks.
- Jurisdiction
- US federal (GLBA Safeguards Rule 16 CFR Part 314, Regulation P 12 CFR Part 1016) and US states (money transmission laws, many based on the CSBS Money Transmission Modernization Act)
- Primary source
- ecfr.gov
Engineering interpretation of testing requirements, not compliance advice.
What GLBA and state money transmission laws require
GLBA Safeguards Rule. For nonbank financial institutions, the FTC implements Title V of the Gramm-Leach-Bliley Act (GLBA) in 16 CFR Part 314 (checked on 2026-09-16, eCFR current to 2026-09-14). Section 314.1(b) names check cashers, wire transferors, and payday lenders among covered entities; institutions under another regulator's GLBA section 505 authority, such as banks, are outside Part 314. Section 314.4 lists the elements of the written information security program:
- 314.4(a) and (b). A Qualified Individual (the person who oversees the program) and a written risk assessment.
- 314.4(c)(1). Access controls that limit authorized users to the customer information they need, and customers to their own information.
- 314.4(c)(3). Encryption of customer information at rest and in transit over external networks; where encryption is infeasible, compensating controls the Qualified Individual reviews and approves.
- 314.4(c)(5). Multi-factor authentication for any individual accessing any information system, unless the Qualified Individual approves an equivalent control in writing.
- 314.4(c)(6) to (c)(8). Disposal no later than two years after last use, with listed exceptions, change management, and logging of authorized users' activity.
- 314.4(d)(2). Without effective continuous monitoring, annual penetration testing and vulnerability assessments at least every six months and after material changes.
- 314.4(h) to (j). A written incident response plan, an annual written report to the board, and notice to the FTC within 30 days of discovering a notification event that involves at least 500 consumers (effective 13 May 2024, Section 314.5).
Section 314.6 exempts institutions with customer information on fewer than 5,000 consumers from 314.4(b)(1), (d)(2), (h), and (i).
Regulation P. The CFPB privacy rule, 12 CFR Part 1016 (checked on 2026-09-16), covers individuals who obtain products for personal, family, or household purposes (1016.1(b)(1)). Section 1016.4(a)(1) requires an initial privacy notice no later than the start of the customer relationship, and 1016.5(a) an annual notice unless the 1016.5(e) exception applies. Section 1016.10(a) forbids disclosure to a nonaffiliated third party before an initial notice, an opt-out notice, and a reasonable opportunity to opt out. Section 1016.12(a) forbids disclosing account data such as a deposit or credit card account number to a nonaffiliated third party for marketing.
State money transmission laws. States license money transmitters under their own statutes. The Conference of State Bank Supervisors (CSBS) publishes the Money Transmission Modernization Act model law (MTMA, checked on 2026-09-16), which states enact in full, in part, or not at all. In the model text:
- Section 2.01(q) defines money transmission as selling or issuing payment instruments or stored value, or receiving money for transmission, including payroll processing services.
- Sections 7.01 and 7.06 require a report of condition within 45 days of quarter end, with a permissible investments report, and records for at least [three] years, including bank reconciliation records.
- Sections 9.02 and 9.03 require a refund within 10 days of a written request unless a listed exception applies, and a receipt with listed fields. Both exclude transfers under the federal Remittance Rule.
- Section 10.01 sets tangible net worth at the greater of $100,000 or 3 percent of the first $100 million of total assets plus lower rates above it. Section 10.02 sets a surety bond of the greater of [$100,000] or average daily money transmission liability in the state, up to [$500,000].
- Section 10.03(a) requires permissible investments of not less than all outstanding money transmission obligations at all times.
Bracketed values vary by state; commentary to Section 10.02 notes states with a bond maximum above $500,000. The enacted state statute is the test oracle. The Nationwide Multistate Licensing System (NMLS) receives the quarterly MSB Call Report (checked on 2026-09-16).
What GLBA and money transmitter testing verifies
MTMA rows apply where a state enacted the cited section.
| Requirement | What we test | Evidence produced |
|---|---|---|
| 16 CFR 314.4(c)(5): multi-factor authentication for any individual accessing an information system | Customer app, admin console, and support tool logins with a password only and with a replayed one-time code | Authentication test log per interface and factor |
| 16 CFR 314.4(c)(1)(ii): customers access only their own information | Account, transfer, and statement requests that carry another customer's resource ID | Access control test matrix per role and resource type |
| 16 CFR 314.4(c)(3): customer information encrypted at rest and in transit over external networks | TLS settings on public endpoints, and encryption of customer information stores in production and test environments | TLS scan output and storage encryption configuration record |
| 16 CFR 314.4(d)(2): annual penetration testing and vulnerability assessments at least every six months, absent continuous monitoring | Web, API, and mobile interfaces that handle customer information, scoped from the written risk assessment | Penetration test report with findings, severity, and retest results |
| 12 CFR 1016.4(a)(1): initial privacy notice no later than the start of the customer relationship | Onboarding paths, including deep links and resumed sessions, that reach account funding without the privacy notice acknowledgement | Onboarding step log with notice version and acknowledgement timestamp |
| 12 CFR 1016.10(a): no disclosure to a nonaffiliated third party before the opt-out opportunity or after an opt-out | Partner data exports for consumers inside the opt-out period and for consumers who opted out | Partner export comparison per consumer opt-out status |
| MTMA Section 9.03(c): receipt with sender, recipient, date, transaction number, licensee name, NMLS Unique ID, USD amount, fee, and taxes | In-app, email, and in-person receipts for consumer transfers outside the federal Remittance Rule | Receipt field checklist per channel and language |
| MTMA Section 9.02(b): refund within 10 days of a written refund request unless a listed exception applies | Refund requests for pending, forwarded, held-for-fraud-review, and unidentifiable transfers | Refund timing log per transfer state |
| MTMA Section 10.03(a): permissible investments not less than all outstanding money transmission obligations | Outstanding obligation totals from the ledger for pending, returned, refunded, and escheated transfers | Reconciliation of ledger obligations with the permissible investments report |
Artifacts state examiners and partner banks request
- The written information security program and risk assessment (16 CFR 314.4(b)(1)).
- The annual penetration test report and the vulnerability assessment results for each six-month period (314.4(d)(2)).
- Qualified Individual approvals of controls used instead of encryption (314.4(c)(3)) or multi-factor authentication (314.4(c)(5)).
- The written incident response plan (314.4(h)) and the annual report to the board, which covers testing results (314.4(i)(2)).
- Service provider contracts and periodic service provider assessments (314.4(f)).
- Privacy notice versions with delivery records, and opt-out records (12 CFR 1016.4, 1016.5, and 1016.10).
- MSB Call Report filings in NMLS, and audited financial statements within 90 days after fiscal year end (MTMA Sections 7.01 and 7.02).
- The monthly general ledger, bank reconciliation records, and records of outstanding money transmission obligations (MTMA Section 7.06).
- Quarterly authorized delegate reports within 45 days of quarter end (MTMA Section 7.03).
Common findings against GLBA and money transmission rules
- Support console without a second factor. Support agents open customer records with a password only, and no written approval of an equivalent control exists. The defect breaks 16 CFR 314.4(c)(5).
- Transfer details for another customer. A transfer detail endpoint returns another customer's recipient bank account number when the transfer ID in the request changes. The defect breaks 16 CFR 314.4(c)(1)(ii).
- Production records in an unencrypted test database. A staging database holds a copy of production customer records on unencrypted storage. The defect breaks 16 CFR 314.4(c)(3).
- No assessment after a new API. A new mobile API that adds a money movement flow, with no continuous monitoring in place, gets no vulnerability assessment until the next six-month cycle. The defect breaks the material change trigger in 16 CFR 314.4(d)(2)(ii).
- Privacy notice skipped on a deep link. A referral deep link opens the funding screen before the privacy notice acknowledgement step. The defect breaks 12 CFR 1016.4(a)(1).
- Opt-out not applied to a partner export. The nightly marketing partner export reads a cached audience list, so a consumer who opted out two weeks earlier is still disclosed. The defect breaks 12 CFR 1016.10(a)(1)(iv).
- Receipt without licensee identifiers. An in-app receipt for a domestic transfer omits the NMLS Unique ID and the fee line. The defect breaks MTMA Section 9.03(c)(1) as enacted in the state.
- Returned transfers missing from obligations. Transfers in a "returned, awaiting refund" state drop out of the outstanding obligations query, so the permissible investments report shows coverage the licensee does not have. The defect breaks MTMA Section 10.03(a) as enacted in the state and misstates the report of condition under Section 7.01(b)(3).
How we cover GLBA and money transmitter requirements
BaaS and partner bank integration testing produces the partner bank due diligence test evidence pack, programme control and limit checks, and the webhook delivery, ordering, and retry test report. Lending and credit decisioning testing covers consumer lending flows where Regulation P notices and opt-outs apply.
We test GLBA and state money transmission requirements for international transfer products, neobanks, crypto exchanges, earned wage access, and payroll platforms, where the model definition includes payroll processing services. Consumer transfers under the federal Remittance Rule are on the Regulation E page. SOC 2 test scope is on the SOC 2 page.
Related
Segments
- International transfers
- Neobanks and digital banking
- Crypto exchanges and wallets
- Earned wage access
- Family and youth banking
- Consumer lending and credit marketplaces
- Buy now pay later
- Payroll and global hiring
- AP/AR automation and treasury
- Banking-as-a-Service and card issuing
- Payment acquiring
- Debt collection and loan management software
- Open banking and data aggregation
- POS and merchant services
- Tax software
Adjacent standards
Questions
Does GLBA require penetration testing?
What is GLBA?
What is a money transmitter license?
Who needs a money transmitter license?
Scope your testing
Send FintechAssuranceLabs your product, segment, money flows, and the standards that need evidence, and get a proposed test scope with its deliverables.
Scope your testing