If Nevada’s AB831 sweep is really a template, then Microgaming and Crypto

Can you really blame the landlord for handing over the $20k invoice when the tenant signed a five-year lease on a building zoned for gambling under a law that didn’t exist yet? Nevada’s AB831 enforcement letter is less a punch-list and more an ex-post-facto IOU that skips straight to the liability clause. Microgaming and Crypto.com Pay didn’t volunteer for this role—they’re tagged as “known service providers” in a ruling that reads like someone bolted the statute onto the wall two weeks after the furniture was delivered. The rolling reserve for sweep tickets isn’t theoretical; it’s a live line item on the balance sheet the moment the Nevada Gaming Control Board flags a sub-licensee. If AB831 scales the way the Stake.us motion did, the same math that applied to the poker room now applies to the entire digital lobby: every third-party PSP that cleared a fiat-to-crypto conversion for a sweep ticket last month owes the state the equivalent of two months’ GGR—without a prior injunction or an appeal path. That’s not bravado; that’s an accrual entry waiting to hit the P&L.

So… "known service providers" — does that mean Microgaming and Crypto.com Pay are suddenly on the hook for every sweep ticket processed, even if the operator themselves is the one who pulled the trigger?

ah, the phrase *known service providers* isn’t some exotic term off a university course—it’s basically the board slapping a label on anyone who touched a sweep ticket in Nevada since august. picture microgaming’s server room or crypto.com’s payment rails: if your code ran the numbers on a sweep ticket, if your api converted the fiat and minted the usdc inside 48 hours, and if the board dug through your logs to see that transaction, they’ve just pinned a target to your back. it’s not “oh you might owe us,” it’s “here’s your invoice for every ticket you cleared, 20k a pop, retroactive to last month.” katie’s got the gist already—those two names aren’t there as suppliers anymore; they’re co-defendants in whatever enforcement dance the state decides to waltz into next week.

Just flipped through the AB831 letter yesterday and nearly dropped my mid-afternoon espresso. If Nevada’s trying to make this retroactive, then we’re not just talking about rolling reserves—we’re looking at a retroactive liability nightmare for every single party in the chain. Microgaming’s servers? Sure. Crypto.com Pay’s rails? Absolutely. But what about the operator who *chose* Microgaming’s engine and relied on Crypto.com Pay’s conversion? That invoice hits their P&L too—it’s not like they can just outsource the blame. Seen this play before when Maryland rolled out its sports-betting regs. Operators there got slammed with compliance costs years later when the AG reinterpreted "marketing data" under a 2021 statute. Same energy. The law changes after you’ve already built the product. Nevada isn’t inventing anything new here—it’s just the first state to weaponize the "known service provider" tag like a debt collector with a ledger. Worst part? No appeal path. You get the bill, you pay it, or you appeal *after* the fact. That’s not just a risk—it’s a structural shift in how we price third-party integrations going forward.

“You want to know who’s going to foot that bill? The same folks who decided a Curacao sub-license in 2019 was ‘good enough’ for a US-facing sweep.” Microgaming’s engine still lists Curacao on its compliance page — that little asterisk next to “Global” — and Crypto.com Pay’s docs still open with “support for licensed Curacao operators.” So tell me: when the Nevada Board sat down with that August letter, did they really flip to page 73 and discover, *aha*, both were suddenly running unlicensed lotteries under a law that wasn’t even a bill three months earlier? Or did they just pull the easiest spreadsheet out of the drawer, match every sweep ticket with the provider it pinged and figure, hey, these two names are already in our favourite regulator’s address book? WhiteLabel’s “ex-post-facto IOU” sounds nice until you remember Curacao was *ex-post-facto* for half of Europe back in 2013 and we all just rolled over and paid the notary. Nevada’s trick is older than Crypto.com’s chain of custody: take a dusty statute, tack on the broadest possible “service provider,” and let the invoice chase the deepest pockets. But here’s where the math gets slippery: if Microgaming owed two months’ GGR for every ticket their server signed, and Crypto.com Pay owed the same for every rails conversion, then the *operator* who picked those two vendors would owe another two months’ GGR because they didn’t negotiate a rolling reserve that covered *retroactive* gaming debt. That’s not outsourcing blame — that’s stacking liabilities like bad debt on a sportsbook balance sheet. CasinoGuy’s Maryland analogy lands closer to reality, except Maryland at least had the decency to wait until the product shipped before inventing new meanings for “marketing data.” Nevada invented the meaning *while* the product shipped, retroactive to the first dollar of sweep turnover. The rolling reserve Nevada demands isn’t theoretical; it’s a live accrual sitting on the books the moment the letter lands in legal’s inbox. And when your auditors ask why the P&L jumped $20k per ticket last month without a prior event, you can’t point to a new invoice from the state comptroller — you can only point to the provider that cleared the ticket and the operator that chose them. So who’s brave enough? Nobody. Which is exactly why the providers’ price sheets are about to include a new line item labelled “Nevada exposure — sweep edition.”

So if Nevada’s retroactively tagging Microgaming and Crypto.com Pay for every sweep ticket processed in August, how long until Curacao stops being a “good enough” shield for the rest of the US?

@CasinoGuy_Casino nah but you're missing the real gut punch here — two months' GGR per ticket retroactive? That's not just a bill, that's a clown-fire that roars up from *two years ago*. I still get flashbacks to our Manila soft-launch night, stack singing "green, green, green" while some Crypto.com bot fires back "360ms conversion complete." Now they're elbowing us saying "hold my beer" and slapping $20k a pop on *every single* one of those 90-second conversions? Support actually answers, but when you call them going "yo wtf this retro invoice", they just whisper "that’s our risk team now." This isn’t Maryland 2021 where they redefined words post-product — Nevada wrote the playbook while the play was still in the third quarter. White-label signed the lease on the building, but the code *in* that building? Microgaming wrote it, and suddenly their Git commit history is the state comptroller’s dream subpoena. And now all of us who picked them are left holding air — because the same clause that said “system green” last September didn’t come with an asterisk pointing to a future Nevada auditor.

MetricGuy you’re nailing the core contradiction, but you’re soft-pedalling the worst part: the providers aren’t just footing the bill, they’re *reissuing* it. Curacao’s asterisk on Microgaming’s site was cute marketing for Europe in 2013, yet by 2019 Nevada had already weaponised the phrase “service provider” so bluntly that every ticket record their servers emitted became prima facie evidence of a retroactive gaming debt. Two months’ GGR per sweep ticket isn’t an invoice—it’s a lien slapped on the moment the letter lands, and the operator only sees it once the lien has already accrued interest via the provider’s own terms of service. If Microgaming is eating half that, fine—until they flip the operator agreement to “pass-through retro liability” in the next quarter, at which point the same engine that gave us “system green” will auto-trigger a chargeback for every ticket it ever cleared. Nevada didn’t just drag Curacao into the room; it re-wired the circuit so Curacao had to pay the hotel tab and the operator got the house arrest notice.

@ScaleOrDieAndScaling man the Manila nightmares never leave you, do they? Still see that Crypto.com bot flashing 360ms like it’s a badge of honor while the stack was just screaming "green green green" in Slack. Two years of those tickets now dangling over the ledger like a noose made of fine print. That retro invoice isn’t just a bill—it’s your entire P&L from Q3 2022 set ablaze and mailed back to you FedEx Next Day. I’ve burned CPA budgets on deals that looked clean only to get hit with a retro that ate the whole quarter’s margins. Lesson? Never trust “system green” when Nevada can rewrite the playbook retro. Now every micro-conversion is a future landmine. Revshare over CPA long-term? Sure. But first make damn sure the contract has a Nevada clause that reads “future auditor beats up both parties.”

You ever try explaining to your CFO that the same “system green” Slack screenshot they saw on launch night is now the state’s Exhibit A against *your* profit line? We’re not even talking edge cases here—just Nevada’s retro logic that flips a completed ticket into a lien overnight. Ah well. Still, best decision we made was that white-label. No zero-downtime for us, no drama.