The Office of the Comptroller of the Currency (OCC) rejected Wise's application for a U.S. national trust bank charter due to deficiencies in its Anti-Money Laundering and Countering the Financing of Terrorism (AML/CFT) framework. This wasn't a close call. The OCC cited "significant supervisory and compliance concerns," indicating fundamental structural problems, not minor documentation gaps.
For AML/KYC teams at fintechs eyeing banking licenses, this outcome reveals a critical pattern: compliance standards that work under money transmitter licenses don't scale to federal banking charters. Here's why these applications fail and what you need to fix before you submit.
Why These Mistakes Keep Happening
The transition from payment provider to chartered bank isn't an upgrade; it's a category shift. Your current compliance program likely satisfies state money transmitter requirements across 48 jurisdictions. You've passed examinations and process millions of transactions. But federal banking regulators evaluate you against a different baseline: can you operate as a fiduciary institution under continuous OCC supervision?
Most fintech compliance teams underestimate this gap because they're measuring against the wrong benchmark. You're comparing your controls to other payment companies, while regulators compare you to community banks and trust companies with decades of federal examination history.
Mistake 1: Treating AML/CFT as a Technology Problem
Why it happens: Fintechs build sophisticated transaction monitoring systems with machine learning models, automated risk scoring, and real-time screening. Leadership assumes these tools demonstrate AML/CFT capability.
The consequence: Regulators don't assess your transaction monitoring platform in isolation. They evaluate whether your governance structure, escalation procedures, investigative capacity, and senior management oversight can sustain a federal AML/CFT program under Bank Secrecy Act (BSA) requirements. Wise's rejection highlighted concerns about whether proposed board and senior management possessed sufficient experience overseeing AML compliance in a banking context, not whether their technology worked.
The fix: Document your AML/CFT governance framework separately from your technology stack. Your application should demonstrate:
- Board-level AML/CFT oversight with members experienced in BSA compliance at federally regulated institutions
- A designated BSA Officer with direct reporting lines to the board, not buried under a Chief Compliance Officer who also handles licensing and regulatory relations
- Escalation procedures that specify when investigations move from analysts to senior management to the board
- Quality assurance testing protocols for Suspicious Activity Report (SAR) decisioning, not just system performance metrics
If your current BSA Officer has only worked at payment companies, you're signaling inexperience with federal banking examination standards.
Mistake 2: Submitting Applications That Describe Your Current State
Why it happens: Application teams compile evidence of existing controls, current staffing, and operational processes as they exist today. This feels logical, you're proving you already meet requirements.
The consequence: The OCC evaluates whether you can meet enhanced regulatory obligations under a federal charter, not whether you satisfy money transmitter standards. Wise noted that its application "reflected its business as it existed more than a year ago" and didn't account for subsequent compliance investments. This timing gap is common, but it reveals a structural problem: if your application describes controls you've since upgraded, you're implicitly admitting those controls were insufficient.
The fix: Your application should project forward, not backward. Document:
- The compliance program you'll operate under the charter, including staffing levels, reporting structures, and control testing frequencies that match federal banking expectations
- Planned enhancements with implementation timelines, not aspirational statements
- How your transaction monitoring thresholds, customer due diligence procedures, and sanctions screening protocols will change post-charter
If you've recently settled enforcement actions, Wise settled a $4.2 million action with six state regulators over AML deficiencies, your application must explicitly address how your remediated program differs from the one that generated violations.
Mistake 3: Underestimating the Governance Experience Gap
Why it happens: Fintech boards typically include payments experts, technology leaders, and investors with deep sector knowledge. These directors understand digital payments, cross-border flows, and platform economics.
The consequence: Federal banking regulators expect board members who've overseen fiduciary banking activities and AML compliance at institutions subject to OCC examination. The OCC specifically questioned whether Wise's proposed board possessed this experience. Payments expertise doesn't substitute for banking governance experience in a charter application.
The fix: Recruit board members or advisory directors with backgrounds including:
- Service on boards of OCC-supervised institutions (national banks or federal trust companies)
- Experience as BSA Officers or Chief Compliance Officers at federally chartered banks
- Participation in regulatory examinations, consent orders, or remediation programs at banking institutions
This isn't about credentials for appearance. These directors know how federal examiners evaluate board minutes, how to structure compliance committee charters, and what "adequate oversight" means in OCC examination reports. If your board lacks this experience, add it before you apply.
Mistake 4: Assuming Your Current Licenses Demonstrate Readiness
Why it happens: Operating under money transmitter licenses across 48 states and four territories, as Wise does, requires significant compliance infrastructure. Teams assume this multi-state licensing proves they can handle federal oversight.
The consequence: State money transmitter examination cycles, enforcement priorities, and compliance expectations differ fundamentally from OCC supervision. Federal banking charters impose continuous supervision, not periodic examinations. Your compliance program must function under the assumption that examiners have ongoing access to your systems, records, and decision-making processes.
The fix: Audit your current compliance program against OCC expectations, not state money transmitter requirements:
- Can your transaction monitoring system generate examination-ready documentation for every alert disposition decision, not just SAR filings?
- Do your customer due diligence procedures capture beneficial ownership information consistent with FinCEN's Customer Due Diligence Rule, or just the identity verification your state licenses require?
- Are your sanctions screening protocols structured to satisfy OFAC examination standards, including full audit trails and documented override procedures?
Map every control to the equivalent expectation in the FFIEC BSA/AML Examination Manual. Where gaps exist, close them before you apply.
Mistake 5: Treating the Application as a Compliance Exercise
Why it happens: Application teams frame charter applications as demonstrating compliance capability, proving you meet requirements.
The consequence: The OCC evaluates strategic fit, operational resilience, and supervisory risk, not just compliance checkboxes. Wise positioned its revised application around "interoperability between traditional payment rails and emerging digital asset infrastructure" following passage of the GENIUS Act. This framing connects compliance capability to strategic value within the evolving regulatory environment.
The fix: Your application should answer: why does a federal charter serve the public interest, and why are you the right organization to hold it? This requires:
- Demonstrating how your charter enhances financial system stability, expands access, or improves efficiency in ways your current licenses don't permit
- Showing how regulatory changes (like the GENIUS Act's framework for payment stablecoins) create supervisory clarity that didn't exist when similar applications were denied
- Explaining how your technology platform addresses specific gaps in the U.S. payments system that chartered institutions are positioned to fill
If your application reads like a compliance audit response, you're not making the strategic case for why the OCC should supervise your institution.
Prevention Checklist
Before you submit a national trust bank charter application:
- Board includes members with OCC-supervised institution governance experience
- BSA Officer has direct board reporting line and federal banking background
- Transaction monitoring documentation meets FFIEC examination standards, not just state requirements
- Customer due diligence procedures capture beneficial ownership per FinCEN CDD Rule
- Sanctions screening includes full audit trails and documented override procedures
- Application describes post-charter compliance program, not current state
- Recent enforcement actions are explicitly addressed with remediation evidence
- Strategic rationale connects charter to public interest and regulatory environment
- Governance structure demonstrates capacity for continuous federal supervision
- Compliance committee charter, meeting frequency, and escalation procedures match federal banking norms
The OCC made clear that Wise can reapply. That invitation isn't courtesy, it's an acknowledgment that the deficiencies are fixable. But fixing them requires recognizing that federal banking charters demand a different compliance architecture than the one that works under state money transmitter licenses. Your technology might be ready. The question is whether your governance, experience, and supervisory readiness match your platform's capabilities.
