The US Commodity Futures Trading Commission issued Staff Letter 26-25 on September 17, 2026, extending no-action relief to developers of passive crypto trading software who satisfy ten mandatory conditions. Under the letter, CFTC staff will not recommend enforcement against these developers for failing to register as introducing brokers (IBs), a category of licensed financial intermediary, so long as providers meet those ten specified conditions. The move creates the first broadly available no-action position for software firms building front-end interfaces to CFTC-regulated derivatives markets.

The full text of Staff Letter 26-25 was not publicly accessible at the time of publication; specific claims about the letter's conditions and scope are drawn from secondary reporting and legal analysis.

The relief applies narrowly to what the agency defines as "passive software providers": companies that build and distribute interface software allowing users to submit orders directly to registered futures commission merchants (FCMs), introducing brokers (IBs), and designated contract markets (DCMs), without the developer touching customer funds, generating trade signals, or exercising any discretion over individual transactions.

Developers who go beyond that boundary remain subject to full IB registration requirements under the Commodity Exchange Act. The letter draws a material distinction between recommending specific regulated trading venues, which is permitted under certain conditions, and generating trade signals or exercising order discretion over individual transactions, which remain prohibited and trigger registration obligations.

---

The letter expands a precedent the agency set six months earlier. In March 2026, the CFTC issued Staff Letter 26-09 exclusively to Phantom Technologies, the self-custodial crypto wallet company, after Phantom sought to integrate derivatives access into its product. Phantom's request raised two novel legal questions: whether a software provider could recommend specific regulated trading partners (DCMs and FCMs) to users, and whether it could receive revenue-sharing payments from those partners. Both activities had previously been off-limits for software vendors without an IB license. The September letter extends comparable terms to the broader industry, with the same joint-liability requirement: any developer accepting the relief must execute a written agreement with its registered counterparties making both parties jointly and severally liable for violations of commodity law.

---

Legislative failure accelerated the agency's hand. The Digital Asset Market CLARITY Act, a comprehensive US crypto market-structure bill that passed the House in July 2025, failed a Senate cloture vote on September 15, falling short of the 60-vote threshold needed to advance. The vote was 49 to 50.

All Democratic senators and three Republicans voted against it. CFTC Chairman Michael Selig indicated, according to reporting from CryptoTimes, that the agency would proceed using its existing statutory authority rather than waiting on Congress.

The staff letter followed two days later. Jones Day's analysis of the Senate vote described it as eliminating any realistic prospect for comprehensive digital asset legislation in 2026, leaving administrative tools like no-action relief as the primary mechanism for regulatory clarity in the near term.

---

The CFTC is not acting in isolation. In April 2026, the SEC's Division of Trading and Markets published a parallel statement exempting what it called "Covered User Interface Providers" from broker-dealer registration when those interfaces facilitate crypto asset security transactions. That relief carries a five-year sunset clause.

Together, the two agencies are sketching out a functional category of software infrastructure that is non-custodial, passive, and disclosure-compliant, sitting outside the traditional licensed-intermediary framework.

---

Outside the United States, the practical reach of the letter is limited but its signal value is real. Developers based in Nigeria, Kenya, or India who build passive order-routing tools for US-regulated derivatives venues could technically qualify for the relief, but Condition 10 requires filing a notice with the CFTC and formally submitting to the agency's jurisdiction. That is a meaningful legal commitment for a team operating from Lagos or Nairobi under a different domestic regulatory regime.

Indian developers face additional complications beyond Condition 10. India has no SEBI-approved crypto derivatives market, and the country's 30 percent VDA tax, 1 percent TDS regime, and RBI capital flow oversight create independent compliance considerations for teams building for global platforms.

It is also worth noting that South Africa's Financial Sector Conduct Authority has proposed a ban on crypto derivatives and contracts for difference (CFDs) for retail clients, which would create a direct conflict for developers trying to serve both markets. That proposal sits in tension with the FSCA's existing licensing framework: VALR, South Africa's largest exchange by volume, holds an over-the-counter derivatives provider license from the FSCA granted in October 2025. The coexistence of institutional derivatives licensing and a proposed retail ban means the regulatory picture for South African-market developers is more nuanced than a simple prohibition, and affects how those developers assess the viability of serving that market.

---

The regional stakes are not trivial. Sub-Saharan Africa recorded $205 billion in on-chain transaction volume between July 2024 and June 2025, a 52 percent increase year over year, according to Chainalysis data. Nigeria alone accounted for $92.1 billion of that total. Kenya now has more than 6 million active crypto users, and VALR in South Africa counts more than 1.7 million registered users. The developer communities in these markets are actively building for global platforms, and US regulatory design decisions shape what products they can realistically bring to market. The convergence of SEC and CFTC no-action positions is enabling a "super app" model, where single interfaces provide multi-venue access to regulated derivatives. That architecture is particularly well-suited to the mobile-first ecosystems dominant across sub-Saharan Africa and South Asia, making the practical implications of US regulatory design more immediate for non-US developers than the letter's geographic framing might suggest.

---

Going forward, the CFTC's letter should be read as a template rather than a resolution. The conditions attached to the relief, particularly the disclosure, record-keeping, and joint-liability requirements, function as a provisional compliance framework while Congress remains deadlocked on broader legislation. That framework carries important limitations: no-action relief binds only the issuing division's enforcement recommendations, is not a formal rule, and can be withdrawn. The protections it offers depend on continued staff discretion rather than any statutory guarantee. For now, developers building passive crypto trading infrastructure have their clearest signal yet that the US regulatory posture has shifted from enforcement to accommodation, provided they stay strictly on the passive side of the line.