Third-party apps just gained a sanctioned, direct route into regulated prediction markets. On September 17, 2026, the CFTC’s Market Participants Division handed down a broad CFTC passive software exemption, and it changes something specific: software providers can now steer users toward registered exchanges without registering as introducing brokers in their own right. For wallets, terminals, and referral apps that have wanted to work with platforms like Kalshi, this removes one of the thickest legal walls standing in the way.
What the CFTC Actually Did
CFTC Staff Letter No. 26-25 spells out the mechanics behind the relief. Staff at the Market Participants Division committed to not recommending enforcement action against qualifying software providers, or their employees, over a failure to register as an introducing broker or as an associated person of one.
This framework didn’t appear out of nowhere on September 17. Back in March 2026, the CFTC piloted the same core idea on a single company, granting Phantom Technologies a no-action letter that let its self-custodial wallet route users into CFTC-regulated derivatives — event contracts among them — without the wallet itself becoming a licensed broker. September’s letter takes that one-company blueprint and opens it to an entire class of providers that fit the definition, rather than keeping it locked to a single business.
The procedural shift here matters just as much as the underlying policy. Under a company-specific letter, every new applicant has to petition the division separately, sit through staff review, and hope its product lines up closely enough with what came before. A class-wide letter skips that whole queue: any provider that satisfies the stated conditions can rely on the relief immediately, with no need to request its own custom sign-off — a real advantage in a market where dozens of wallets, terminals, and dashboards are all trying to move fast.
Who Counts as “Passive Software”
The CFTC kept the definition deliberately tight. To qualify, a provider builds front-end software that sends user orders straight to registered futures commission merchants, introducing brokers, or designated contract markets — and does nothing beyond that. Holding user funds disqualifies a provider outright. Generating buy or sell signals disqualifies it too. So does exercising any discretion over how or where an order gets routed.
Anything that resembles active trading advice or fund management sits outside this category by definition. Tools that just display available markets and pass along a user’s click toward a regulated exchange sit inside it. Analytics dashboards, wallet interfaces, and referral hubs all clear that bar as long as they stay on the display-and-forward side of the line.
Concretely, the category covers things like mobile trading front-ends, browser extensions that surface live prices, portfolio trackers that link out to a brokerage’s order form, and bot interfaces on Discord or Telegram that simply relay a command to a registered venue. The thread connecting all of them: the software never touches user money and never decides what someone should trade — it only shortens the distance to the regulated exchange.
Ten separate conditions still stand between a provider and this exemption. Among them: filing a notice with the CFTC, disclosing any relationship or conflict of interest with the brokers it connects users to, running compliance policies comparable to a registered introducing broker’s, and accepting the agency’s enforcement jurisdiction if something goes wrong down the line.
Compare that to full introducing broker registration, which takes real time and real money — National Furures Association membership, minimum net capital or guarantee requirements, background checks on every principal, and a supervisory and recordkeeping program built for a regulated brokerage. Letter 26-25 trades that heavier process for a lighter one; oversight doesn’t disappear, which is exactly why the letter reads more like a compliance checklist than a blanket pass.
Why This Matters for Kalshi and Polymarket
Kalshi already carries CFTC registration as an exchange, and Polymarket has spent recent months rebuilding its US compliance footing around a registered entity it acquired. Neither platform can grow past its own app without outside distribution partners. Before this letter existed, any app, website, or referral service that funneled users into a regulated exchange ran a real risk: regulators could treat it as an unregistered introducing broker, and untangling that meant a slow, expensive registration process that scared consumer brands away from partnering up at all.
Distribution sits at the center of what changed. Regulated exchanges don’t just compete with each other for order flow — they’re up against offshore and decentralized venues that never had to think twice about introducing broker status. A cleaner route for third-party apps to send volume toward CFTC-registered markets narrows that competitive gap, letting Kalshi and Polymarket-adjacent DCMs plug into wallets and terminals traders already use instead of building every distribution channel from scratch themselves.
Apps built around leaderboards, wallet tracking, or trading terminals can now point users toward regulated exchanges without carrying that registration weight, provided they hold the line on staying passive. Our guide to Polymarket trading terminals walks through the mechanics of one such tool, and that same passive-display-versus-active-discretion boundary now shapes how products like it get designed going forward.
Developers working directly against exchange APIs run into the identical boundary. Our overview of the Polymarket API covers what data access looks like today; this relief operates one layer above that — at the interfaces users click on, not the raw data feed underneath them.
The Limits of a No-Action Letter
A no-action position isn’t a permanent rewrite of the rulebook. Staff letters reflect how the current division reads existing law, full stop — a future division head could narrow this relief or withdraw it entirely without going through formal rulemaking. Any company building a product on top of this exemption is leaning on an interpretation that shifts whenever CFTC leadership does.
The letter’s ten conditions give the agency plenty of room to step in if a provider drifts from passive display toward something that looks more like advice or execution control. That’s a genuine compliance list, not a rubber stamp — providers still need legal review before launch, even with the relief already secured.
History backs up that caution. Other corners of derivatives law have watched regulators narrow or pull no-action relief once a fresh set of commissioners took a different view of the underlying risk, sometimes with barely a transition window rather than any real advance warning. Nothing suggests Letter 26-25 is headed that direction soon, but any provider building a business model on top of it should treat the relief as today’s reading of the law rather than a permanent grant — and keep a fallback compliance plan ready just in case.
What Comes Next
More consumer apps will likely test partnerships with regulated prediction market exchanges now that the broker-registration hurdle has gotten smaller. Analytics platforms and wallet trackers are the obvious first movers, since their design already keeps them on the passive side of the line. Whether that turns into meaningful growth for Kalshi or Polymarket depends less on how many headlines the September 17 letter generated and more on how many providers actually file the required notices and stick to the conditions attached to them.
