Feature Regulatory Compliance
The Fed's Payment Account Proposal: What Fintechs and Digital Asset Firms Need to Know Before the July 27 Comment Deadline
The Federal Reserve proposed a special-purpose Payment Account in May 2026, offering eligible fintechs direct access to Fedwire Funds and FedNow without a bank charter. The comment period closes July 27. Here's who qualifies, what compliance the Fed requires, and why your institution should care even if you're not applying yet.
Table of Contents
The Federal Reserve doesn’t change its mind often. When it does, it tends to move slowly and in response to something that already happened. The Payment Account proposal is neither: it’s proactive, structurally significant, and the comment period closes July 27 — 19 days from today. Most compliance teams at eligible fintechs haven’t finished reading it yet.
TL;DR
- The Fed proposed a special-purpose “Payment Account” on May 20, 2026, giving eligible fintechs and digital asset firms direct access to Fedwire Funds and FedNow without a full master account or bank charter
- Comment period closes July 27, 2026 (Federal Register docket 2026-10375)
- Eligibility is tiered; Tier 3 institutions (non-federally supervised) face a temporary hold on application decisions through December 31, 2026
- Direct access requires a demonstrable BSA/AML and OFAC compliance program — the Fed can mandate independent third-party assessments
The May 2026 Executive Order That Kicked This Off
On May 19, 2026, President Trump signed an Executive Order titled “Integrating Financial Technology Innovation Into Regulatory Frameworks.” The Order directed federal financial regulators to review existing regulations, guidance, and supervisory practices that impede fintech partnerships with banks and credit unions, or that create barriers to charter applications. Regulators have 90 days to identify the barriers and 180 days to take responsive steps.
Critically, the EO also “requested” — technically non-binding, but politically significant given who’s asking — that the Federal Reserve conduct a comprehensive evaluation of its legal, regulatory, and policy framework governing payment system access for uninsured depository institutions and non-bank financial companies, including digital asset firms.
The Fed’s response came the next day.
What the Fed Actually Proposed
On May 20, 2026, the Federal Reserve announced it was proposing a new special-purpose account category: the Payment Account. The proposal was published in the Federal Register on May 26, 2026 (Docket No. 2026-10375), with a 60-day comment window ending July 27.
The Payment Account is designed for institutions that need to clear and settle payments directly at the Fed but don’t need — or can’t obtain — a full master account. Think stablecoin issuers, licensed money transmitters, payments-focused fintechs, and digital asset custodians that want to get off their sponsor bank’s infrastructure and onto the Fed’s rails directly.
What You’d Get—and What You Wouldn’t
The payment account is deliberately constrained. The Fed built in hard limits to reduce systemic risk before the framework is fully proven:
| Feature | Full Master Account | Payment Account |
|---|---|---|
| Fedwire Funds (large-value) | ✓ | ✓ |
| FedNow (instant payments) | ✓ | ✓ |
| FedACH (batch ACH) | ✓ | ✗ |
| Discount window access | ✓ | ✗ |
| Intraday credit | ✓ | ✗ |
| Interest on balances | ✓ | ✗ |
| Overnight balance cap | None | $1 billion |
The deliberate omissions matter. No discount window means the Fed isn’t your lender of last resort — you need adequate liquidity buffers independent of Fed access. No intraday credit means you pre-fund your positions. No interest on balances limits the incentive to park large amounts at the Fed indefinitely. The $1 billion closing balance cap reinforces this: Payment Accounts are settlement infrastructure, not investment vehicles.
The exclusion of FedACH is notable. ACH batch settlement operates on different risk rails and the Fed is clearly treating this as phase-two territory at earliest.
Who’s Eligible: Understanding the Three Tiers
The Fed’s existing Account Access Guidelines classify institutions seeking Reserve Bank accounts into three tiers based on their federal supervisory status. The Payment Account proposal maps onto this same framework:
Tier 1 institutions are federally insured and subject to federal prudential supervision — traditional banks and credit unions. They face the lowest level of scrutiny in the account access process because their regulatory oversight and deposit insurance already create accountability structures.
Tier 2 institutions are subject to federal prudential supervision but may not be federally insured, or may operate through a holding company structure that meets specific requirements. Certain licensed trust companies and specialized institutions fall here.
Tier 3 institutions are not federally insured and not subject to prudential supervision by a federal banking agency. Most uninsured fintechs, licensed money transmitters, digital asset custodians, and stablecoin issuers operate as Tier 3 entities.
The Tier 3 classification carries a significant practical implication: the Fed has temporarily paused application decisions for Tier 3 institutions while it finalizes the Payment Account policy framework. That pause is expected to lift no later than December 31, 2026.
If you’re a Tier 3 institution, you should still submit a comment before July 27. You won’t receive a decision on an account application before year-end, but comments from eligible-but-paused institutions directly shape what the final access framework looks like.
The Compliance Bar: What the Fed Will Require
Access to a Payment Account is not a registration — it’s a supervised relationship, and the Fed will vet your compliance infrastructure before granting access. Specifically, Reserve Banks can require applicants to:
- Provide documentation demonstrating compliance with Bank Secrecy Act and AML obligations
- Demonstrate OFAC sanctions compliance
- Submit to independent third-party assessments of BSA/AML and OFAC programs — self-certifications alone are not sufficient
- Provide attestations from senior management
- Share audit reports
- Notify the Reserve Bank of events that materially change the institution’s illicit finance risk profile
This compliance bar has real teeth. Institutions with underdeveloped AML programs — no written AML policy, no designated compliance officer, no independent testing — should not apply until those gaps are closed. You are asking to be a direct participant in the Fed’s payment infrastructure. The Fed will vet your program accordingly.
Sullivan & Cromwell’s analysis flags the independent assessment requirement as particularly significant: this is not a checkbox exercise. Institutions with BaaS-model compliance programs — where the sponsor bank owns the BSA/AML obligations — face a structural challenge if they pursue Payment Account access. The question becomes: can you demonstrate a BSA/AML program that is yours, not your bank partner’s?
What This Means for BaaS-Model Fintechs
The Payment Account isn’t designed for fintechs currently inside a BaaS structure. Those companies rely on their sponsor bank’s existing Fed access as part of the arrangement — they inherit the bank’s infrastructure rather than accessing it directly. The Payment Account is designed for fintechs that want to operate outside that structure, or want to reduce dependency on a single sponsor bank for payment rails.
For BaaS-model fintechs, the more immediate implication is competitive and structural: if the Payment Account framework matures and becomes accessible to Tier 2 and Tier 3 firms, it changes the leverage dynamics in bank-fintech relationships. A fintech that can credibly pursue direct Fed access has more negotiating power with sponsor banks over fee structures, terms, and exit scenarios.
The structural risks created by BaaS intermediary dependency are well-documented. As covered in detail in our post on BaaS vendor exit planning after Synapse, the 2024 Synapse bankruptcy exposed what happens when a middleware firm fails and reconciliation breaks down. Direct Fed access, at maturity, addresses some of those risks at the source — though it introduces new compliance obligations in their place.
What This Means for Stablecoin Issuers
The use case is clearest here. Stablecoin operations require managing on- and off-ramp liquidity between digital assets and US dollars in real time. Today, that typically means relying on a banking partner to hold dollar reserves and handle dollar settlement.
A Payment Account would let a stablecoin issuer manage dollar-side liquidity directly at the Fed — Fedwire Funds for large-value settlement, FedNow for smaller-value instant transfers. No banking intermediary. No dependency on a partner bank’s appetite for stablecoin-related deposits.
The GENIUS Act, signed in July 2025, requires stablecoin issuers to maintain 1:1 reserves in high-quality liquid assets. Reserves held directly at the Federal Reserve represent the highest-quality liquid asset available under U.S. law. For stablecoin issuers building GENIUS Act-compliant reserve structures, a Payment Account would be architecturally optimal — if the compliance bar can be met.
Our post on GENIUS Act AML/CFT compliance covers the FinCEN and OFAC requirements that stablecoin issuers already face. Those same requirements overlap significantly with what the Fed will evaluate in a Payment Account application. If your GENIUS Act compliance program is solid, your Payment Account application has a stronger foundation.
So What? Three Things to Do Before July 27
The comment window closes in 19 days. Even if you’re not planning to apply immediately, three things warrant attention now:
1. Determine your tier. Is your institution Tier 1, 2, or 3 under the existing Account Access Guidelines? Non-bank financial companies that don’t know the answer should find out immediately. Tier 3 means a pause on decisions through year-end — but it doesn’t mean you shouldn’t be preparing or commenting. Mayer Brown’s analysis includes a useful tier classification walkthrough.
2. Audit your BSA/AML and OFAC posture. The Fed’s minimum is a documented, tested, independently assessed compliance program. If your AML infrastructure is currently embedded in a sponsor bank relationship rather than your own program, you have a gap that would surface immediately in any application review. The due diligence and vendor management program in your TPRM kit can help structure the documentation the Fed will want to see — particularly around third-party compliance dependencies.
3. Submit a comment if access terms affect you. The July 27 deadline is real and the comment record matters. Focus on: the eligibility tier criteria (especially if your institution structure creates ambiguity), the specific BSA/AML independent assessment requirement, whether FedACH access should be phased in, and the mechanics of the $1B closing balance limit. The Federal Register docket number is 2026-10375.
The Payment Account proposal is early-stage — the comment period is open precisely because the final framework isn’t set. What financial institutions say before July 27 shapes what institutions can do in 2027.
◆ Related template
Third-Party Risk Management (TPRM) Kit
Complete vendor risk management lifecycle from initial due diligence to ongoing oversight.
◆ Immaterial Findings · Weekly
Sharp risk & compliance insights. No fluff.
◆ FAQ
Frequently asked questions.
What is the Federal Reserve's proposed Payment Account and how does it differ from a Master Account?
Which fintechs are eligible to apply for a Federal Reserve Payment Account?
What compliance requirements will the Fed impose on Payment Account applicants?
Why doesn't the Payment Account include FedACH access?
How does the May 2026 Trump Executive Order relate to the Fed's Payment Account proposal?
Should my fintech submit a comment before July 27?
Author
Rebecca Leung
Rebecca Leung has 8+ years of risk and compliance experience across first and second line roles at commercial banks, asset managers, and fintechs. Former management consultant advising financial institutions on risk strategy. Founder of RiskTemplates.
◆ Related framework
Third-Party Risk Management (TPRM) Kit
Complete vendor risk management lifecycle from initial due diligence to ongoing oversight.
◆ Keep reading
Related posts.
Regulatory Compliance
SEC Cyber Disclosure Rule: What 2.5 Years of Form 8-K Filings Reveal About Your Response Program Gaps
The SEC's 4-business-day cyber incident disclosure rule has 2.5 years of enforcement history. Here's what the filings and enforcement actions reveal about common materiality determination failures — and how to build a decision protocol that survives SEC scrutiny in 2026.
Jul 5, 2026
Regulatory Compliance
GENIUS Act AML/CFT Compliance: Breaking Down the FinCEN and OFAC Rule That Drops July 18
The FinCEN/OFAC joint proposed rule for stablecoin issuers establishes a full BSA/AML compliance program requirement — SAR filing, CTR filing, CIP, CDD, and OFAC sanctions screening — with a technical wallet-blocking mandate that has no precedent in traditional financial services. Here's what Permitted Payment Stablecoin Issuers and their bank partners need to build.
Jul 4, 2026
Regulatory Compliance
15 Days Until the GENIUS Act Regulatory Deadline: What Stablecoin Issuers Need Before July 18
Six federal agencies must finalize GENIUS Act implementing regulations by July 18, 2026. Here's what the OCC capital floor, FinCEN CIP rules, and the compliance timeline mean for stablecoin issuers right now.
Jul 2, 2026