SEC Clarifies Broker-Dealer Scope for Crypto Asset Securities Interfaces

The Interface Is Not the Broker, But the Line Is Thinner Than It Looks

On April 13, 2026, the U.S. Securities and Exchange Commission, through its Division of Trading and Markets, published a staff statement addressing a question that has been sitting at the center of U.S. crypto market structure for years: under what circumstances does the operator of a user interface facilitating crypto asset securities transactions cross the line into broker-dealer activity?

The document is carefully framed. It does not constitute a rule adopted by the Commission, nor does it create binding legal obligations or safe harbors. Rather, it reflects the staff’s current interpretive posture: an attempt to provide directional clarity in an area where statutory concepts developed for traditional intermediated markets are being applied to architectures built around self-custody and direct protocol interaction.

And yet, despite its formally non-binding status, the statement is consequential. It offers, perhaps for the first time in a structured way, a functional test for distinguishing between software that enables transactions and entities that effect them.

There is an additional layer to this that is easy to overlook, but essential to understanding the statement correctly. The SEC is not, in this document, attempting to resolve the classification of crypto assets. That question, whether a particular token or instrument constitutes a security, remains governed by existing legal tests and has been addressed separately, including in the Commission’s March 2026 release on the application of federal securities laws to crypto assets.

Instead, the focus here is different. It assumes that at least some crypto assets in circulation already fall within the definition of securities, and asks a downstream question: what are the regulatory consequences for those who build the infrastructure through which those assets are traded?

This is therefore not a statement about issuance, token design, or primary offerings. It is a statement about transactional infrastructure, specifically, the role of interfaces that sit between users and execution environments in secondary markets.

From Intermediated Markets to Interface-Based Execution

The starting point for the staff’s analysis is an implicit recognition that crypto-native transaction flows differ fundamentally from those assumed by the Exchange Act.

In traditional securities markets, the pathway is clear: an investor places an order, a broker intermediates that order, and execution occurs through established market infrastructure. The legal framework maps neatly onto that chain of intermediation.

By contrast, the “Covered User Interface” described in the statement operates in a different environment. It is a website, application, or embedded wallet interface that allows a user, through a self-custodial wallet, to define transaction parameters and convert them into blockchain-executable instructions. The interface does not hold assets, does not execute trades in the conventional sense, and does not stand between counterparties. It translates intent into code and facilitates interaction with smart contracts or distributed trading systems.

This shift from intermediation to interaction creates the legal tension the statement attempts to resolve.

The Central Question: When Does Facilitation Become Intermediation?

The relevant statutory framework has not changed. Section 15(a) of the Exchange Act prohibits unregistered brokers from inducing securities transactions, and Section 3(a)(4) defines a broker as a person engaged in the business of effecting transactions in securities for the account of others.

What has changed is the context in which those concepts must be applied. 

At its core, the entire analysis hinges on a single, but highly consequential question: is the interface provider, in substance, “effecting transactions” on behalf of users, or merely enabling users to effect their own transactions?

If a user independently determines transaction parameters, signs the transaction, and submits it through a self-custodial wallet, can the interface that made that process intelligible be said to have “effected” the transaction? Or is it more appropriately understood as a tool, akin to a calculator or communication layer, through which the user acts?

The staff’s answer is neither categorical nor purely formalistic. Instead, it is built around a functional assessment of the interface provider’s role.

A Conditional Non-Objection Framework

The statement articulates a set of conditions under which the staff would not object to a Covered User Interface Provider operating without broker-dealer registration.

What emerges from these conditions is not a bright-line rule, but a coherent framework structured around a single unifying principle: the interface must remain non-intermediating in substance, even if it is indispensable in practice.

This principle is expressed across several dimensions.

User Control as the Anchor

First, the user must remain the locus of decision-making.

The interface may assist in defining transaction parameters and may provide educational content to help users understand those parameters. However, it must not displace user judgment. The ability to customise defaults is essential, not incidental.

This reflects a broader regulatory instinct: where decision-making authority resides is often determinative of whether an activity is viewed as advisory, intermediary, or merely facilitative.

The Prohibition on Transaction-Level Influence

Second, the provider must refrain from soliciting specific transactions.

While general promotion of the interface is permitted, the line is drawn at encouraging particular investment actions involving specific crypto asset securities. This distinction preserves the conceptual separation between offering access to a tool and influencing investment behavior through that tool.

Importantly, the prohibition extends beyond explicit recommendations. The structure and presentation of information within the interface are also implicated.

Neutrality in Routing and Presentation

The treatment of execution routes illustrates this point with particular clarity.

The interface may display one or more potential execution pathways and may allow users to filter or sort those pathways based on objective criteria such as price or speed. However, it may not characterise any route as superior, for example, by describing it as offering the “best price” or being “most reliable.”

This reflects a nuanced but critical insight: in digital environments, design choices can function as de facto recommendations. By constraining not only what is said but how options are structured, the staff is attempting to limit subtle forms of behavioral steering.

Objectivity and Explainability of System Logic

A related requirement is that the software underpinning the interface must operate based on pre-disclosed, objective, and independently verifiable parameters.

This is, in effect, a transparency obligation applied to algorithmic behavior. It signals skepticism toward opaque optimisation processes that may embed discretionary judgments or undisclosed priorities.

In practical terms, it pushes interface providers toward explainable systems, where the transformation from user input to displayed output can be understood, audited, and, at least in principle, replicated.

Compensation as a Regulatory Signal

The structure of compensation receives particularly careful treatment.

The provider’s fees must be fixed, user-paid, and agnostic to transaction characteristics such as size, execution venue, or counterparty. The statement explicitly excludes compensation models that depend on transaction flow from third parties, including payment for order flow.

It reflects a deeper regulatory concern: compensation mechanisms often reveal where economic incentives, and therefore functional roles, truly lie.

In U.S. securities law, transaction-based compensation has long been treated as a key indicator of broker activity. Where an entity’s revenue is tied to the occurrence, size, or characteristics of securities transactions, it suggests that the entity has a direct economic interest in those transactions taking place. That interest, in turn, is often associated with participation in the transaction process itself, rather than mere facilitation.

The staff’s approach in this statement follows that logic. By requiring compensation to be fixed and user-paid, the framework attempts to eliminate the types of incentives that could subtly influence how transactions are structured, routed, or presented. It is not only explicit forms of steering that are relevant here. It is also the presence of embedded economic drivers that may shape system behavior in ways that are not immediately visible to the user.

This is particularly important in the context of modern trading interfaces, where monetization models can be layered and indirect. Revenue may be generated through venue arrangements, routing preferences, spread capture, affiliate relationships, or other forms of transaction-linked economics. Even where these mechanisms are not overtly disclosed as influencing outcomes, they can create structural incentives to favor certain execution paths over others.

From a regulatory perspective, this is where the line begins to shift. An interface that is compensated solely by the user for providing access and functionality can more plausibly be characterised as a neutral tool. Its incentives are aligned with usability and service provision. An interface whose revenues depend, directly or indirectly, on how transactions are executed begins to look different. It may still present itself as a passive layer, but its economic position more closely resembles that of a participant in the transaction flow.

In that sense, the staff is not only regulating conduct. It is indirectly regulating business models.

The message is clear: even in a system built on self-custody and smart contracts, the presence of transaction-based or flow-dependent compensation is a strong signal of intermediation. And once that signal appears, the characterisation of the interface as purely facilitative becomes significantly more difficult to sustain.

The Hard Boundary: Activities That Remain Broker-Like

The statement also delineates a set of activities that fall outside the scope of the non-objection position.

These include negotiating transaction terms, making recommendations, arranging financing, handling client assets, executing or settling trades, and taking or routing orders.

Taken together, these exclusions function as a negative definition of brokerage in the crypto interface context. They identify the functions that, if performed, would likely trigger registration requirements regardless of how the surrounding technology is described.

Governance and Disclosure as Structural Requirements

Notably, the framework does not rely solely on functional limitations. It also imposes expectations around governance, controls, and disclosure.

Providers are expected to implement policies for evaluating and monitoring integrated trading venues, to manage conflicts of interest, and to maintain transparency around system parameters, fees, limitations, and risks, including those associated with transaction ordering and maximal extractable value (MEV).

Disclosure, in this context, is not a peripheral compliance exercise. It is integral to maintaining the characterisation of the interface as a neutral tool rather than an opaque intermediary.

A Functional Approach to Software-Based Market Structure

Viewed holistically, the statement represents an attempt to translate longstanding securities law concepts into a software-mediated environment.

It does not reject the premise of self-custodial, user-directed transactions. Nor does it insist that every participant in a transaction flow be regulated as an intermediary.

Instead, it seeks to preserve the underlying logic of the broker-dealer regime, focused on control, influence, and economic incentives, while accommodating a different technological substrate.

The Emerging Design Constraint

For market participants, the practical implication is that regulatory analysis increasingly attaches not only to what a system does, but to how it is designed, monetized, and presented.

An interface that is architected as a neutral translation layer, funded by transparent user fees and governed by objective logic, may fall within the contours of the staff’s non-objection position.

An interface that embeds optimisation, steering, or monetization tied to transaction outcomes may not.

The distinction is subtle in form, but significant in consequence.

Conclusion

The staff statement does not resolve all uncertainties surrounding crypto asset securities and broker-dealer regulation. Its scope is limited, its authority is non-binding, and its future depends on further Commission action.

Nevertheless, it provides a structured way of thinking about a question that has often been framed too simplistically.

The issue is not whether an entity labels itself as a “front end,” nor whether its operations are “on-chain.”

The issue is whether, in substance, it acts as a participant in the transaction process or as an instrument through which the user acts.

And in that distinction, between participation and facilitation, the boundary of broker-dealer regulation continues to be drawn.