Skip to content
Broker news. Connected. RSS feed
FXBROKERS

A clearer view of the broker industry.

Retail-derivatives customer money is split across three CFTC regimes

Monthly filings show retail-facing FCMs carrying customer assets under futures, foreign-futures and cleared-swaps rules. The product label alone does not reveal the legal protection.

The retail-derivatives boom is being presented to customers through familiar apps, but the customer money behind those products does not sit in one uniform regulatory bucket. CFTC records for 31 August 2026 show several retail-facing futures commission merchants reporting customer funds under section 4d, cleared-swaps rules, or both. Coinbase Financial Markets reported assets in all three principal regimes: U.S. futures and options, foreign futures and options, and cleared swaps.[1][2][3]

The legal distinction is not cosmetic. Each regime applies to a different class of contracts and uses separate accounts, calculations and protections. An app label such as “prediction market”, “event contract” or “futures” is not enough to determine where customer property is carried. The exchange, instrument, clearing arrangement and FCM legal entity together determine the applicable treatment.[2][3][4]

Three customer-fund regimes appear in one monthly table

Section 4d of the Commodity Exchange Act covers customer funds for U.S. exchange-traded futures and options. Part 30 covers funds for foreign futures and foreign options. Cleared-swaps customer collateral is held under a separate legal segregation model. The CFTC publishes assets in segregation and the amount required to be segregated for each category.[2][3]

“Assets in segregation” and “amount required” should not be read as profit and liability. The former describes the assets maintained in the customer protection account; the latter is the calculated requirement associated with customer positions and balances. An excess of assets over the requirement is expected operational headroom. It does not belong to customers merely because it appears in the customer-fund table, and it cannot be transferred conceptually from one legal pool to another.[2][3]

Retail-facing FCMs now span several architectures

Robinhood Derivatives reported $234.5 million of section 4d customer assets against a $131.3 million requirement, plus $194.4 million of cleared-swaps customer assets against a $36.2 million requirement. Combined for analytical purposes, the two pools contained $428.9 million of assets against $167.4 million required. The combination is useful for sizing the entity, but the two pools remain legally separate.[1][2][4]

Coinbase Financial Markets reported $346.9 million of section 4d assets against $211.4 million required, $6.0 million of Part 30 assets against a requirement of only about $5,000, and $166.1 million of cleared-swaps assets against $6.2 million required. Across the three lines, the entity reported $519.0 million of customer assets. The unusually small Part 30 requirement beside the assets shows why raw assets cannot be equated with current customer exposure.[1][2]

FanDuel Prediction Markets reported $1.7 million of section 4d assets against about $52,000 required and $10.0 million of cleared-swaps assets against $3.4 million required. Webull Futures reported $62.1 million of section 4d assets and $8.4 million of cleared-swaps assets. Plus500US reported the largest selected section 4d pool, at $1.04 billion, as well as smaller Part 30 and cleared-swaps pools.[1]

Other retail-labelled entities were concentrated in one category. Kalshi Prime reported $16.8 million of section 4d assets against $12.5 million required. Sleeper Markets reported $11.2 million in cleared-swaps customer assets against $1.1 million required. Performance Predictions II and Foris DAX FCM also reported cleared-swaps customer assets. The legal name on the CFTC table may be unfamiliar to a customer who entered through a consumer brand.[1][2]

The figures cannot identify which dollars came from event contracts

It would be wrong to label every balance at these FCMs as prediction-market money. An FCM can clear several products, and the monthly financial table does not break a customer pool down by contract. Robinhood, for example, describes event contracts as offered through Robinhood Derivatives and traded on designated contract markets, but its CFTC customer-fund lines can include other eligible activity at the same entity.[1][4]

This limitation narrows the finding without erasing it. The records establish the architecture used by the legal entities carrying retail customers. They show that the same retail-facing FCM can maintain both futures and cleared-swaps pools. They do not establish the share attributable to sports, economics, politics, crypto or any other event category.[1][2][4]

Intermediation changed the Kalshi structure

The CFTC’s January 2025 amendment to KalshiEX’s designation permitted intermediated futures contracts in addition to the exchange’s existing direct-access model. That change made the role of an FCM more visible: an intermediary can receive customer property, carry accounts and connect customers to the designated contract market. Kalshi Prime’s section 4d line is one financial trace of that intermediated architecture.[1][5]

A customer may see a yes-or-no contract with a simple payout, but the operational chain can include the app, the FCM, the exchange and the clearing organisation. Those entities can be affiliates or independent companies. Each performs a different function. Confusing the front-end brand with the regulated holder of customer funds obscures who owes what to whom.[3][4][5]

Why separate pools matter during stress

Segregation rules are designed to keep customer property separate from the FCM’s own money and to support the transfer or return of customer positions and balances if the intermediary fails. The calculation is performed for the relevant customer class. A surplus in one pool does not automatically cure a shortfall in another, because the legal protections and entitled customers differ.[2][3]

The August data showed assets above requirements for every selected line discussed here. That is a compliance snapshot, not a guarantee against loss. Customer funds can still be exposed to operational error, investment risk within permitted instruments, bank or custodian failure, cyber incidents, disputed position treatment and market moves. The table also reports month-end figures, not intraday lows.[1][3]

The margin between assets and requirements can be large because the assets line includes customer property and qualifying residual interest maintained by the FCM, while the requirement responds to current customer balances and positions. A large numerical excess should not be advertised as an insurance fund. It is part of the segregation calculation and can change as positions settle, customers transfer funds and the FCM adjusts its residual interest.[2][3]

The rulebook is still developing around the products

In February 2026, the CFTC withdrew a proposed event-contract rulemaking. Withdrawal did not abolish the Commodity Exchange Act or exchange and FCM obligations. It left product legality and regulatory boundaries to existing statutes, orders, court decisions and contract-specific review rather than the withdrawn proposal. The customer-fund rules continue to operate at the intermediary level.[6][3]

That distinction is important in political debates over prediction markets. Arguments about whether a contract should be listed are separate from the question of how an authorised intermediary must carry customer property once a contract is available. A product can be controversial while its customer assets are reported within a familiar futures or swaps protection regime.[3][5][6]

What a customer should be able to identify

Before funding an account, a customer should be able to identify the exact FCM legal entity, the exchange or venue, the clearing model and the customer-fund regime. Disclosures should also explain whether cash earns interest, whether the firm retains that interest, how withdrawals work, and what happens if a contract is voided or disputed. A brand-level statement that a product is “regulated” is too broad to answer those questions.[3][4]

The CFTC table provides part of that map. It shows the legal entities and the size of the reported pools. It does not map each app screen to a specific line. Retail platforms could close that gap by naming the FCM and fund regime beside each product, rather than leaving customers to reconstruct the chain from multiple agreements.[1][2][4]

The selected retail-facing entities already carry more than $2 billion

Adding the customer-asset lines of Robinhood Derivatives, Coinbase Financial Markets, FanDuel Prediction Markets, Kalshi Prime, Sleeper Markets, Webull Futures and Plus500US produces approximately $2.12 billion across the three regimes. The figure is not a market-size estimate for event contracts: Plus500US and Webull, among others, carry broader futures activity, and the same legal entities can serve several products. It is an order-of-magnitude measure of the regulated customer pools operated by retail-facing FCMs.[1][2]

Plus500US accounted for about half of that selected total, largely through its section 4d pool. Coinbase and Robinhood together accounted for roughly $948 million. The distribution shows why brand-level market narratives can be misleading. A company prominent in event-contract headlines may sit beside a much larger customer-fund pool built through conventional futures, while a newer prediction-market entity may still be financially small.[1]

The total also excludes other FCMs and cannot be reconciled directly with exchange trading volume. Customer assets are a stock measured at month end; trading volume is a flow over time. A platform can process large notional volume while customers post relatively little collateral, or hold substantial cash while trading lightly.[1][2]

An insolvency would test legal identity, not app familiarity

In a failure, the decisive records would be the customer account at the FCM, the class of contract and the location of the relevant segregated pool. The consumer-facing app might remain the customer’s main interface, but insolvency administration and transfer procedures would operate through regulated legal entities. A customer who cannot name that entity is poorly equipped to understand notices or file a claim.[3][4]

Separate pools are intended to prevent one customer class from subsidising another. That protection also means customers cannot assume that a large excess shown elsewhere in the same corporate group is available to them. Group liquidity, guarantees and affiliate support may matter in practice, but they are different from the statutory segregation calculation.[2][3]

The monthly data do not show beneficial ownership by individual customer, nor do they establish how quickly assets could be transferred. They are an early-warning and transparency tool. Operational readiness depends on books and records, reconciliation, bank and custodian arrangements, exchange portability and the condition of the FCM at the time of stress.[1][3]

The front-end disclosure can be made much simpler

A concise product label could state: “Carried by [legal FCM]; traded on [venue]; treated as [4d futures / Part 30 / cleared swaps]; customer-fund disclosures available here.” That would translate the regulatory chain into information a retail customer can use before funding an account. It would also reduce the risk that the word “regulated” is understood as a single universal protection.[3][4]

The reconstruction shows that this is not a theoretical request. Robinhood and Coinbase reported multiple customer classes in the same monthly filing. The architecture is already complex enough that customers need product-level mapping. Greater clarity would not imply that any current disclosure is unlawful; it would make the economic and legal relationship easier to understand.[1][2][4]

The adversarial check found no reported customer-fund deficit

Every selected line discussed in this article showed assets at or above the reported requirement. The investigation therefore does not support a deficiency headline. Large excesses also cannot be treated as proof that every customer would be repaid immediately under all stress scenarios, because legal entitlement, asset liquidity and operational records still matter.[1][2][3]

The finding that survives both directions is structural: retail-facing firms are using several customer-protection regimes, and the public brand does not reveal the applicable one. That can be established without alleging a failure by any named entity.[1][3][4]

A market-structure finding, not a shortfall finding

Across the selected retail-facing FCMs, the August figures showed substantial assets and positive excesses over required amounts. The investigation found no reported deficiency in those lines. Its original contribution is the cross-entity reconstruction: the new retail-derivatives market is not one pool of prediction-market cash but a network of separately protected customer classes carried by different FCMs.[1][2][3]

That architecture will matter more as the market expands. The front end can make contracts look interchangeable; the back end decides which rules protect the customer, where the money is reported and which regulated entity must return it. The simplest contract on a phone can rest on a surprisingly complex chain of legal segregation.[1][3][4]

Follow the evidence

Sources & further reading

  1. August 2026 FCM and RFED Financial Data U.S. Commodity Futures Trading Commission · Accessed 10 Nov 2026
  2. Description of Report Data Fields U.S. Commodity Futures Trading Commission · Accessed 10 Nov 2026
  3. FCM customer funds U.S. Commodity Futures Trading Commission · Accessed 10 Nov 2026
  4. Event contracts Robinhood · Accessed 10 Nov 2026
  5. CFTC amends KalshiEX designated contract market order U.S. Commodity Futures Trading Commission · 17 Jan 2025 · Accessed 10 Nov 2026
  6. CFTC withdraws event contracts rule proposal U.S. Commodity Futures Trading Commission · 4 Feb 2026 · Accessed 10 Nov 2026

Report an error or submit an update