Andreessen Horowitz (a16z) has asked New York's Department of Financial Services (NYDFS) to withdraw and rewrite its proposed payment stablecoin rules, arguing that finalizing a state regime before federal standards exist could put the state's certification at risk. The firm's September 21, 2026 comment letter marks an escalation in the state vs. federal stablecoin regulation standoff — and the practical exposure reaches beyond issuers to startups, DAOs, and finance teams that rely on stablecoin payment and custody rails (TokenPost, October 21, 2026).
Table of Contents
- What Just Happened: A16z's Letter to New York
- Why It Matters Now for Founders, Finance Leads, and DAOs
- The Background You Need Before Acting
- Concrete Implications and Recommended Actions
- What to Watch Next and Open Questions
- Key Takeaways
What Just Happened: A16z's Letter to New York
The September 21 comment letter and the July 22 Part 202 proposal
TokenPost reported on October 21, 2026 that a16z submitted a September 21, 2026 comment letter to NYDFS asking the agency to withdraw and rewrite its proposed Part 202 rules for payment stablecoin issuers. New York published the proposed rule on July 22, 2026. The timing is the core problem: the GENIUS Act — signed into law on July 22, 2025 (White House fact sheet) — requires federal implementing rules from Treasury and the OCC, and that federal process was still ongoing when New York moved first. The Act creates a path for state-qualified payment stablecoin issuers to remain under state supervision, but only if the state's framework passes a federal test. The Stablecoin Certification Review Committee must approve the state's rules as substantially similar to federal standards. a16z warned that differences between New York's final Part 202 rule and the eventual federal requirements could lead the committee to deny New York's certification — which would remove the state-supervision option for issuers that depend on it (TokenPost, October 21, 2026).
Why It Matters Now for Founders, Finance Leads, and DAOs
The unresolved state vs. federal question
Public debate often frames state and federal stablecoin oversight as complementary, but that view assumes a stable federal standard already exists. The a16z–NYDFS letter identifies a different problem: a state rule finalized now cannot be measured against a federal standard that does not exist yet. For payment stablecoin issuers and their business customers, "complementary" is a projection, not a settled legal fact, until the certification review actually runs.
My adjudication: the complementary framing is structurally reasonable for the long run, but it underweights the binary near-term risk. The certification committee compares text to text; a state that moves first owns the mismatch risk.
Classification shifts are not hypothetical, either. An asset can move from ordinary to significant under supervisory benchmarks — USDC Tagged 'Significant' EMT: Stablecoin Regulation Shift shows how quickly a stablecoin's regulatory category can change as oversight matures.
Where the current pages disagree—and what that disagreement actually costs
There is a second split worth naming. Ripple's institutional materials treat existing US oversight as sufficient for RLUSD, while a16z's comment letter warns that pending state/federal divergence creates real stablecoin issuer certification risk for payment stablecoin issuers generally.
Both can be locally true. Ripple operates RLUSD through a New York trust company under an existing NYDFS supervisory relationship, so its comfort may be issuer-specific. The a16z warning applies to the broader class of state-qualified issuers whose frameworks have not cleared the committee.
For a non-issuer business, the cost of that disagreement is concrete: if a state's issuer certification is denied, the stablecoins issued under that framework could face a different supervisory trajectory — potentially affecting redemption, banking support, and which crypto on-ramp and off-ramp providers can hold them. Businesses that treat "our issuer says it is fine" as the end of the analysis are carrying a hidden counterparty risk.
The Background You Need Before Acting
What stablecoins are and how they're used in business
Stablecoins are digital assets pegged 1:1 to a fiat currency, used for payments, trading, cross-border transfers, and working capital. Adoption has moved fast — stablecoin payments surpassed ACH in some contexts, which is why the legal wrapper around issuers now matters to everyday workflows.
How US stablecoin regulation is currently split
US stablecoin regulation is fragmented: federal agencies like Treasury, the OCC, and the Fed touch stablecoin activity through banking and securities authorities, while state regulators (notably NYDFS) license issuers. The split means compliance differs by jurisdiction and a single issuer can sit in multiple lanes.
The $10 billion threshold and the certification review
The GENIUS Act draws a $10 billion threshold: state-qualified payment stablecoin issuers with no more than that in consolidated outstanding issuance may choose state supervision if their state's framework is certified as substantially similar. Above that threshold, the federal path takes over. Treasury and the OCC began formal implementation in September 2025 (Treasury press release). Those earlier comment cycles already exposed friction between market practice and drafting assumptions — see Stablecoin Regulation: What the NCA Treasury Comments Mean. The federal process was still unfinished when New York published Part 202.
Concrete Implications and Recommended Actions
For founders: map your stablecoin exposure and jurisdictions
Start with a mapping exercise, not a policy debate. Identify which stablecoins you hold and transact in, which legal entity issues each one, under which state or federal framework that issuer currently operates, and whether that framework is certified or pending. Most founders cannot answer the last two questions. That gap is the exposure.
Then classify your balances: operating cash needs high certainty; crypto working capital needs speed; treasury reserves need segregation. Different classifications should ride different rails.
For finance leads: ask your banking and on/off-ramp provider the right questions
Your banking and crypto on/off-ramp provider sits between you and the regulatory risk. Ask:
- Which stablecoin issuers do you support, and under what framework is each qualified?
- Do any of your settlement paths depend on a NYDFS trust company or an uncertified state framework?
- If a major issuer's state certification is denied, what is your contingency — alternate issuer, fiat fallback, or custody re-route?
- Are customer funds segregated from your operating accounts, and where are digital assets held?
- Can you provide audit-ready reporting across fiat and crypto balances?
Then test the answers by running one non-critical payment through a second rail before you need it. Banking-side infrastructure is changing rapidly — Lead Bank's stablecoin APIs signal that on/off-ramp exposure is becoming more programmable, which makes vendor-side contingency questions more urgent.
For DAOs: separate treasury operations from regulatory risk
For decentralized organizations, the cleanest DAO treasury management rule is separation: keep core operating funds in fiat or fiat-denominated instruments in segregated accounts, while holding only working capital in stablecoins. That way, a certification decision in one state does not freeze payroll or vendor payments.
For DAOs, role-based permissions and multisig controls matter more as regulatory risk rises. A platform that provides segregated multi-currency accounts, USDC on/off-ramps, and DAO-specific role controls (OneSafe, for example, supports free USDC deposits and withdrawals, multi-currency accounts, and customizable roles) makes a fiat-core plus stablecoin-working-capital split operationally manageable. The tradeoff between self-custody and managed rails is real; NEAR's approach vs. hybrid platforms outlines what to weigh.
| Role | Do now | Ask | If state certification is denied |
|---|---|---|---|
| Founders | Map stablecoin holdings by issuer, jurisdiction, and treasury class | Which issuer's stablecoin do we hold, under which framework? | Pre-approve a second issuer and a fiat fallback |
| Finance leads | Document your on/off-ramp provider's regulatory dependencies | Does your provider rely on NYDFS trust or an uncertified state framework? | Test a second rail now; re-segregate balances if a denial triggers |
| DAOs | Separate fiat operating funds from stablecoin working capital | Who holds keys, and where are digital assets custodied? | Re-route payroll and vendors to fiat or a certified-rail stablecoin before deadlines |
What to Watch Next and Open Questions
Will New York wait for final federal standards?
NYDFS now has a decision: proceed with Part 202 and accept the certification risk, or wait for final federal standards and leave New York-licensed issuers in limbo longer. Watch for the agency's response to the comment letters and any revised proposal.
What the certification review committee will actually compare
The committee will compare state rules against federal standards on reserves, redemption, capital, risk management, and permissible assets (the exact comparison framework is still being defined).
The open questions no regulator has answered yet
- Will substantially similar be strictly textual, or will supervisory outcomes count?
- Does a state framework get partial certification, or is it all-or-nothing?
- What happens to existing state-licensed issuers during a certification denial?
Key Takeaways
- a16z's September 21, 2026 letter asks NYDFS to withdraw Part 202 until federal GENIUS Act standards are final, because a premature rule could cost New York its stablecoin issuer certification.
- For non-issuers, the a16z New York stablecoin letter is a counterparty and rail risk warning, not just an issuer problem: know which issuer and framework back every stablecoin you hold.
- Treat state certification as a pending binary, not a settled complementarity, until the Stablecoin Certification Review Committee rules.
- Finance leads should audit their on/off-ramp provider's NYDFS dependency and test a second rail; DAOs should separate fiat operating funds from stablecoin working capital now.
- Watch NYDFS's next move and the committee's comparison framework for the earliest signal of whether certification risk materializes.
If your team needs one platform for fiat and stablecoin operations with segregated accounts and DAO-ready controls, sign up for OneSafe to map your rails.
