SEC and CFTC jointly release cryptocurrency front-end guidelines: operating without broker licenses in specific scenarios

The trading process of crypto assets involves multiple technical layers, with user-facing interfaces at the forefront. These interfaces—including websites, browser extensions, mobile applications, and software embedded in self-custodied wallets—serve the function of converting user-set trading parameters into on-chain executable instructions. However, whether such interfaces constitute legally defined “brokers” has long remained unclear.

The regulatory jurisdiction of the U.S. Securities and Exchange Commission (SEC) and the Commodity Futures Trading Commission (CFTC) overlaps in the crypto space. The SEC exercises oversight over securities-type crypto assets trading under the Securities Act, while the CFTC oversees crypto derivatives and commodity-type crypto assets under the Commodity Exchange Act. This dual-regulation structure results in crypto front-end interfaces facing dual uncertainties in compliance pathways.

On April 13, 2026, the SEC’s Division of Trading and Markets issued a staff statement providing clear guidance on whether “covered user interfaces” need to register as broker-dealers. The statement defines “covered user interfaces” as websites, browser extensions, or software applications that assist users in initiating crypto asset securities transactions on blockchain protocols. Meanwhile, the CFTC, earlier on, responded to the compliance pathways for self-custodied wallets accessing derivatives markets through no-action letters and other means. The coordinated actions of these two agencies on crypto front-end issues mark a key turning point in the shift from scattered enforcement to the development of a systematic regulatory framework in the U.S.

How are Covered User Interfaces Defined and Regulatory Boundaries Drawn?

The SEC staff statement first clarifies the scope of “covered user interfaces.” The definition covers three types of platforms: websites, browser extensions, and software applications, including those embedded within self-custodied wallets. Their core function is to assist users in preparing and transmitting crypto asset securities trading instructions. Typical operational flow involves: users set trading parameters on the interface, which then converts these parameters into blockchain-readable instructions; users sign and submit these instructions via self-custodied wallets to the on-chain protocol.

This technical delineation has significant legal implications. The statement explicitly limits the function to “assisting in preparing trades,” not “executing or matching trades.” This means that software tools merely facilitating information conversion between users and blockchain protocols generally do not fall under the definition of “broker” as per Section 15 of the Securities Exchange Act. However, the statement emphasizes that this exemption applies only to providers meeting specific conditions; any activities beyond “assisting in preparation”—such as matching trades, custody of funds, order routing, or providing investment advice—are excluded from the exemption.

The SEC and CFTC maintain consistency in this delineation. On March 17, 2026, the CFTC publicly confirmed that it would implement the SEC’s interpretive framework under the Commodity Exchange Act, clearly distinguishing between securities-related and commodities-related regulation. This coordination mechanism is not temporary—both agencies signed a memorandum of understanding on March 11, 2026, establishing a formal institutional framework for inter-agency coordination, providing a unified approach to cross-jurisdictional front-end regulation issues.

What Operational Conditions Must Be Met for Broker Registration Exemptions?

The SEC staff statement offers a conditional exemption pathway for crypto front-ends, but it requires providers to strictly adhere to multiple operational constraints. These conditions collectively emphasize a core principle: the interface must maintain technological neutrality and not act as a financial intermediary.

Specifically, the exemption conditions include seven dimensions. The interface must not actively solicit users for specific crypto asset securities trades. It must not provide investment advice or any information that could be viewed as trade recommendations. It must not hold or custody user funds. It must not execute orders or decide on trade routing on behalf of users. It must employ objective pricing and routing logic. Compensation must be fixed and unrelated to routing choices. Full disclosure of fee structures, potential conflicts of interest, and associated risks must be provided to users.

In multi-routing scenarios, more specific requirements apply. If the interface connects multiple execution paths or liquidity sources, it must allow users to sort or filter options based on objective criteria (such as price or speed), and it must not label any route as “best” or “most reliable.” Additionally, the interface must not use marketing language like “best price” to influence user trading decisions or execution paths.

These conditions aim to clearly delineate the functional role of crypto front-ends as technical tools versus their role as financial intermediaries. Interfaces can display market data, asset prices, and estimated Gas fees, and can charge transparent trading fees, but cannot intervene in trading decisions through routing choices, price optimization, or investment advice.

Why Is Fee Structure Neutrality Central to Compliance?

Fee structure design is one of the key dimensions scrutinized by the SEC. The staff statement requires that the compensation for covered user interfaces must be both fixed and unrelated to routing choices. This means providers cannot earn differential commissions based on guiding users toward specific counterparties, liquidity pools, or execution paths.

The rationale is to prevent conflicts of interest. If the interface’s revenue depends on trade destinations, it creates an economic incentive to steer users toward paths that benefit the provider rather than the user’s best interests, undermining its role as a neutral technical tool. The SEC explicitly states that interfaces earning variable commissions based on trade direction, token selection, or routing destination may not qualify for the safe harbor.

This constraint is especially relevant for aggregation wallets or DeFi front-ends. The requirement for “objective routing and pricing logic” implies that any interface that directs users to specific pools or protocols for revenue reasons risks being classified as a broker-dealer. Therefore, fee neutrality is not only a technical parameter but a core factor in determining the legal classification of the interface.

How Does the Five-Year Window Affect Front-End Developers’ Compliance Planning?

The SEC staff statement explicitly states that it is temporary. Absent further action by the Commission, this staff guidance will automatically expire five years after April 13, 2026. This timeframe provides a limited but clear horizon for crypto front-end developers’ compliance planning.

From a developer’s perspective, the five-year window has dual implications. On one hand, it offers a predictable compliance pathway. DeFi front-ends, wallet extensions, and mobile apps that have long operated in regulatory gray areas can now operate under a clear conditional framework without risking enforcement as unregistered brokers. On the other hand, the five-year limit means compliance planning must consider the time constraint—this safe harbor is not permanent, and future legislation or formal rules could alter the current standards.

The SEC also solicited market feedback on the content of this guidance, indicating that the framework remains evolving. The statement itself is not a formal rule but guidance issued by staff, lacking the same legal authority as formal regulations. This means that Congress’s ongoing efforts to pass comprehensive crypto legislation—including the Market Structure Act, which aims to clarify SEC and CFTC jurisdiction—may significantly influence the future of front-end regulation.

How Does CFTC’s Parallel Action Cover Derivatives Trading Front-Ends?

Alongside the SEC’s front-end guidance, the CFTC has taken parallel steps. On March 17, 2026, the CFTC’s Market Participants Division issued a no-action letter to Phantom Technologies, allowing the self-custodied wallet to connect users to CFTC-regulated derivatives markets under ten specified conditions without registering as an introducing broker.

The conditions are instructive. They permit the wallet to display market data and directly submit orders for CFTC-regulated derivatives such as event contracts and perpetual swaps to partner platforms. The wallet must not hold user assets or exercise discretion over routing or execution. The ten conditions include requirements for user disclosures, direct access to partner platforms, marketing controls, record-keeping, bankruptcy notifications, and joint liability commitments.

While targeted at specific entities, the logic of the CFTC’s action aligns closely with the SEC’s front-end guidance: both rely on non-custodial, non-discretionary, transparent information as compliance prerequisites. Notably, the CFTC Chair publicly stated that the agency is working with the SEC to modernize rules to ensure that on-chain software systems and front-ends find clear regulatory placement within the U.S. framework.

How Do New Front-End Regulations Impact Different Platform Models?

The impact of the new regulations varies significantly across different types of front-ends, exhibiting a layered effect.

Pure information display interfaces face minimal resistance. Platforms that only show market prices and allow users to independently construct trades are unlikely to be classified as brokers under the core definition, and their compliance costs are relatively low. Such interfaces already have a relatively clear compliance position under the current framework.

Aggregators that optimize routing or recommend trades face the greatest challenge. These interfaces, which promote decentralized trading access within the ecosystem, may need redesigns to meet SEC’s neutrality standards. Their business models—pushing liquidity into pools and offering optimal routing—conflict with SEC’s prohibition on deciding trade routes or labeling routes as “best.”

Centralized platforms already registered as broker-dealers are largely unaffected by this guidance. The guidance mainly targets non-custodial, unregistered crypto front-ends operating in regulatory gray areas, not established traditional market participants.

In derivatives, the CFTC’s no-action letter provides a compliance template for specific entities. Other wallet providers seeking similar exemptions may need to follow the same conditions, making the CFTC’s ten conditions a potential industry standard for non-custodial wallets accessing derivatives markets.

Legal Effect of Staff Guidance and Future Legislative Directions

Understanding the legal status of the SEC staff statement is crucial. The guidance is not a formal rule and does not have the same binding legal effect as regulations. It reflects the staff’s interpretation of the existing Securities Act’s broker definition but is not issued through a formal rulemaking process.

This legal position entails multiple limitations. The staff guidance does not bind courts—federal courts can independently determine whether particular crypto assets qualify as securities or whether specific interfaces constitute brokers. The SEC itself can update, modify, or abandon this guidance without going through formal rulemaking. The staff explicitly states that the SEC may further refine or revise this guidance based on public feedback.

Meanwhile, Congress is advancing comprehensive crypto legislation. The Senate’s key committees are expected to vote on the Market Structure Act, which aims to clarify SEC and CFTC jurisdiction and establish a unified regulatory framework for exchanges and market participants. The White House’s digital assets advisor notes that the previously perceived “difficult-to-resolve” crypto regulatory disagreements have significantly diminished, improving prospects for passage. If enacted, such legislation would elevate the regulatory coordination between SEC and CFTC from administrative memoranda to statutory law.

Summary

The series of actions by the SEC and CFTC around crypto front-end regulation in 2026 marks a shift from a fragmented enforcement approach to the development of a systematic regulatory framework in the U.S. The SEC staff guidance provides a conditional broker registration exemption for covered user interfaces, with core constraints including non-custodial, non-discretionary, fee-neutral, and fully disclosed operations. This exemption is temporary, offering a five-year window. The CFTC’s parallel no-action letter for derivatives access and the memorandum of understanding between the agencies establish institutional coordination. While not legally binding as formal regulations, these guidance documents offer the clearest current reference for compliant crypto front-end operation. Future legislation will determine the final shape of this regulatory framework.

FAQ

Q1: What types of software products are included as covered user interfaces?

Including websites, browser extensions, mobile applications, and software embedded in self-custodied wallets. Their core function is to assist users in converting set trading parameters into executable blockchain instructions.

Q2: What are the core conditions for crypto front-ends to qualify for broker registration exemptions?

Core conditions include: not soliciting specific trades, not providing investment advice, not holding user funds, not executing orders or deciding routing, employing objective pricing and routing logic, fixed fee structures unrelated to routing, and full disclosure of fees, conflicts, and risks.

Q3: Will the exemption automatically expire after the five-year window?

If the SEC does not take further action, the staff guidance will automatically expire five years after April 13, 2026. Future formal rules or legislation could establish new frameworks before then.

Q4: What role does the CFTC play in regulating crypto front-ends?

The CFTC oversees crypto derivatives and commodity-type crypto assets. It has issued a no-action letter allowing certain self-custodied wallets to connect users to regulated derivatives markets under specified conditions, and is working with the SEC to modernize rules for on-chain software and front-end regulation.