CFTC Passive Software Relief Opens Trading Apps Without Broker Registration

The CFTC expanded passive software relief beyond one company, giving qualifying app developers a path around broker registration under ten strict conditions. The September 17 decision covers software that connects users directly with regulated derivatives firms without holding assets or controlling individual orders. It creates a wider distribution channel for prediction markets, perpetual contracts, and other regulated products.

The shift matters because these developers can earn transaction-based fees, promote specific contracts, and introduce users to registered trading partners. Those activities have historically supported treating a business as an introducing broker. The CFTC now distinguishes the interface carrying an order from the regulated institution handling that order.

That distinction can put crypto wallets and consumer finance apps beside traditional brokerage channels. It also pressures registered exchanges and intermediaries to compete for distribution partnerships. Yet the relief is neither a blanket exemption nor a final rule. Providers must accept compliance duties, shared liability, and CFTC jurisdiction without receiving the certainty of permanent regulation.

The immediate precedent is Phantom, the crypto wallet developer that received company-specific relief in March 2026. Staff Letter 26-25 makes substantially similar treatment available to other eligible providers. The result is a broader experiment in deciding when financial software remains an interface and when it becomes an intermediary.

CFTC Passive Software Relief Extends Beyond Phantom

The CFTC changed who can rely on its non-enforcement position, not the underlying registration law.

The agency’s Market Participants Division issued Staff Letter 26-25 on September 17, 2026. The letter applies to qualifying passive software providers and relevant employees engaged in defined activities.

Staff will not recommend enforcement solely because those providers lack introducing broker registration. Relevant personnel also receive protection from enforcement over associated-person registration.

An introducing broker generally solicits or accepts derivatives orders for compensation but does not hold the customer assets supporting those trades. CFTC interpretations have historically treated that activity more broadly than physically receiving an order.

Paid referrals, customer solicitation, and per-trade compensation can all influence the registration analysis. A software interface can therefore resemble a broker when it promotes products, directs customers toward a partner, and earns money from resulting activity.

Staff Letter 26-25 recognizes that modern apps can perform those functions without making trading decisions. A qualifying provider supplies front-end software on a user’s device. The user transmits orders directly to a regulated firm through that interface.

The software provider cannot affirmatively participate in particular orders. It cannot generate explicit buy or sell signals. It also cannot exercise discretion over routing or execution.

Most importantly, the provider cannot hold, control, or take custody of user assets. Funds supporting derivatives positions remain with a registered futures commission merchant, clearing organization, or designated contract market.

This structure divides the customer experience into two layers. The app controls presentation and access, while regulated institutions retain onboarding, execution, clearing, and custody responsibilities.

The relief covers interfaces for event contracts, perpetual contracts, and other CFTC-regulated derivatives. It is not restricted to crypto wallets, a boundary the letter states explicitly.

Providers can offer a standalone interface or embed the feature inside an existing wallet. An embedded interface must clearly distinguish regulated derivatives activity from other functions.

The policy therefore reaches conventional financial applications as well as crypto products. A consumer platform could place regulated event contracts inside its existing interface without becoming an introducing broker, provided every condition is satisfied.

The provider can also market its partnership and promote available contracts. It can introduce users to particular registered firms. Users must remain free to access those firms without going through the software provider.

Revenue is allowed too. A registered partner can share relevant revenue with the interface provider, while the provider can charge users transaction-based fees.

Those permissions make the relief commercially useful. Earlier treatment for technology service vendors relied on narrower assumptions, including pre-existing customer relationships and limits on recommendations or connected compensation.

The CFTC announcement describes the new position as broadly available relief modeled on Phantom’s letter. That change turns a company-specific precedent into a potential distribution framework.

However, the agency did not “exempt” every non-custodial app from every financial rule. Staff offered a conditional no-action position covering two registration requirements and a defined set of activities.

That difference is central. A provider outside the letter’s boundaries cannot assume that avoiding custody alone removes its registration obligations.

Why Non-Custodial Trading Apps Gain a Distribution Advantage

The practical benefit is broader product distribution without forcing every consumer interface to become a full regulated broker.

A wallet or finance app already has a customer relationship, familiar navigation, and an established place on the user’s device. Adding regulated trading access can reduce the need for a separate account journey.

Under the covered model, the app presents market information and lets the user submit an order. The order travels directly to a registered partner. Assets and collateral remain inside regulated market infrastructure.

That arrangement can help designated contract markets and futures intermediaries reach customers through third-party software. Instead of building every consumer experience themselves, regulated firms can supply products behind specialized interfaces.

The opportunity is especially visible in prediction markets. Event contracts let traders take positions on measurable outcomes, including economic releases, elections, weather, and sports.

Consumer interest has encouraged finance apps to place these contracts beside stocks, options, and cryptocurrencies. Robinhood, Coinbase, crypto wallets, and other platforms have explored different routes into this market.

Robinhood illustrates why distribution matters. The company had more than 28 million funded customers when it expanded its prediction-market partnerships in September 2026. Its interface can expose event contracts to an audience that may never visit a dedicated exchange.

The CFTC’s action lowers one federal registration obstacle for similarly positioned apps. An eligible interface no longer needs introducing broker registration solely because it performs the covered marketing and access functions.

That benefit also reaches crypto derivatives. The letter specifically includes perpetual contracts, which are derivatives without a conventional expiration date.

A wallet could display a regulated perpetual product and transmit a self-directed order to its registered partner. The wallet could earn related revenue without taking custody of the collateral or selecting how the order executes.

The rule is not limited to self-custody in the ordinary crypto sense. Within this model, the provider remains non-custodial, but a regulated clearing organization or intermediary still holds funds supporting the derivatives position.

In other words, the software does not eliminate regulated custody. It relocates the customer interface while keeping assets and execution within the established derivatives system.

This separation creates a valuable distribution role. Consumer apps can focus on interface design, discovery, and customer acquisition. Registered partners handle functions carrying deeper capital, supervision, and market-integrity obligations.

For developers, that can narrow the compliance burden associated with launching a trading feature. It does not eliminate compliance work, legal review, or contractual risk.

For exchanges, the framework creates more potential storefronts. A regulated market can distribute the same products through multiple interfaces while retaining the direct customer or member relationship required by the letter.

For existing introducing brokers, the change creates competitive pressure. Some app providers can now perform valuable acquisition and marketing functions without obtaining the same registration.

That does not make the two business models identical. A traditional broker can undertake activities outside the letter’s narrow limits. Passive providers cannot advise users, direct particular orders, or handle assets.

The competitive question is whether those additional functions remain valuable to customers. If users mainly want discovery and one-tap access, the lighter interface model can capture significant traffic.

Registered brokers may respond by improving their applications, supplying infrastructure to more partners, or emphasizing advisory and execution services that passive software cannot provide.

The result is not simple deregulation. It is a new division of labor between the interface attracting the customer and the institution legally carrying the trade.

The Exemption Comes With Ten Compliance Conditions

Passive software avoids broker registration only by accepting controls that resemble parts of broker supervision.

Staff Letter 26-25 establishes ten conditions. Together, they limit who can rely on the relief and preserve enforcement routes when customer-facing conduct causes harm.

First, providers, principals, and people soliciting users cannot be subject to statutory disqualification without a staff waiver. A provider must notify the division if a covered person later becomes disqualified.

Second, users must receive disclosures about relationships between the software provider and registered partners. Those disclosures must address potential conflicts, including fees.

This condition matters because a supposedly neutral interface may earn more when users select certain products or partners. Revenue sharing can shape placement, recommendations, and promotional emphasis.

Third, users must acknowledge an applicable risk disclosure. The provider must retain evidence of that acknowledgement unless a registered partner already delivers the required statement.

Fourth, customers must onboard directly with the designated contract market, futures commission merchant, or introducing broker. They must also retain independent access to that institution.

A passive provider cannot become an unavoidable gatekeeper. The direct relationship helps keep the registered firm accountable for customer functions assigned to it.

Fifth, providers must adopt policies for public communications and marketing. Those policies must follow applicable CFTC and National Futures Association standards as though the provider were registered.

Sixth, the provider cannot run advertising that would require NFA pre-approval if it were an introducing broker. Marketing freedom therefore stops well before an unrestricted consumer advertising model.

These conditions constrain how apps describe event contracts and leveraged products. A polished interface cannot disguise risk, present misleading probabilities, or bypass rules governing promotional claims.

Seventh, the provider and each registered partner must sign an undertaking that creates joint and several liability for relevant legal violations. They must file that document with the CFTC division.

Joint and several liability means either party can face responsibility for the full covered violation. That obligation gives registered firms a strong reason to review their software partners carefully.

It also complicates claims that the provider is merely a neutral pipe. The app may avoid registration, but its conduct can still create direct financial exposure for both parties.

Partners will likely demand audit rights, marketing approval, data access, and termination protections. Contract negotiations may become a more meaningful barrier than the registration process itself.

Eighth, providers must maintain records about compliance and regulated activities under applicable CFTC recordkeeping standards. Product decisions, disclosures, promotions, and partner arrangements can therefore create reviewable evidence.

Ninth, providers must notify the division if they become insolvent or enter bankruptcy. Financial distress can interrupt interfaces, compromise records, and confuse customers about access to positions.

Tenth, each provider must file a notice accepting the conditions and consenting to CFTC investigation and enforcement jurisdiction. Certain government-affiliated providers may also need an enforceable sovereign-immunity waiver.

The notice requirement separates passive software relief from an automatic statutory exclusion. A developer must affirmatively enter the framework and accept the regulator’s reach.

These obligations make the policy more demanding than its headline suggests. Developers save the effort of becoming registered introducing brokers, yet still need compliance staff, legal controls, and partner oversight.

The relief also applies only when every covered activity stays within defined limits. A product update that adds trade recommendations or discretionary routing can change the analysis.

An app’s labels are not decisive. Calling a service non-custodial or passive will not protect conduct that gives the provider control over orders, assets, or investment decisions.

Product teams will need to treat architecture as a regulatory boundary. Custody permissions, routing logic, recommendation systems, and promotional tools all affect eligibility.

That creates a direct role for engineers. A technical feature can move the provider outside the letter even if the company’s contracts still describe it as software.

A Staff Letter Is Not Permanent Regulatory Certainty

The relief creates an operating path, but it does not settle the legal status of software providers through binding regulation.

Staff Letter 26-25 represents the Market Participants Division’s position. It does not bind the full Commission or another CFTC office.

The division can modify, suspend, restrict, or terminate its position. Changed or omitted material facts can also make the relief unavailable.

Its duration is expressly temporary. The position lasts until Commission rulemaking or guidance addresses introducing broker registration for software developers.

That limitation creates an unusual planning problem. Companies can build products under the framework, but future rules can impose different duties after integrations gain customers.

The relief also covers only introducing broker and associated-person registration tied to the specified activities. It does not erase anti-fraud rules, marketing standards, state disputes, or other federal requirements.

Software connecting users to unregistered markets falls outside the central model. Covered transactions must occur through designated contract markets and appropriate registered intermediaries.

Purely decentralized derivatives interfaces cannot assume that the letter protects them. The policy favors software distribution connected to regulated market infrastructure.

The distinction is also narrower than “software is not a broker.” Software qualifies only when the provider avoids custody, order-level involvement, trading signals, and routing discretion.

That line can become difficult when applications use personalization. A ranked market feed might reflect general engagement data, while an individualized recommendation can resemble a trading signal.

Notifications present another challenge. An alert reporting a price change differs from a message urging a particular user to buy before an event.

Artificial intelligence can blur the boundary further. A conversational assistant that explains contract mechanics may remain educational. One that recommends a position based on user data can exceed passive functionality.

Smart-order tools pose similar questions. Software that merely transmits a selected order looks different from software choosing the venue, timing, or execution strategy.

Providers must decide whether higher-conversion features justify losing the relief. That tradeoff can shape product design across wallets and online finance platforms.

Consumer protection remains the largest policy concern. Prediction contracts can appear simple because they often resolve to binary outcomes. Their legal structure and financial risks remain more complicated.

Critics argue that sports contracts placed beside investments normalize wagering as financial activity. Mick Mulvaney of Gambling is Not Investing told Axios that a football bet does not become an investment beside a retirement account.

State regulators have advanced a broader objection. They argue that sports-focused event markets operate like gambling businesses and should follow state licensing, age, and consumer-protection rules.

The federal dispute remains active. CFTC leaders have defended federal authority over regulated event contracts, while several states have pursued enforcement against Kalshi and Polymarket.

The state conflict concerns the underlying markets rather than passive software registration. Still, easier app distribution increases the stakes.

More interfaces can bring regulated event contracts to more users. That growth can strengthen the industry’s commercial position while giving state officials additional examples to challenge.

The CFTC has also signaled plans for broader prediction-market rules. Those proceedings can address product eligibility and market structure beyond the narrow registration issue in this letter.

The no-action position therefore solves one bottleneck inside an unsettled system. It lets qualifying software distribute regulated products, but it cannot guarantee that every offered contract survives other litigation.

Companies should also avoid treating the Phantom precedent as proof that their own architecture qualifies. Phantom’s original relief addressed a detailed factual model and imposed comparable safeguards.

Staff Letter 26-25 broadens access to that model. It does not broaden the model until every interface becomes eligible.

What Crypto and Prediction Markets Should Watch Next

The policy’s significance will depend on adoption, product boundaries, and whether temporary relief becomes durable regulation.

The first signal is the number and type of software providers that file notices under Letter 26-25. Public integrations will show whether the conditions support real product launches.

Large wallets are obvious candidates because they already serve self-directed crypto users. Consumer finance applications and specialist trading interfaces can also use the framework.

Adoption by several recognizable apps would confirm that the letter created a meaningful distribution channel. Limited adoption would suggest that liability, marketing controls, or partner requirements remain too demanding.

The quality of registered partnerships matters as much as their number. Major exchanges and futures intermediaries have compliance systems that can support customer onboarding, custody, and supervision.

Smaller providers may offer more attractive economics but create greater operational risk. Apps must assess whether each partner can maintain access, clearing, disclosures, and customer support.

The second signal is how developers define passive behavior in production. Interfaces will test boundaries through rankings, notifications, education, and personalization.

A straightforward order-entry screen fits comfortably within the letter. A feed optimized around user behavior creates harder questions about encouragement and recommendations.

The CFTC’s response to such features will reveal whether “passive” describes technical control or a broader customer-influence standard. Enforcement, interpretive guidance, or private staff discussions can shape that answer.

Providers should watch marketing review closely. The letter permits promotion of particular derivatives but subjects communications to broker-like conduct standards.

That combination is commercially valuable and legally delicate. Aggressive campaigns can generate volume while creating the evidence needed to question eligibility or allege misleading conduct.

The third signal is formal rulemaking. A Commission proposal would show whether staff’s ten-condition structure serves as a bridge or a blueprint.

A final rule resembling the letter would improve durability and let developers plan longer product cycles. Materially tighter rules would weaken the current distribution thesis.

The political composition of the Commission can affect that outcome. Staff relief is easier to change than a rule adopted through notice, public comment, and a Commission vote.

Industry comments will likely focus on custody, recommendations, compensation, and liability. Consumer advocates can press for clearer standards around sports contracts, young users, and gambling-like promotion.

Developers should also track the legal fight over event contracts. The Supreme Court, appellate courts, or state enforcement actions can reshape the products available through these interfaces.

Robinhood’s expansion shows that large consumer platforms are proceeding despite that uncertainty. Its partner strategy spreads distribution across multiple market providers.

Other apps may adopt the same approach. Multiple partnerships can reduce dependence on one exchange, but the letter does not permit providers to exercise discretion over individual routing.

That constraint can force users to select the underlying venue or require predetermined routing rules that do not involve order-level judgment. Implementation details will determine whether aggregation remains practical.

Traditional brokers should watch customer acquisition costs and interface engagement. If passive providers deliver substantial order flow, registered firms can become infrastructure suppliers behind consumer brands.

They can also defend their position with integrated research, advice, execution quality, and account services. Those features extend beyond the passive model and may justify the heavier regulatory structure.

Users should ask a simpler set of questions before trading. Which registered entity holds the assets, executes the order, and provides account support?

They should also inspect revenue disclosures. A platform’s contract placement may reflect compensation arrangements rather than a neutral assessment of usefulness.

Clear labeling matters when a wallet mixes unregulated crypto activity with regulated derivatives. The letter requires conspicuous separation, but interface design determines whether that distinction is understandable.

The CFTC passive software relief ultimately draws a narrow line around financial intermediation. A developer can build the storefront without becoming the institution behind every transaction.

That line opens a substantial product opportunity. It also places responsibility on developers to keep custody, advice, routing discretion, and misleading promotion outside the software layer.

The next few months should reveal whether companies can preserve that discipline while competing for engagement. Watch filed notices, live integrations, and any CFTC move toward permanent rules.

For users, the key action is to look past the app’s familiar interface. Verify the registered partner, understand who holds the collateral, and review how the platform gets paid.