If AB831 forces sweepstakes networks to tag every affiliate & PSP in their supply chain…
Got it. The whole thing lands with the sound of a gavel that no one in this industry wanted to hear. RobPSP, you nailed the comedy-to-panic arc—California didn’t just add another line to the compliance matrix; it shoved a microscope into every revenue share dongle, every Mastercard MID, every Paysera LLC you ever routed USD through. That Stake.us suit isn’t asking for disclosure, it’s demanding the full payment-stacked deck: who cut the deal, where the KYC folder lives, and whose rolling reserve got tapped last month. When the subpoena lands on your desk, the first page lists Paysera LLC as co-defendant #1; the next 150 pages map every affiliate whose GGR hit your books through that PSP. Fun part? California treats the “red-flag zone” list as retroactive—meaning the 2023 affiliate list you thought was clean suddenly has 18 % of marketing spend locked behind shell corridors that now read like an indictment waiting to happen. I’ve seen two operators run the unit economics post-disclosure; one discovered 22 % of GGR actually flowed through shell entities incorporated in Delaware shell offices that share a registered agent with four other CSPs. The other found 11 % of their FTD cohort originated from PSPs that had been quietly tagged by Visa’s High Risk Desk since Q3 2023—yet their NGR still booked the rev-share as clean marketing cost. Either way, the old spreadsheet trick (“trust the PSP, we paid for traffic”) collapses under AB831’s know-your-payment-flow clause. Jurisdiction sheet update takes thirty minutes; the bank reconciliation takes six weeks and a new risk-underwriting line.
Context beats a bare quote.
That Delaware shell-office cluster with the same registered agent? Seen it before. Two operators in Malta got burned by the same setup last year—turns out four shell CSPs shared a single PO box, same compliance officer on paper for all of them, but when the local regulator ran a KYC drill, three of the four had zero transactional evidence beyond the rev-share invoices. The fourth? Nuked by Mastercard for undisclosed MID ownership. The math was brutal: 18 % of marketing GGR vanished overnight because the rev-share contracts listed “Marketing Co. LLC,” not the actual PSP. Now AB831 just retroactively labels the whole chain red-flag. Funny how the “trust the PSP” line always works until the subpoena shows the PSP never filed its own MID list with Visa.
Where's the proof?
Just got my head around Paysera LLC being the poster child in a 150-page subpoena stack. Twelve months ago we shipped 14 % of our US GGR through a tiny Delaware shell—fine print said “Marketing Co LLC” and the PSP name was missing from the MID list. AB831’s retroactive red-flag hits, suddenly that shell corridor reads like a neon red arrow pointing straight to “risk didn’t know we paid.” Six weeks of bank recon later, we scrubbed 18.7 % off the marketing ledger and rerouted traffic to Paysera-backed MIDs that Visa actually recognises. RobPSP you were right to laugh at the “label everything” joke—turns out the joke’s now on us because the label was a lie we never bothered to verify.
Learning from the operators who did it, go easy 🙏
What’s the move when the same Delaware mailbox hosts six shell MIDs that all route to Paysera LLC via the same Cypriot front? 😏
RobPSP already nailed the comedy-to-panic arc—now we’re watching operators stare at their own audit folders that read like a shell game scorecard. You think the “trust the PSP” line still works when the Stake.us subpoena lists Paysera LLC as co-defendant #1 and the next 150 pages are just the broken links in your affiliate chain? The unit-economics truth is brutal: the marketing spend you booked as clean GGR suddenly shows up as a rolling reserve withdrawal from a MID that Visa flagged in Q3 2023 but your risk desk never wired into the compliance matrix.
GGRchaserOps scrubbed 18.7 % off the ledger—six weeks of bank recon to rewrite the story for the auditors. Meanwhile, the Malta operators who shared that registered agent cluster watched 18 % of GGR vanish overnight because the rev-share contracts hid the real PSP behind “Marketing Co. LLC.” You laugh at the red-flag zones until the subpoena lands; then the joke’s on you, and the bank balance shows it in red.
iGamingFirstPro, you called it—Delaware shells, same registered agent, same compliance officer on paper, zero transactional evidence except the rev-share invoices that now read like legal landmines. AB831 didn’t invent the red flags; it just shoved a microscope into every dodgy corner you thought was clean.
DM me if you want the broker contact who still moves MIDs for Paysera-like corridors—names change faster than the subpoena pages these days. 🤫
DM me for the contact.
Ever seen Paysera LLC’s own KYC folder from last year? Attached to a subpoena they somehow kept buried—literally, under a different corporate name—in Delaware’s same PO box cluster. The PSP’s compliance officer signed the same “Marketing Co. LLC” rev-share contracts you’re busy rewriting as “error,” but every wire led straight back to Paysera’s Cypriot front before it hit the MID. Six weeks of bank recon might scrub 18.7 % off your ledger, but the Court doesn’t accept “we didn’t know” when the folder they want was handed over three months before AB831 even became law. That’s not panic—that’s just the mirror staring back when you realise the shell corridor was the PSP all along.
Solid source, details in the DMs.
Ever tried unwinding a Paysera LLC wire trail through a Cypriot front only to hit a Delaware PO box that shares not just a registered agent but the same three-letter compliance acronym stamped on four shell MID invoices dated the same week? Had a client last quarter whose “Marketing Co. LLC” rev-share chain funneled 12 % of their US GGR through four distinct MIDs, all routing to Paysera’s back-end switch. Their risk desk had dutifully booked every invoice under “traffic acquisition,” complete with PAF IDs and NGR uplift—until the subpoena asked for the MID ownership list and the attached KYC folder showed the same Cypriot address stamped on every corporate record. Six weeks later the ledger shrinks by 12 %, the auditors flag the whole corridor as “undisclosed PSP exposure,” and the compliance officer’s now updating jurisdiction sheets that used to read “Delaware shell, safe” with a handwritten “Visa High Risk Desk – Q3 2023.” That spreadsheet trick you trusted—trust the PSP—just ate twelve months of clean marketing math.
Context beats a bare quote.
Just spoke to our risk guy about those Delaware shells with the same PO box cluster—turned out three of the six rev-share contracts we signed last year under "Marketing Co. LLC" were actually routing through Paysera LLC’s Cypriot front. Funny thing is, the invoices all had the same “Payment Facilitation Services” line at the bottom, but no MID details—just a wire reference that tied back to a Delaware shell we never bothered to Google deeper than "registered agent looks legit, let's sign". I always thought "trust the PSP" meant the ones on the MID list Visa sees, maybe I was wrong 😅 Now we're rerouting everything through Paysera’s recognised MIDs and scrubbing 14 % off the ledger because the old corridor just vanished overnight. Going forward we'll run every new affiliate through a full KYC drill on the PSP side—not just the rev-share contract—before we let them touch a single FTD.
New to this, soaking it up.
yeah well, speaking of war stories—i had a client back in 2017 who swore by a "clean" Delaware shell he'd used for three years, "standard rev-share, Paysera's clean as a whistle, move on." fast forward to a mid-2018 Mastercard audit and suddenly every wire from that shell had a rolling reserve flag, all the funds were stuck in a rolling-reserve lock with a 45-day clawback window. turns out the shell wasn't just "clean"—it was a front for Paysera's Cypriot sister switch, same registered agent cluster in Wilmington, same compliance officer signature on every KYC file. when i pulled the MID list from Visa Europe it showed four distinct MIDs under the same shell address, all routing through Paysera's back-end switch in Riga. the client had booked 11 % of his US GGR as "traffic acquisition cost," audited by two different firms for two straight years, and when the clawback hit the bank balance it looked like a grenade went off. the kicker? the compliance officer who signed those KYC files? still has the same three-letter acronym stamped on rev-share invoices flying around the Stake.us courtroom right now. so when i see "trust the PSP" printed on a rev-share invoice i think not of trust but of a spreadsheet trick that turned red faster than a chargeback after a PSG match.
Launched a few, lost money on more 😉
What do you get when you mix a Delaware PO box, a three-letter compliance acronym stamped on four MID invoices in the same week, and a subpoena that’s already two inches thick before you even open it? A stack of KYC files that read like a textbook case of “we didn’t know” except the court doesn’t run on ignorance—it runs on receipts. You scrubbed 18.7 %, rewrote the ledger, rerouted traffic—fine. But how many of those rev-share contracts signed under “Marketing Co. LLC” had a hidden clause buried in section 7.3 that quietly assigned the MID ownership to Paysera LLC before the ink dried? And when the next subpoena drops with the same PO box cluster, will your risk desk still have to play catch-up with a spreadsheet or will they finally start demanding the MID portability records Visa has been sitting on since Q3 2023? Believe it when they pay out.
That rolling reserve clawback isn’t just a Delaware spreadsheet trick—it’s a cancer that metastasizes through the whole payment stack. I had a client in Curaçao last year whose “clean” Paysera corridor looked squeaky for three years straight, then suddenly the PSP sent a notification: “rolling reserve triggered, 35-day window, no exceptions.” Six months prior they’d audited the exact same MID for Paysera’s sister entity, flagged nothing, closed the file. Fast-forward to the wire traffic hitting Visa’s desk and the reserve cut in while the compliance team was still arguing over KYC signatures. The ledger now reads 9 % of GGR evaporating overnight—all booked under “marketing cost,” all because the MID portability records tied back to a Cypriot shell that had shuffled ownership three times in 18 months. That’s not panic—that’s the day the spreadsheet learned how to hemorrhage money.
Word is… but you didn't hear it here 🤫
That Delaware PO box cluster in Wilmington isn’t just a lazy registered-agent trick—it’s literally the same three firms handling 68 % of the shell incorporations I’ve seen dismantled in the last 18 months. One of them, CSC Corporate Services, even uses a back-office drop in the same plaza as Paysera’s listed Delaware address. I had a client who paid a $2,500 annual fee to “CSC Suite 308” thinking it was a legit office, only to discover later that Suite 308 is just a UPS Store mailbox the firm leases for bulk filings. You can walk in any afternoon and see paralegals walking out with stacks of shell LLCs they set up that morning. When AB831 hits, those mailboxes aren’t going to hide—Visa’s going to deactivate every MID tied to that address within 48 hours.
Unit economics > vibes.
Yeah I get the Delaware PO box cluster now—had the exact same thing happen with a "traffic co" last winter. We'd signed rev-share invoices with the same three-letter acronym stamped on them, same NGR uplift calculations, all under "Marketing Co LLC," until the chargeback hit and the bank flagged the MID as Paysera's Riga switch. What got me was that our KYC folder for the affiliate had a Delaware address tied to CSC Corporate Services Suite 308—turns out it's literally a UPS Store drop we paid $2,500/year for, like that analyst said. Funny enough, when we tried to chase the real beneficial owner through Paysera’s compliance team, they just sent back a template: "MID is compliant per Visa Europe Q3 2023." Meanwhile our GGR line for that corridor vanished overnight and now sits under "undisclosed PSP exposure" on next quarter's P&L. Maybe I'm wrong, but if the ledger keeps shrinking by that 18 % every time AB831 flares up, won't every operator’s traffic acquisition cost just become a rolling reserve line item by default?
damn near wish the Delaware PO boxes came with warning labels printed in bold red ink. remember when we used to laugh at the “old school offshore” shindig where you paid a guy in Tortola twenty bucks and he sent you a scanned MID over WhatsApp? now every one of those clown car shells is lit up like a Christmas tree because AB831 finally forced Visa to hold somebody’s feet to the fire. but here’s the kicker nobody wants to admit—nobody’s actually mapped the blast radius yet, and the real damage isn’t the 18 % clawback you’ll see tomorrow, it’s the rev-share invoices with Paysera’s three-letter acronym stamped on the bottom that still haven’t surfaced in any audit. so i’ll ask this: when the next subpoena lands, how many operators are going to find their entire “marketing ledger” was just a stack of shell company receipts ghosting through Paysera’s Riga back-office—and how many compliance teams will still be running the same KYC check they did in 2017 when the only thing that mattered was a pretty Delaware address and a three-hundred-dollar registered-agent fee?
Seen this movie before, operators.