AB831 just dropped a bomb: if we onboard a Costa-Rican PSP or a UAE affiliate tomorrow…

God, I keep seeing this exact panic loop in operator circles every time AB831 drops a new case file. Remember when the Delaware AG went after that UK-based PSP last year because three Delaware-licensed affiliates used their MID? TurnkeyPTSD’s right about the movie déjà vu—same plot, different jurisdiction—but this Costa Rica/UAE combo lands harder. EveriPay in CR isn’t just a payment processor; they’re holding multiple MIDs for U.S.-facing skins while their parent holds a CR PSP license under SUGEF. That dual stack is the red flag. Arizona courts love piercing corporate veils when the MID sits in a CR entity but the beneficial owner sits in Dubai managing the U.S.-side rev-share with AffPower. And here’s the kicker: if your Dubai JV has an FTD-to-GGR ratio above 35% with AffPower as the traffic source, California AG subpoenas aren’t just possible—they’re scheduled for failure.

What’s the difference between running a rev-share out of Dubai and giving the California AG a hand-drawn map to your chargeback ratios? You’re not just wiring money overseas—you’re handing them a stack of paperwork that says “here, I did my own KYC screening on the affiliates, and no, I didn’t even look at their Dubai JV entity.” At the risk manager table in São Paulo we call that “invitational negligence,” and it lands faster than the NGR hits zero after a bot-ring surge. That 35% FTD-to-GGR ratio RevShareBeliever flagged? It’s the moment your UAE “partner” quietly rolls the MID to EveriPay Costa Rica, the one holding the MIDs for U.S.-facing skins while SUGEF pretends it’s a textbook AML case. California AG doesn’t care about your Costa Rican license or your Dubai offshore shell; they see a MID that’s been a revolving door for shell entities, and they subpoena the entire chain because that’s how piercing the corporate veil works now—no magic wand, just a subpoena template. EveriPay’s parent in Costa Rica? It’s the same playbook we saw with that UK PSP Delaware fell over: when the MID sits in one jurisdiction but the beneficial owner and the affiliate revenue are wired through a second one that treats KYC like a suggestion, the AG treats every wire as proof of intent. You want to argue compliance? Fine—show me the rolling reserve contract that EveriPay signed with each U.S. operator using that MID. Spoiler: it’s probably boilerplate with an evergreen clause you can terminate with 30 days notice, meaning EveriPay’s liability vanishes the moment the heat shows up. So the real question isn’t whether the AG will come knocking—it’s how many subpoenas they’ll issue before you realize your Dubai JV’s “healthy rev-share” just became the first domino in a line of corporate shells that California wants to audit backward to 2021.

Yeah, we kinda saw this exact disaster unfold with that Turkish PSP last summer—turns out "offshore compliance" there was just a guy in a WeWork with a stamp collection. So when California AG started digging, they didn't care that the PSP was "regulated" by some Caribbean watchdog; they went straight for the MID tied to three Delaware operators, and boom—entire rev-share chain got treated like a single shell entity. EveriPay's setup sounds like a carbon copy: CR license but U.S.-facing MIDs moving through Dubai "management" with AffPower as the top traffic source. I get the 35% FTD alarm bells—RevShareBeliever’s right, that’s basically an engraved invitation for piercing— but here’s the bit that’s been chewing at me all week: what’s the rolling reserve actually covering? If EveriPay’s boilerplate contract with operators allows them to freeze the reserve or flip it to another MID the second scrutiny hits, then that reserve isn’t a buffer—it’s a fig leaf. Saw one operator in São Paulo try the same trick; they lost their MID inside 45 days when the reserve magically "reallocated" to cover a chargeback surge from "non-KYC" Dubai traffic. Might be time to ask EveriPay for the actual reserve schedule, not the marketing PDF they hand out at ICE London.

Remember when we onboarded that Costa Rican MID last year under the same logic? Thought we were bulletproof with SUGEF waving us through. Six weeks later, Nevada AG came sniffing after a chargeback cluster tied to an UAE traffic source—turns out our "rolling reserve" contract had an evergreen clause. When the heat showed up, EveriPay just folded it into another MID they’d opened for a shell entity in Panama. Poof—our reserve vanished overnight, and suddenly we’re explaining to Nevada why a Dubai JV’s "healthy FTD ratio" was really a laundromat disguised as a rev-share. Not kidding, their compliance guy literally said "we treat each MID as a separate risk bucket" while shifting the bucket between jurisdictions like a game of whack-a-mole. 😏

Ever seen a regulator get into the nitty-gritty of a rolling reserve contract faster than you can say “corporate veil”? I had that pleasure back in 2018 when the Pennsylvania gaming board pulled the curtain on a Caribbean PSP we’d been using — fun night, that one. Their boilerplate reserve clause read like it was written by Houdini: “reserve automatically reallocated upon any subpoena, no notice required.” So when the subpoena landed, our MID evaporated into thin air and the board treated us like the PSP itself. Lesson number one that new lot never learned: the moment your rolling reserve contract gives the PSP an exit hatch, they’re not your partner — they’re your getaway driver.

You're all talking about EveriPay like it's some rogue actor running a fire sale of MIDs to Dubai shell games. Fine—let’s table-flip the PR gloss for a second. Where in any of these vendor decks does it explicitly say EveriPay guarantees *contractual indemnification* for subpoena fallout originating from an affiliate traffic source they *didn’t* vet beyond “click-wrap KYC” in a WeWork? They’ll show you a MID with 30% reserve on paper, but the boilerplate reserve clause in their 2023 rev-share addendum? Section 7.3: “Reserve reallocates without notice upon any request from a payment network or law enforcement body.” That’s not a rolling reserve—that’s an unconditional surrender clause masquerading as compliance theater. And the 35% FTD alarm? It’s noise until someone proves the MID’s payment-flow ever touched the Costa Rica entity post-2021. Last quarter our analytics flagged a Dubai rev-share at 42% FTD, so we pulled the MID trigger ourselves—turned out the traffic was coming through a Panama shell that routed payments via a Lithuanian PSP. The real pivot isn’t the FTD ratio; it’s whether the MID *ever physically existed* in a jurisdiction whose courts will honor a California AG subpoena. EveriPay’s dual-stack playbook (CR license + Dubai management) only works if SUGEF decides to ignore the MID’s U.S. usage history—good luck betting legal precedent on that. So before we all pretend EveriPay is the new Everi—ask them for the last three MIDs they terminated under subpoena pressure and the corresponding reserve clawbacks. Bet the silence after that question gets louder than any panic loop.

Yeah, RollingReserveKing’s missing the forest for the tree roots there. The conversation’s swinging between “EveriPay is the villain” and “boilerplate reserve clauses are sketchy,” but nobody’s asking why operators keep using CR PSPs with Dubai JVs in the first place if the risk is that obvious. Case in point: last year we moved a chunk of U.S.-facing skins off a CR MID entirely after Nevada AG lit a fire under a different UAE-heavy rev-share. Not because EveriPay’s contracts scared us—that easy, they didn’t. We walked because the Dubai traffic source (same network RevShareBeliever flagged) kept tripping up MID stability, not the reserve clause. EveriPay’s SUGEF license? Still squeaky clean. Their reserve contract? Amended within 48 hours once we threatened to pull the trigger. The real wildfire wasn’t EveriPay—it was the affiliate layer funneling traffic through shell entities that’d already been burned by California-style AG scrutiny elsewhere. Dual-stack isn’t the problem; dual-stack *without* unified KYC/AML for the entire traffic chain is. You want to avoid the Slack-desk subpoena parade? Don’t blame the PSP for your affiliate rev-share’s leaks. Tighten the Dubai JV’s entity ownership so every affiliate payout hits a single transparent ledger. EveriPay’s happy to guarantee that ledger if you pay for their enhanced due diligence package—extra 0.15% on rev-share, but no MID migration games. The silence after that counter-offer usually speaks louder than any contract clause. 🤫

The EveriPay and AffPower naming in the Stake.us suit isn’t just about geography—it’s about the MID lifecycle. I’ve seen operators chase the lowest rev-share out of Costa Rica or Dubai, only to discover later that the MID in question had been surgically repurposed three times in two years: first under a U.S. skin operator, then a Cyprus shell for a second operator, and finally re-registered in Panama under EveriPay’s umbrella after Nevada AG issued their first warning letter last summer. The MID itself isn’t the crime scene—it’s the forensic breadcrumb trail of corporate reshuffling that California AG treats as prima facie evidence of willful evasion. You don’t need 35% FTD to get subpoenaed; you need a MID that’s been passed through jurisdictions faster than SUGEF can update their public filings. And let’s be clear: SUGEF’s silence on these relocations isn’t oversight—it’s tacit acknowledgment that the reserve clause in the operator-PSP contract was written to dissolve the moment scrutiny hits.

Man, I’d have laughed myself sick if I’d actually read those reserve clauses before onboarding that Costa Rican MID we used for our LatAm skins last winter — turns out the clause buried in paragraph twelve of the PDF just said “rolling reserve automatically dissolves upon any subpoena.” 🤡 Of course I missed it; who reads boilerplate in December when the GGR target is 300k and your affiliate manager’s screaming about “holiday FTDs” in the group chat. But here’s what bugs me: CasinoLifeBiz nailed the core issue — dual-stack isn’t the fire, it’s the fire hose of shell entities funneling traffic through Dubai. We saw the same leak at AffPower when they switched our U.S.-facing rev-share to a Panama shell overnight; suddenly our NGR was half what it should’ve been because “Dubai management” re-routed payments to a MID that had just failed a Nevada gaming board KYC audit. EveriPay’s SUGEF license might look clean, but if the MID’s money trail leads to a jurisdiction that won’t cough up subpoena docs, the reserve isn’t a safety net—it’s a mirage. We ended up yanking the whole MID and paying 0.20% more for a Lithuanian PSP with a single ledger. Saved us the Slack-desk surprise; still waiting for California AG’s email every Tuesday like it’s my second job.

been in the offshore PSP game long enough to know one thing: if your traffic chain looks like a three-card monte setup, no SUGEF license will save you when the regulators start circling like vultures over a casino buffet. back in 2014 when i launched my first .cr skin, i partnered with a PSP that promised the cleanest MID in the region—Costa Rican shell, panamanian paperwork, but the traffic all came through dubai shell companies routing payments through lithuanian banks. worked like a charm until the maryland ag subpoenaed every entity in the chain and suddenly the cr midi "disappeared" overnight because the reserve clause was written like it was meant to evaporate under pressure. regulators don’t chase jurisdictions—they chase the money, and if your affiliate layer is shuffling funds through half a dozen shells faster than you can say "compliance," the reserve isn’t a safety net, it’s a body bag for your operator license.

Emma247’s 2018 Pennsylvania case hit the nail squarely—caribbean PSPs have been running this exact playbook since the dawn of regulated iGaming. But “fun night” is a masterclass in understatement when the MID vaporises before you’ve even had time to draft the defence letter. The reserve clause didn’t just “automatically reallocate”; it signed away the operator’s entire margin on the invoice before the ink was dry. Corporate veil? More like corporate trapdoor. RollingReserveKing, you’re right that EveriPay’s boilerplate screams surrender—Section 7.3 is the financial equivalent of a dead-man’s switch wired to the MID’s last known jurisdiction. Yet CasinoLifeBiz dumps the hot potato back on the operators: “why keep using CR PSPs?” Because for every dollar the Dubai rev-share bleeds, EveriPay takes an extra 2 bps on the MID fee and hands us the compliance certificate with a smile. Until the certificate isn’t worth the paper. What worries me is the MID lifecycle Harry_Payments sketched—the traffic reshuffle you described happens weekly in Dubai free-zones. Affiliates sign up, PSP pushes them through a Panama shell that “routes payments via Lithuanian banks,” regulators issue a warning, and by Friday the MID’s listed owner is a freshly inked BVI shell incorporated at 12:34 p.m. local time. SUGEF’s public filings? Updated “within 30 days.” By then the California AG subpoena already has the MID’s former owner mailing address—likely a WeWork mailbox in Jumeirah Lakes Towers. NumbersAuditor, your LatAm MID fiasco isn’t unique; it’s systemic. The reserve clause in paragraph twelve isn’t a typo—it’s the PSP’s escape hatch stamped into the contract. When regulators start asking whose traffic actually hit the MID, the reserve vanishes faster than the MID itself, leaving the operator holding the bag of FTD chargebacks and a Nevada-style KYC audit. EveriPay’s SUGEF license stays squeaky clean because the licence belongs to the Costa Rican shell, not the MID’s actual payment flow. BenOps58, your 2014 three-card monte is still the gold standard for regulators. They don’t need paperwork; they need a continuous, traceable flow of funds from player wallet to operator bank account. Once the trail loops through Dubai shells, Lithuanian ledgers, and Panamanian incorporations faster than the reserve can react, the only outcome is an operator license revoked for “failure to maintain adequate controls.” The reserve? Gone. The MID? Dissolved. The Slack-desk? Already typing the subpoena.

You ever wonder why some of the slickest dual-stack deals still walk away from scrutiny unscathed? Take our Caribbean-Curacao hybrid last year—operating under EveriPay’s CR arm, routed through a Curacao license for U.S. skins. FTDs were garbage, sure, but the MID stayed pristine because we insisted on a unified KYC flow where every affiliate payout hit the EveriPay ledger *before* touching any Dubai shell. The reserve? Locked, not vaporized. No Section 7.3 slap-in-the-face reallocations, no Nevada AG fires—just smooth sailing. The trick wasn’t avoiding the PSP; it was dictating the traffic chain.

everiplay’s contract wasn’t the problem—it was the three-way mirror trick the Dubai rev-share kept pulling with the MID: every time california ag blinked, the affiliate layer rotated the shell faster than sugef could update their website, and suddenly the reserve clause wasn’t dissolving—it was disappearing from the chain of custody entirely. so here’s the open door we’re all walking through: if you hand a cr psp the keys to your rev-share traffic without forcing that unified ledger casino lifebiz keeps preaching, you’re not just gambling on ftds—you’re handing the regulators a blank subpoena. and when the mid trace loops through dubai → panama → lithuania so fast the reserve can’t even cough up a ggr number, the only thing worse than a slack-desk is explaining to your compliance officer why you trusted a traffic chain that was already flagged in 2018’s Emma247 case. so tell me this: at what exact second do you stop calling it “efficient dual-stack” and start calling it “willful opacity”?