Between “Front-End” and “Broker”

April 15, 2026

On April 13, 2026, the SEC’s Division of Trading and Markets released a staff statement that crypto practitioners have been waiting on for the better part of a year: formal guidance on when a user-facing interface that facilitates crypto asset securities transactions can operate *without* registering as a broker-dealer under Section 15(a) of the Securities Exchange Act of 1934. The short version: if your platform is a neutral tool (no custody, no advice, no discretion, no funny business with fees) the staff won’t recommend enforcement. For five years. Maybe.

What Problem Is This Solving?

Under the Exchange Act, a “broker” is “any person engaged in the business of effecting transactions in securities for the account of others.” 15 U.S.C. § 78c(a)(4)(A). Courts have interpreted “effecting transactions” broadly — routing orders, soliciting trades, handling funds, and providing transaction-related advice can all trigger registration obligations.¹

The problem for crypto is that the line between “software tool” and “broker” has been unclear (to say the least). A non-custodial wallet that integrates a swap aggregator, a DEX front-end that routes trades across multiple liquidity pools, an app that compares execution venues for token trades – each of these could be characterized as “effecting transactions” under a sufficiently aggressive reading of existing caselaw.

The Crypto Task Force roundtables and written submissions throughout late 2025 and early 2026 surfaced this issue repeatedly. The Blockchain Association’s April 6, 2026, comment letter put it bluntly: providers of non-custodial wallet interfaces and DEX front-ends that neither control customer assets nor perform core trading functions are not securities intermediaries. The staff appears to have listened.

The “Covered User Interface Provider” Framework

The statement introduces the concept of a “Covered User Interface Provider” – an entity that operates a website, mobile application, or browser-based tool that helps users prepare and transmit crypto asset securities transactions through self-custodial wallets. The staff’s position is that such a provider need not register as a broker-dealer, provided it satisfies a detailed set of conditions.

I want to emphasize: this is a staff statement, not a Commission-level rule or interpretation. It is not legally binding. It doesn’t create rights or obligations enforceable in court. That said, what it does do is signal that the Division of Trading and Markets won’t recommend enforcement action against providers that color inside these lines. That matters (think of it as the practical equivalent of a conditional no-action position) but it’s a different animal from the Joint Interpretation the SEC and CFTC issued on March 17, which was a formal Commission action binding on both agencies.²

The Conditions: Seven Pillars of Neutrality

The conditions break down into roughly seven categories. Each is independently necessary. Miss one, and you’re back in broker-dealer territory.

  1. No Recommendations, No Solicitation. The provider cannot recommend specific trades, suggest particular crypto asset securities, or solicit transactions. The interface must function as a passive tool through which users make their own decisions about what to buy, sell, or swap, in what quantity, and at what price.
  2. User Retains Full Control. The user must control all trade parameters — price, size, timing, execution preferences. The interface cannot override, modify, or constrain user choices in ways that reflect the provider’s judgment about what’s best for the user. Self-custody is assumed throughout.
  3. Objective Presentation of Options. If the interface displays multiple execution routes or venues, it must sort or filter them using objective, pre-disclosed criteria: price, speed, fee amount, liquidity depth. The provider cannot label any route as “best,” “preferred,” or “recommended.” No subjective characterizations, no editorial overlay.
  4. Fee Neutrality. Fees must be fixed, transparent, and applied consistently regardless of which asset is traded, which venue is selected, or what execution route is chosen. The provider’s compensation cannot vary based on trade outcomes, counterparty identity, or venue affiliation. If you’re currently earning revenue through route-dependent fee structures (and a lot of aggregators and wallet-integrated swap features are) this condition requires a fundamental business model rethink.
  5. Conflict Disclosure and Fair Treatment. If the provider is affiliated with a trading venue, liquidity pool, or other execution system, it must disclose that relationship prominently. Affiliated venues must be treated on the same terms as unaffiliated venues in how they’re presented and accessed through the interface.
  6. Comprehensive Disclosure Obligations. Providers must clearly communicate their non-registered status, their fee structures, their conflicts of interest, the mechanics of how the system works, their cybersecurity controls, and the limitations of the interface. The staff wants users to understand what they’re using and what protections they don’t have.
  7. Venue Monitoring. Providers must implement and maintain policies for evaluating connected trading venues on factors like liquidity, transparency, security, and reliability. These evaluations must be consistent across all integrated systems and subject to ongoing review. Default parameters must be based on objective criteria.

What (or who) is Still a Broker

The statement explicitly carves out activities that remain squarely within the broker-dealer registration requirement: executing trades, holding or handling customer assets, providing investment advice, negotiating transactions, or exercising discretion over order routing or execution. If your platform does any of these things, you’re a broker. Full stop. The statement doesn’t change that.

This is worth emphasizing because there’s a natural tendency to read these kinds of staff positions as broader than they are. The statement protects a specific, narrow category of activity: providing a neutral software tool through which users independently prepare and submit transactions using their own wallets. The moment the provider’s thumb is on the scale (in any direction, for any reason) the protection evaporates.

How This Fits Into the Broader Picture

This statement doesn’t exist in a vacuum. It sits inside a rapidly evolving regulatory architecture that has taken shape over the past twelve months:

  • The SEC/CFTC Joint Interpretation (Release No. 33-11412, March 17, 2026) established a five-part crypto asset taxonomy — digital commodities, digital collectibles, digital tools, stablecoins, and digital securities — and formally superseded the SEC staff’s 2019 Framework for “Investment Contract” Analysis of Digital Assets.
  • The GENIUS Act (Pub. L. No. 119-27), enacted in July 2025, created a statutory carve-out for payment stablecoins issued by permitted issuers.
  • The Division’s December 2025 statement on broker-dealer custody of crypto asset securities clarified how Rule 15c3-3 applies to private key management.
  • The DTC no-action letter (December 11, 2025) authorized a three-year pilot for tokenizing DTC-custodied assets on supported blockchains.

Today’s statement is the next tile in the mosaic by addressing the front-end layer, the interfaces through which retail and institutional users actually interact with onchain markets, and does so in a way that’s consistent with the trajectory of the Crypto Task Force comment letters, which have consistently argued that software providers who don’t control assets, don’t exercise discretion, and don’t intermediate trades shouldn’t be forced into the broker-dealer box.

Five-Year Sunset

The framework has a built-in expiration: five years from issuance, unless superseded by Commission-level rulemaking or legislation. The staff clearly expects that either the forthcoming “Reg Crypto” exemptive framework (currently under OIRA review) or a comprehensive market structure bill from Congress will provide a more durable answer before then. All of that said, read the actual statement. The conditions are detailed and the distinctions matter. Further, it is really important to remember that staff-level guidance is not a safe harbor, it’s a weather forecast, and a forecast won’t keep you dry if it storms.

¹See, e.g., SEC v. Kramer, 778 F. Supp. 2d 1320 (M.D. Fla. 2011); SEC v. Hansen, No. 83 Civ. 3692, 1984 WL 2413 (S.D.N.Y. Apr. 6, 1984).

²See “Application of the Federal Securities Laws to Certain Types of Crypto Assets and Certain Transactions Involving Crypto Assets,” Release No. 33-11412, 91 Fed. Reg. 13,714 (Mar. 23, 2026).

Written by David Lopez Kurtz