AB831 just put everyone in the sweepstakes chain on the hook—so what’s PayPal doing when…

The way PayPal just folded the MID switch without a peep is the real tell—no outreach, no escalation matrix, just "we're done with rev-share affiliate payouts today" like it's a Tuesday. I've dealt with rolling reserves for years and this isn't about KYC noise; it's PayPal calculating that an affiliate name in a Florida DBPR complaint outweighs 60 bps in processing fees for GGR above $25M monthly. You push to ACH-only when the regulator has already singled out your payout rail as a conduit to the affiliate layer—something card networks flagged internally before the Stake.us filing even dropped. The Florida case didn't invent supply-chain liability; it merely gave the major rails a documented court file to attach their own fraud models to. Visa and Mastercard spent months tightening their KYC/KYB rulebooks specifically around affiliate marketing tiers in high-GGR markets—they don't care who processes what dispute, they care about the MID sitting two layers above the player where the affiliate revenue sits. PayPal's dispute window caps at $10k per chargeback? Irrelevant. Their liability exposure isn't customer disputes; it's third-party beneficiary risk under Florida Statute 601.8102 where an affiliate named in agency theory becomes a "supplier" to the operator. Florida DBPR can compel PayPal for records under s. 601.8106(2)(b) faster than an operator can unravel a rev-share contract—case in point, that's why the operators silenced the MID overnight. Rev-share deals shifted the unit economics so the affiliate bears all KYC/AML risk while the operator keeps 100% of the NGR—of course the rails want out. The real question isn't PayPal's chargeback policy; it's at what GGR threshold an operator migrates from rev-share to fixed-fee payouts if the affiliate tier itself triggers a regulatory tripwire.

Wait—so the rails are basically saying affiliates aren’t just a marketing layer but a "supplier" because they’re named in the Stake.us case? But then… how does Florida Statute 601.8102 even define what counts as a "supplier" here? I’m still figuring out how an affiliate with zero direct player touch gets lumped into the same basket as an operator’s backend vendor. Like, if I pay an affiliate 30% rev-share and they outsource KYC to some third-party tool, are they suddenly a "supplier" because Florida DBPR says so? Or is it only when the affiliate’s name lands in a public lawsuit? 😬

you remember when Curacao first tagged "master agents" as "payment facilitators" back in the mid-2000s? same song, different verse. florida statute 601.8102 isn't about who touches the player—it's about who handles the cash flow that eventually lands in the player's pocket. affiliate gets paid because the operator gets GGR; operator only gets GGR because the affiliate steered the traffic that triggered the deposit. so under agency theory, that payment flow makes the affiliate a "supplier" to the operator—like how a kitchen supplier is a supplier to a restaurant even if the diner never meets the butcher. the moment an affiliate name pops up in a florida dbpr filing, the rail sees a single point of failure: if the state can compel records from the operator, it can follow the money upstream to the affiliate because the affiliate's payout is directly tied to the operator's revenue stream. case in point: staking.us got named because the florida lawsuit argued the affiliate layer acted as the operator's conduit for player acquisition funding. rails read that as "payment rail to an unlicensed supplier," and they don't wait for a court ruling—they just yank the MID before the next chargeback lands. rolling reserve frozen for 90 days? that's the rail holding back the affiliate's cut while it sorts who actually owns the liability. ah well, we'll see

Yeah. Only now the rails start asking why we ever let affiliates write MIDs on rev-share payouts. I’ve had two PSPs redo the contract language mid-renewal so the affiliate’s payout sits under the operator’s MID instead of its own—fixed 25 bps instead of the old 55 bps, and a rolling reserve that follows the operator’s license expiry date, not the affiliate’s screw-up. Took a day of haggling to get it through; they said Florida Statute 601.8102 is a minefield they don’t want to map alone.

So the MID isn’t just getting yanked for fun—PayPal folded faster than a deck chair in a hurricane because Florida 601.8102 turns every affiliate name tied to an operator’s revenue into a supplier on paper, even if the affiliate never saw a player’s ID. 😬 But here’s what gnaws at me: if we migrate the affiliate payouts under our own MID and hike the fee to fixed 25 bps like MillieAffiliate did, are we really dodging the tripwire or just letting the regulator chase the operator instead of the affiliate?