Why is everyone acting surprised that the Nevada AG just named Stake

Spend a single day watching how money moves in this space and you realize the industry’s collective surprise here borders on delusional. First Digital didn’t just “route” traffic through their MID—they parked an entire funnel of New York customers inside a Nevada-licensed entity and then acted as though geography stopped at the dashboard. AB831 §3(2) wasn’t written to punish sweepstakes mechanics; it was drafted to stop licensees from laundering customer funds through shells they believe are safe because the PSP’s paperwork says “offshore.” The minute that MID swept FTDs from NY cardholders and credited Stake.us ledgers in Nevada, every compliance tick-box inside First Digital’s playbook vaporized. You don’t get to hide behind Citadel’s shiny brand when the ledger entry reads “customer funds deposited in Las Vegas.” Compliance teams convinced themselves KYC screens were a firebreak; they forgot AB831 treats any deposit touching a licensed entity as New York-sourced if the cardholder is physically in New York. Roll the tape forward: Nevada AG names Stake.us and First Digital together because the statute explicitly treats processors as co-defendants when they knowingly insert offshore traffic into a licensed U.S. ledger. Anyone still scratching their head might want to check who signs the MID agreements—they’re signing up for vicarious liability the moment the first NY-funded transaction hits their settlement desk.

So that "vicarious liability" term keeps sticking in my head — is that basically First Digital's fancy way of saying if Stake.us messes up, Citadel gets the blame too?

i’ve seen that term burned into my skull when the Curacao regulator went after a couple of processors over a rev-share brand that somehow thought their “offshore” status would protect them from a customer’s chargeback in London. vicarious liability isn’t some academic phrase—it’s the rule that says if you touch the wires and a New York customer slips through your MID because your KYC feeds look squeaky clean, the Nevada AG can haul you in alongside the operator. in this Stake.us episode it boils down to one ugly truth: First Digital’s MID agreement made them the pipeline; once NY-sourced dollars passed through their settlement desk in Vegas, every compliance tick-box they ticked inside First Digital’s playbook counted for nothing because the ledger still bore the fingerprints of a New York cardholder. the statute treats that ledger entry as a deposit “in this state,” full stop. so no matter how many offshore brochures Citadel prints, if the FTD hits their desk from a NY IP and ends up funding a sweep ledger in Nevada, they’re shoulder-to-shoulder with Stake.us in front of the Nevada AG—vicarious liability in action.

SlotOps_Est — vicarious liability isn’t a buzzword tossed around to scare processors; it’s the legal hammer the Nevada AG swings when an entity becomes the conduit for funds tied to a restricted jurisdiction. First Digital’s MID made them the artery; once those New York FTDs pulsed through their Vegas settlement desk and landed in Stake.us’s Nevada ledgers, the statute didn’t care how squeaky-clean their KYC feeds looked or how many "offshore" brochures Citadel handed out. The moment the first New York cardholder’s deposit hit that MID, compliance firewalls turned to dust. So here’s the kicker we’re all avoiding: how many other MIDs out there are quietly routing New York sweep traffic into licensed entities and praying geography stops at the dashboard? First Digital just got tagged with the bill—who’s next in line to read the same summons?