Missouri LR 8408: A Platform Using Stripe Is Not a Marketplace Facilitator. Agent Marketplaces Should Not Lean on That Half of the Ruling.
Key Takeaway: In Letter Ruling LR 8408, dated September 24, 2026, the Missouri Department of Revenue held that a peer-to-peer marketplace for digital game items is not a marketplace facilitator and owes no Missouri sales tax on its paid software subscriptions. The ruling gives two reasons. The first, that the underlying sales are not taxable, is sound and carries over to most AI agent marketplaces in Missouri. The second, that the platform cannot collect and transmit payments, sits awkwardly next to the ruling's own facts and the statute's wording, and agent platforms should not build on it.
What the Department Ruled
The applicant is a Missouri LLC that runs a peer-to-peer marketplace for Counter-Strike cosmetic items. The game publisher's own account system moves the items between users, and the applicant never takes custody of them. The applicant provides listing, search, offer, auction, checkout, transaction-status, dispute and seller-payout interfaces. The ruling records that "Stripe, a financial service, processes Applicant's user payments." The applicant may charge marketplace fees and separately sells monthly, annual and one-time access to software features through its website and a browser extension.
The Department answered two questions.
Issue 1: are the item transfers taxable, making the applicant a facilitator? No. The ruling quotes the imposition statute, RSMo § 144.020.1(1), which taxes the business of "selling tangible personal property or rendering taxable service at retail." It then says that "Electronically stored information is not tangible personal property" and that "Missouri does not tax non-tangible property." The item sales are therefore not taxable. On facilitator status, the ruling says the applicant "cannot collect and transmit payments arising from sales conducted between users," and so "cannot act as a marketplace facilitator."
Issue 2: is the software subscription taxable? No. Paid software access "is not one of the enumerated services that are subject to Missouri sales or use tax," so no sourcing rules apply to it.
The ruling binds the Department only with respect to this applicant, for three years, and only while the facts stay as described.
Two Reasons, and Only One Is Load-Bearing
Missouri's facilitator definition is in RSMo § 144.752, which I read this morning. A marketplace facilitator is a person that:
"(a) Facilitates a retail sale by a marketplace seller by listing or advertising for sale by the marketplace seller, in any forum, tangible personal property or services that are subject to tax under this chapter; and (b) Either directly or indirectly through agreements or arrangements with third parties collects payment from the purchaser and transmits all or part of the payment to the marketplace seller."
The test has two prongs, joined by "and." Prong (a) requires that the thing being listed be taxable in Missouri. Once the Department concluded the items were non-tangible and untaxed, prong (a) failed and the facilitator question was over. Everything in the ruling about payment flows is a second, independent ground. The outcome would not change without it.
That second ground is where agent operators should be careful. Prong (b) counts payment collected "indirectly through agreements or arrangements with third parties." The statute separately excludes a third-party financial institution "whose sole activity with respect to marketplace sales is to facilitate the payment transactions between two parties." That exclusion protects the processor. It does not protect the platform that engaged the processor.
The ruling states that Stripe processes the applicant's user payments, and it also states that the applicant cannot collect and transmit payments between users. It does not explain how those two facts fit together. There is a plausible reading: the money for the item trades may move inside the game publisher's system, while Stripe handles only the applicant's own fees and subscriptions. But the ruling does not say that, and a letter ruling's conclusions are tied to the facts the applicant presented. Missouri has not decided that a platform which routes buyer payments through Stripe, with seller payouts on the other side, falls outside prong (b). On the statute's text, it likely does not.
What This Means for AI Agent Marketplaces
Take an agent marketplace, tool directory, or x402 router that lists third-party agent services, takes the buyer agent's payment, and pays the provider. Run it through LR 8408 in this order.
First, is the underlying sale taxable in Missouri? For most agent-to-agent commerce, no. Missouri taxes tangible personal property and enumerated services. SaaS, API calls, inference, data delivered electronically and digital goods are not on the list, and LR 8408 is the second Missouri letter ruling in a month to say so plainly. (The first was LR 8405, dated August 26, which we covered in Missouri Says the Disc Is Not the Product.) If the sale is untaxed, prong (a) fails, and your platform's payment architecture does not matter in Missouri. That is the durable holding, and voters left it in place when they rejected Amendment 5 in August.
Second, if any listed item is taxable, do not rely on "we use a processor." A marketplace that sells tangible goods, or a taxable service, alongside agent services needs to answer prong (b) on its own facts. If your platform takes the buyer's money through a processor account you control and pays sellers out of it, the statute's "indirectly through agreements or arrangements with third parties" language points toward facilitator status. LR 8408 does not decide otherwise.
Third, do not export the Missouri answer. Missouri's definition is one of the narrow ones. Other states define facilitator by communicating offers, setting prices or providing customer support, with or without touching money. Our operator, facilitator or merchant of record decision tree walks through the difference. The same agent platform can be outside the definition in Missouri and inside it elsewhere.
What the Ruling Leaves Open
- The applicant's own marketplace fees. The ruling records that the applicant may charge them, but Issue 2 addresses only the software subscription. The reasoning (no enumerated service) would seem to cover a platform fee as well. The ruling does not say so.
- The payment-flow facts. As discussed above, how the item trades are paid for is not described in enough detail to apply the prong (b) conclusion to any other platform.
- Agent buyers. Nothing in the ruling addresses purchases initiated by software agents. We apply Missouri's rules to agent purchases the same way we apply them to human ones; the Department has not confirmed that approach.
Missouri marketplace facilitator status, and how it interacts with each state's collection rules, is an open question we track. The Tax Foundation's overview of marketplace facilitator laws is a useful starting map of how the states differ.
What AgentTax Users Should Do
- For Missouri, classify the product first. If what passes through your marketplace is SaaS, API access or a digital product, Missouri does not tax it, and facilitator status there is academic.
- Do not cite LR 8408 for the proposition that a processor keeps you out of prong (b). It was issued to one taxpayer, and its payment-flow reasoning is not explained.
- Map your payment flow state by state. Who holds the buyer's funds, whose processor account they land in, and who pays the seller decide facilitator status in narrow states like Missouri. Broader states look at other things.
- Know what our engine does. Verified today with $1,000 B2B buyer calls to St. Louis ZIP 63101 (9.515% combined rate):
saas,subscription,marketplace_fee,api_access,digital_good,data_purchaseandlicenseall return $0 under Missouri's category rules. A seller call withmarketplace_role: "facilitator"and Missouri nexus also returns $0 formarketplace_fee. The local rate is reported but never applied, because nothing in this set is in Missouri's base.
What to Watch
First, whether the Department publishes a ruling on a platform that does take buyer payments through its own processor account. That would test the prong (b) reasoning directly. Second, whether a future ballot measure or bill revisits Missouri's sales tax base, which would make prong (a) a live question for agent marketplaces. Third, whether other narrow-definition states issue rulings that treat processor-routed payments the way LR 8408 appears to.
To see how a Missouri transaction computes, run it in the playground or read the AI agent sales tax guide for how agent activity maps onto each state's tax base.
This analysis is for informational purposes only and does not constitute legal or tax advice. This post reflects AgentTax's current interpretation of evolving law. Consult a licensed tax professional for compliance decisions.
Related Articles
Which Vendors Offer Human-in-the-Loop Tax Registrations and Filings for AI Agents?
5 min readIndustry & OpinionAvalara Aviator Maps Products to Tax Codes. AI Agent Work Does Not Arrive as a Product.
6 min readPolicyLouisiana's Digital Tools Exemption Rule Is Final, and Analytical Software Stayed Out
6 min read