About a-team Marketing Services
The knowledge platform for the financial technology industry

A-Team Insight Blogs

Passive Software Providers: Opportunities and Obligations under the CFTC’s New Guidance

Subscribe to our newsletter

Passive software providers have an opportunity to play an active role in providing access to derivatives markets. But that role could be short-lived.

In a no-action letter issued in September of this year by Commodity Futures Trading Commission (CFTC) staff, qualifying Passive Software Providers (PSPs) were granted the opportunity to connect customers with CFTC-regulated derivatives markets without violating the requirement to register with the Commission as introducing brokers (IBs). The relief granted by Staff Letter 26-25 offers a new route to market, subject to a set of “registration-lite” conditions. As a cautionary note, however, this relief does not have a permanent regulatory foothold. CFTC staff can modify or withdraw it, and future CFTC leadership may decide to take a different approach.

For now, the relief creates new opportunities for technology or wallet provider firms seeking to connect their existing customer bases with regulated derivatives products, including prediction markets. It also permits certain marketing activities and transaction-based compensation arrangements that were restricted under earlier CFTC guidance.

However, as noted above, Staff Letter 26-25 comes with substantial compliance obligations, including a requirement for registered partners to accept joint-and-several liability for specified violations involving PSP activities.

Dorothy DeWitt and Carl Kennedy discuss the significance of the new framework, its practical implications for market participants and the decisions firms should consider before pursuing PSP relief. DeWitt is founder and CEO of Tölt Strategies, former Director of the CFTC’s Division of Market Oversight and former General Counsel of Coinbase. Kennedy is a partner and head of commodities and derivatives at Dechert, and a former senior counsel and policy advisor at the CFTC.

What led the CFTC to issue its recent no-action relief for Passive Software Providers, and what has changed?

Carl Kennedy: The CFTC has been grappling with the regulatory treatment of technology service providers for nearly 20 years. In 2006 and 2008, the agency issued interpretive guidance establishing conditions under which firms providing trading interfaces to registered intermediaries would not be considered IBs. That guidance was fairly restrictive, particularly around things like customer relationships, marketing, and compensation.

As technology evolved, those restrictions became increasingly difficult to reconcile with how modern trading applications operate. The growth of crypto wallets, prediction markets and other front-end interfaces brought the issue into sharper focus. In March, the CFTC granted no-action relief specifically to Phantom Technologies, a crypto wallet provider. Now, the September letter has extended comparable relief to qualifying software providers more broadly, across CFTC-regulated derivatives products.

There’s an important legal distinction between the old guidance and the new relief. The earlier letters interpreted certain activities as falling outside the definition of an IB. The September 2026 letter doesn’t further interpret that definition. Instead, CFTC staff are now saying they won’t recommend enforcement for failure to register as an IB or associated person when a provider engages in specified activities, as long as they satisfy the relevant conditions.

Dorothy DeWitt: To me, one of the changes that really stands out is the treatment of compensation. The earlier guidance placed restrictions on fees tied to trading activity, which made it difficult for some providers to establish viable business models. The new letter permits transaction-based fees and revenue-sharing arrangements, subject to its conditions. That makes the opportunity much more commercially attractive.

What kinds of businesses stand to benefit most from this relief?

DeWitt: I believe the opportunity is quite broad. Perhaps the most obvious group includes front-end developers, trading interfaces and wallet providers that already have significant customer bases. They can now potentially introduce those customers to CFTC-regulated markets without first going through the IB registration process.

But consider a company that isn’t traditionally involved in financial services at all. – lLet’s say an airline has a large loyalty program and wants to offer its customers access to prediction markets through an existing application or even an in-flight entertainment system. That’s purely hypothetical, but it illustrates the possibilities. The company has an established relationship with its customers and may see an opportunity to monetize that relationship by connecting them to a registered exchange.

Under the new framework, a company could bring this kind of offering to market much more quickly and receive transaction-related compensation. That’s a significant benefit for a firm that wants to explore the opportunity before committing to becoming a registered financial intermediary.

Kennedy: I would add that while newer categories like crypto or prediction markets are getting the lion’s share of the attention, the opportunity goes beyond them. The September letter is technology-neutral and applies across CFTC-regulated derivatives products, including traditional futures and options on futures. We’re potentially broadening the distribution of regulated derivatives through an entirely different set of customer interfaces.

What activities are actually permitted for Passive Software Providers, and where does the CFTC draw the line?

Kennedy: Here’s where I think the word “passive” is a bit of a misnomer. It doesn’t mean the provider has to be commercially inactive. A PSP can still market its services, advertise the availability of specific derivatives contracts, promote its relationships with particular registered entities, introduce customers to those entities, and receive compensation related to trading activity.

Where the passivity comes into play is the actual trading process. The software can enable customers to review their positions and submit orders directly to a registered entity. But the PSP cannot affirmatively handle individual orders, generate express buy, or sell signals or exercise discretion over routing or execution. It also cannot take custody or control of the assets securing customers’ positions. The customer needs to retain control over those trading decisions and the ability to access the registered entity independently of the PSP.

DeWitt: That’s certainly true for the commercial side of things. I think it’s worth emphasizing that the requirements aren’t particularly passive from an operational perspective, either. The PSP may have to build processes for disclosures, onboarding and recordkeeping that it never needed before.

A software company or loyalty program might be accustomed to marketing products to customers, but that doesn’t mean it has experience providing financial risk disclosures or documenting potential conflicts of interest. Those requirements are part of the cost of operating under this framework.

What should prospective PSPs understand about the compliance requirements that accompany the relief?

DeWitt: The letter sets out ten conditions that firms need to consider carefully. PSPs must disclose their relationships with registered partners, along with any potential conflicts of interest. They also need to ensure customers receive appropriate risk disclosures and maintain records of their acknowledgments.

There are additional requirements around marketing and recordkeeping, as well as notices and undertakings that must be filed with the CFTC. Depending on the arrangement, certain obligations may be satisfied by the registered intermediary rather than the PSP itself.

For a company that’s never operated in a regulated financial environment, meeting these requirements can involve a significant investment. It may need to establish entirely new compliance processes and determine which responsibilities can be handled by its registered partner. And those controls need to work in practice, not just exist on paper.

Kennedy: I think it bears repeating that the relief doesn’t remove the need for regulatory accountability. The provider must agree to the conditions and consent to CFTC jurisdiction in connection with its covered activities. Also, the registered partner has obligations of its own. The undertaking required by the letter creates an additional reason for that partner to be concerned about the PSP’s conduct and its ability to operate consistently with the conditions of the relief.

How significant is the joint-and-several liability requirement, particularly for exchanges and other registered firms considering PSP partnerships?

Kennedy: I think this is one of the most consequential aspects of the entire letter, and perhaps one that hasn’t received enough attention. Under the required undertaking, the PSP and each participating registered entity agree to be jointly and severally liable for violations of the Commodity Exchange Act or CFTC regulations committed by the PSP or its personnel in connection with the covered activities.

That’s a serious commitment. An exchange, FCM or IB may see tremendous commercial value in partnering with a software provider that can introduce new customers, but it also has to consider the regulatory exposure and long-term supervision associated with that relationship.

That raises significant questions around partner selection. What do you know about the PSP? Does it have adequate compliance resources? Can you demonstrate that you’ve conducted appropriate diligence and established a process for ongoing oversight?

DeWitt: Exactly. Exchanges and intermediaries generally want to attract more customers and increase trading activity. But they’re also managing their existing regulatory obligations, and their resources aren’t unlimited. So, they have to consider whether a particular PSP brings enough value to justify taking on the additional risk.

I am doubtful that we’ll see exchanges immediately entering into these arrangements with dozens of PSPs. There’s a substantial amount of work associated with taking on joint-and-several liability, and they’re going to be selective.

That means due diligence is incredibly important. A PSP needs to demonstrate that it has the right controls and resources in place to be an attractive partner. And the review may not end when the agreement is signed. Registered firms may want independent assessments every six months or annually, for example, to help manage their ongoing exposure.

For a company considering this pathway, how should it evaluate PSP relief against registering as an introducing broker?

DeWitt: I would start by asking what the company is trying to accomplish and how quickly it wants to get to market. If the priority is speed, and the company has an attractive customer base and a registered partner willing to work with it, PSP relief could be an excellent option. It allows the company to begin operating and test the economics of the business without immediately pursuing IB registration.

But the partnership requirement can also become an obstacle. A firm might spend three or four months approaching exchanges and intermediaries, only to find that nobody is willing to take on the liability. Depending on its circumstances, it might have been better off pursuing IB registration from the beginning.

Kennedy: I agree. IB registration is comparatively lighter touch than some other CFTC registration categories, but it still carries meaningful operational and compliance obligations. A firm has to be prepared for ongoing oversight by the CFTC and the National Futures Association (NFA).

At the same time, a PSP arrangement creates its own obligations, including accountability to the registered partner. Ultimately, it is a tradeoff: the price of registration relief is accountability.

How durable is the no-action relief, and what should firms be thinking about as the regulatory framework continues to evolve?

Kennedy: The first thing I’d emphasize is that firms shouldn’t necessarily view this as a permanent solution. This is a staff no-action letter reflecting the policy priorities of the current CFTC leadership. It can be modified or withdrawn, and a future administration may take a different approach. Any company looking to build a long-term business around the relief should be well aware of that reality.

I would encourage firms to think about PSP status as a potential first step into CFTC-regulated markets. It gives them an opportunity to establish a business, understand the regulatory environment and determine whether they want to make the longer-term commitment associated with IB registration.

Some companies may decide the business justifies that investment. Others may find that the opportunity isn’t substantial enough to warrant becoming a registered intermediary.

DeWitt: One advantage of taking that approach is that much of the work a PSP does to establish its compliance program will also be useful if it ultimately decides to register as an IB. The disclosures, policies and procedures, recordkeeping and other controls required under the PSP framework are consistent with many of the broader obligations a registered intermediary would face. So, the company isn’t necessarily starting over when it decides to pursue registration.

I think that’s a sensible way to evaluate this opportunity. The letter provides a potentially valuable route to market, but firms should consider the strength of their proposed partnerships, their ability to operate compliantly and whether the business makes sense over the longer term.

The opportunity is significant, but the circumstances of each individual firm will ultimately dictate whether PSP relief is the right approach.

Subscribe to our newsletter

Related content

WEBINAR

Recorded Webinar: Generative and Agentic AI in Financial Markets: What the Data Really Shows

Artificial intelligence is reshaping financial markets – but the reality on the ground is more nuanced, more uneven, and more instructive than the headlines suggest. A new A-Team Insight research programme, drawing on responses from senior AI decision-makers at buy-side and sell-side institutions across the USA, UK and Canada, reveals a market in transition: from...

BLOG

Smarsh and AWS Target the Governance Gap in AI-Powered Surveillance

Smarsh recently reported what it describes as breakthrough results from its collaboration with Amazon Web Services (AWS), including a 77% reduction in compliance review workload at one global investment bank. The three-month deployment analysed millions of alerts and, according to Smarsh, produced a 2% decline in true positives. The results provide an early test of...

EVENT

TEST Event page 2

Now in its 15th year the TradingTech Summit London brings together the European trading technology capital markets industry and examines the latest changes and innovations in trading technology and explores how technology is being deployed to create an edge in sell side and buy side capital markets financial institutions.

GUIDE

Regulatory Data Handbook 2026 – Fourteenth Edition

Welcome to the fourteenth edition of A-Team Group’s Regulatory Data Handbook. Supervisors increasingly expect firms to demonstrate which rules apply, which data supports each obligation, who owns the control and how exceptions are identified and resolved. Policies and implementation programmes must now be supported by records that can withstand regulatory scrutiny. This edition examines material...