Current status: the procedural vote matters
On September 15, 2026 the Senate did not invoke cloture on the motion to proceed to H.R. 3633. The official floor record reports 49 yeas and 50 nays, with a motion to reconsider entered. This was a procedural vote on proceeding, not final passage. As of September 27, this review treats CLARITY as pending legislation, not enacted law. [1]
The sponsors released their latest substitute draft on September 14. Their description of “final” text means the version they proposed to offer, not a statute signed into law. Analysis below uses that draft, EHF26724, and distinguishes it from older House and Senate versions. [2, 3]
For a financial institution or technology provider, the immediate decision is how to prepare options under uncertainty. A proposed new classification or registration path is not present authority to launch a product. Build a current-law assessment and a separate contingent design.
A market framework should be judged by the trading experience
A clearer classification can help firms understand the proposed registration path, but it does not by itself create deep or fair execution. Market quality also depends on who supplies liquidity, how prices are formed and whether customers can compare the full cost of trading. The draft remains a legislative proposal, not operating permission. [3]
Potential benefits should therefore be stated as mechanisms to test. More predictable rules might make participation easier for some firms. The resulting competition could improve service, or activity could remain concentrated among a few providers with substantial fixed costs. Trading volume alone cannot settle which outcome customers receive.
What the draft tries to organize
The September text combines securities-related provisions for ancillary assets and network tokens with a CFTC framework for digital-commodity intermediaries. It includes exchange, broker, dealer and custody provisions, customer-property protections, illicit-finance measures and software-developer provisions. The economic rights of an instrument remain central; recording a loan or investment on a blockchain does not by itself settle its legal classification. [3]
Recommended analysis has two axes: the asset and the activity. For the asset, identify redemption, debt, equity, profit and control rights. For the activity, identify issuance, distribution, execution, custody and lending. A single platform can occupy several roles. “Crypto business” is too broad a category for licensing, capital or operational diligence.
Stablecoin rewards and deposit competition
Section 10404 of the September draft would restrict covered digital-asset service providers and affiliates from paying stablecoin interest or yield that functions like interest on a bank deposit. It preserves qualifying bona fide activity or transaction rewards. The draft also includes a Treasury process addressing specified harmful deposit movement from community banks. These provisions are proposed and depend on statutory conditions and future rules. [3]
The sponsors explain the September changes as a way to protect community-bank funding while allowing payment innovation. That is their policy rationale, not evidence that a particular level of deposit flight will occur. [2]
For product and funding strategy, model customer behavior rather than assuming either universal migration or no effect. A reward linked to purchases can attract a different customer from a balance-based yield product. Conversion friction, trust, payroll integration, payment acceptance and access can matter as much as the advertised rate.
Custody and conflicts shape the actual customer claim
A customer buying an asset through an intermediary needs to understand what is held, who controls transfers and what rights apply if the provider fails. A familiar application interface cannot answer those questions. Nor does a regulatory label remove the need to examine the agreements and operating arrangements for a particular service.
Conflicts deserve the same practical attention. A firm may have incentives arising from trading, distribution or relationships with issuers. The useful inquiry is whether those incentives affect execution, recommendations, asset availability or fees, and how they are addressed. These are market-design questions even when the underlying technology operates as intended.
Worked example: separate funding sensitivity from the legislative forecast
Illustrative bank: $120 million of a deposit segment is exposed to competing products. If 10% moves and replacement funds cost 2 percentage points more, annual incremental expense is $240,000: $120 million × 10% × 2%. That is a sensitivity calculation, not a forecast that CLARITY passes or causes those outflows.
Run at least three cases: the bill stalls; a version passes with narrower rewards; or a version passes with different reward and intermediary rules. In each case, model funding cost, needs, fee opportunities and technology expense. Avoid booking hypothetical regulatory relief into the base budget before enactment and effective implementation.
The same discipline applies to a tokenized loan product. Faster settlement does not remove borrower default risk, servicing cost or the legal claim’s classification. Improved distribution may lower execution friction while leaving the expected loss and capital economics broadly unchanged.
Customer protection and intermediary controls
The sponsors’ September release highlights changes concerning affiliate trading, conflicts, state consumer-protection laws, ethics and software developers. The Banking Committee had advanced earlier text by a 15–9 vote in May. Neither milestone establishes that all proposed protections now apply to a live platform. [2, 4]
Recommended diligence should examine asset segregation, reconciliation, custody keys, insolvency treatment, related-party activity, execution quality and customer disclosures under currently applicable law. Where the draft offers a possible future framework, keep that analysis clearly labeled. Do not accept a vendor’s claim that the bill has already solved its licensing or consumer-claim problem.
Developer protections deserve fact-specific analysis. A party that writes code and a party that controls customer assets, executes transactions or operates an intermediary are not automatically equivalent. Product descriptions should identify actual control rights and revenue flows. Rebranding an intermediary as software does not resolve the legal issue.
Adoption requires more than a favorable legislative outcome
A financial institution considering a new service faces integration, custody, accounting, customer support and recovery work. Legal clarity can reduce one source of uncertainty while leaving those costs intact. A credible business case compares demand and revenue with the full operating model, including the expense of handling failed transfers or misunderstood product features.
Staging the work can preserve flexibility: resolve customer needs and data requirements before committing to a design that depends on an unpassed provision. This is an operating principle rather than a forecast of passage. Evidence that would strengthen the case includes enacted text, workable implementation rules, credible customer demand and demonstrated economics under realistic service and market conditions.
The policy trade-off
The case for legislation is that defined categories, registration paths and coordinated oversight could reduce uncertainty and improve accountability. The countervailing concern is that exceptions, supervisory capacity or weak implementation could leave meaningful gaps. My assessment is that statutory clarity has value only if the operational perimeter matches the real economic activity.
For banks, a second trade-off is competitive: clearer entry may enable custody, settlement and distribution revenue while increasing pressure on transaction balances. Those effects need not occur at the same institution or on the same timetable. A bank that earns modest custody fees but loses a large low-cost funding base can face an unfavorable net outcome even as market adoption grows.
Actions now and evidence that changes the thesis
Maintain a version-controlled issues register covering current authority, proposed changes, unresolved interpretations, required rulemakings and responsible owners. Preserve the September 14 draft for this revision; future articles should explain substantive text changes rather than silently replacing the analysis. Track official floor action and bill text rather than sponsor headlines alone. [1, 2, 3]
The investment case improves with enactment of a workable perimeter, timely implementation, credible customer-property protections and measured demand for services a bank can provide profitably. It weakens if compliance cost overwhelms revenue, funding migration is concentrated or classification disputes persist. Until then, staged preparation is more defensible than treating an uncertain bill as a completed operating model.
Sources
- U.S. Senate: official September 15, 2026 floor activity and cloture resultOfficial sourceBack to text: ↑1↑2
- Senators Lummis, Boozman and Scott: September 14, 2026 draft releaseOfficial releaseBack to text: ↑1↑2↑3↑4↑5
- September 14, 2026 proposed substitute, EHF26724; especially section 10404Official source · PDFBack to text: ↑1↑2↑3↑4↑5
- Senate Banking Committee: May 14, 2026 committee voteOfficial sourceBack to text: ↑1↑2