AB831 now names Stake’s affiliate network and payment facilitators, but how quickly will…

I still have that scar tissue from the Curacao "affordable" licensing phase too—imagine finding out Paysera’s MID cut its carding rate by half by routing grey traffic through a Lithuanian shell while the paperwork said “digital wallets only.” EvoPlay’s affidavit doesn’t read like a compliance filing, it reads like a vendor directory compiled over one all-nighter in a Tallinn coworking space. The moment Nevada’s investigator sees Paysera’s name tied to sweepstakes that aren’t regulated as sweepstakes in Delaware but are labeled as such in an EvoPlay contract, the PSP license evaporates faster than a player’s bonus balance when the first chargeback hits the MID.

That Lithuanian shell routing isn't some theoretical boogeyman—last year a DACH operator I consulted had Paysera’s "digital wallets only" MID funneling Lithuanian-registered traffic through a Maltese acquirer licensed for e-commerce. The KYC stack read "EU-resident natural persons" while the banking feeds showed webrooms in Klaipėda and Vilnius charging back 18% of the NGR. When the Latvian FIU flagged it, Paysera scrubbed the MID within 72 hours, leaving that operator with a 3-month frozen rolling reserve and a rev-share clause that couldn’t cover the clawback. Nevada isn’t inventing anything new here; it’s just running the same playbook with brighter lights and fewer shells.

Yeah nah, I worked with Paysera once when they still had that "one-click KYC in 60 seconds" badge on their site. Took me six months to get a clear MID history because every time I asked for a breakdown it was "oh, that was just a demo MID, bro". Meanwhile my GGR was getting sliced by some Lithuanian shell they "forgot" to mention. And HannahOffshore is dead right—when the chargebacks hit 15% on what was supposed to be clean EU traffic, Paysera's compliance guy ghosted faster than a player after a bad beat. Now EvoPlay drops Paysera and Crypto.com Pay in the Nevada affidavit like they're collecting rare pokemon cards? Regulators will circle like seagulls at a casino buffet—first grey stream and those PSP licenses are gone before you can scream MID freeze.

Just woke up to this dumpster fire like it’s a 4am chargeback explosion. Another operator here who learned the hard way when Paysera’s “demo MID” turned out to be funding 70k in unstamped Delaware sweepstakes for a crypto casino—NGR looked fine on paper until Nevada OSI noticed the MID was registered to a shell in Šiauliai that wasn’t even in their KYC matrix. Regulators didn’t ask questions; they hit the switch within 11 days. The rev-share agreement had a clawback at 125% of NGR, so once Paysera froze the MID the balance went straight to negative overnight. Seen the same story with Crypto.com Pay—last year they marketed “registered MSP in MGA & VG” on their deck, but when a single Dutch grey-stream slipped through their VASP screening, the Nevada letter arrived within 48 hours with a 30-day suspension threat. Their compliance team bounced the ticket to Malta faster than an affiliate migrates to Curacao when taxes rise. EvoPlay waving these vendors in the affidavit is like handing Nevada a roadmap. Once one PSP name gets linked to a non-compliant stream, the dominoes drop before you can update the rolling reserve report. Moral? If your affiliate network has Paysera or Crypto.com Pay in the stack, go easy on me—rip them out today or you’ll be explaining to the regulators why your NGR read like Monopoly money after the MID freeze.

what’s the point of an affidavit that reads like a vendor shopping list from a black friday blowout when every processor on it has a trail longer than my uncle’s credit card statements during the holidays? back when i was still launching a few of these and curacao licenses cost less than a decent mid-tier affiliate manager’s monthly salary, i saw the exact same movie—vendors promising “no kyc,” “instant mid,” “chargebacks? what chargebacks?” only for some overzealous regulator to pull the plug because one stray stream crossed a line thinner than my patience after the third espresso. the difference now? nevada isn’t sending polite letters; they’re holding court with subpoenas and mid freezes faster than you can say “rolling reserve evaporation.” the real kicker isn’t the vendors—it’s the affidavit itself. evo’s list doesn’t just name processors; it maps the supply chain in crayon, with arrows pointing straight to grey-sweep territory. regulators don’t need a microscope when you’ve handed them a treasure map. and those psp licenses? gone. evaporated. the moment nevada’s investigator ties paysera’s mid to a delaware sweepstakes mislabeled as “digital wallets only,” the license doesn’t get suspended—it gets shredded, and the psp won’t lift a finger because their own midi is already bleeding from clawbacks. remember when crypto.com pay marketed msp credentials in vg and mga while quietly routing dutch traffic through a lithuanian shell? took regulators 48 hours to send the suspension letter. that’s not regulation—that’s swatting a fly with a sledgehammer, and the fly is your license. so if your stack still has paysera or crypto.com pay in it, do yourself a favor: grab a sharpie, draw a big black circle around those mids, and rip them out before nevada does it for you. rolling reserve reports look a lot better when they’re not in the red because your psp just ghosted you. ah well, we'll see

What, exactly, makes you all so sure Paysera and Crypto.com Pay are the canaries in this coal mine rather than the miners themselves? I’ve worked with both—Crypto.com Pay when their deck still listed “registered MSP under MGA and VG” but their compliance emails routed to an entity in Labuan that only held an offshore PSP license for e-commerce, not gaming. Paysera? Their “Lithuanian shell routing for Delaware sweepstakes” wasn’t a secret; it was an open checkbox in their MID application when I did a review for a Seychelles operator in 2022. The real question isn’t whether regulators will yank a PSP license—it’s how many of these affidavits like EvoPlay’s are simply lining up the usual suspects so Nevada can pick off the weakest link and declare a win while the rest scatter. If the goal is deterrence, fine—but let’s stop pretending this is about ethics and start calling it what it is: a high-stakes game of regulatory whack-a-mole where the moles move faster than the mallets. And by the way, have any of you actually seen Paysera produce a clean MID history that didn’t require three separate KYC matrix reviews and a notarized letter from their Lithuanian acquirer? I could be wrong, but that still reads like wishful filing, not compliance.

I still use Paysera’s MID for a small Delaware sweepstakes wrapper, but only because their Lithuanian acquirer shows up on every regulator query with a full MID paper trail—dates, UBOs, bank refs. Three separate KYC reviews? Yeah, I did them too and they matched. Not wishful at all. Where I crashed was when I let an affiliate flip a US traffic stream through Paysera’s Lithuanian shell in week two; regulators saw the Delaware label but the MID’s bank feed said “Klaipėda B2B,” flagged it as grey within 48 hours, and froze the rolling reserve at 200% of the NGR. No moralising—just practical maths. If Nevada rolls out the same template as last year’s Curacao “affordable” phase, Paysera’s MID vanishes faster than the tiny balances we all used to laugh about. Do you still think the paper trail counts for anything once one label doesn’t line up?

A Lithuanian shell MID routing through Klaipėda with a Delaware label isn’t just a red flag—it’s the exact pattern we flagged in our 2023 MGA audit for a Curacao operator who swore Paysera’s MID was "EU-compliant." The operator’s KYC matrix pointed to "EU natural persons," but when the MGA pulled the MID banking feed, the remittance descriptor read "Klaipėda B2B" with UBOs listed as two shell companies in the Šiauliai free zone. Paysera’s compliance response? They sent an updated MID agreement that backdated the registration by six months—Conveniently, just after the first FTD spike. By the time the rev-share clawback hit, the operator’s rolling reserve was already at 240% of NGR, and Paysera’s Lithuanian acquirer shut the MID before the auditor could finish the sentence.

Had to laugh when someone called Paysera’s MID history “clean” after three KYC reviews—I remember my own Lithuanian shell MID where the UBO list changed faster than a mid-tier affiliate manager’s LinkedIn headline. Funny how every “EU-compliant” vendor suddenly forgets the Klaipėda B2B route once the Delaware label flips grey on them 🤣 Meanwhile Crypto.com Pay’s Labuan entity still shows up in their deck like a “trusted MSP,” but we all know Labuan’s gaming license is basically a receipt printed on coconut fiber 😂 Point is, if your rev-share says “no clawbacks” while the MID screams Šiauliai shell, you’re already 30 days from a regulator’s red pen—better rip the Band-Aid before they do.

looked at all the yelling and remembered the summer we signed up with Paysera for a Delaware wrapper because their Lithuanian acquirer swore on their mother’s grave that the MID was squeaky clean—turned out “Klaipėda B2B” was just a polite way of saying “who even knows who owns this,” and Delaware regulators didn’t care how many KYC reviews we did when the MID’s bank descriptor screamed “offshore noise machine.” got our rolling reserve frozen at 235% of NGR inside five business days, and Paysera’s response was a two-page pdf titled “revised UBO timeline—backdated six weeks.” regulators don’t read pdfs—they read bank feeds, and those feed don’t lie about Klaipėda. so the question isn’t whether the paper trail counts; it’s how many revisions you’re willing to accept before the psps auditor calls it a ghost ship. anyone who still thinks the mid is “clean” after seeing that Klaipėda descriptor should open an offshore fund instead of a casino

Funny you all keep treating Paysera’s Lithuanian MID as some sort of compliance talisman because they “matched three KYC reviews.” Have any of you ever pulled the actual banking feeds beyond the first glossy PDF? I did when I was cleaning up a Curacao operator’s mess in 2023—same “clean MID” story, same backdated UBO timelines, same Klaipėda B2B descriptors. The moment Delaware flagged the grey-sweep Delaware label, Paysera’s Lithuanian acquirer sent us a two-page revision titled “UBO timeline correction—backdate six weeks.” Delaware didn’t blink—they froze the MID at 240 % of NGR inside 72 hours and clawed back every FTD from the last quarter. The paper trail wasn’t just wishful; it was actively rewritten. Now someone claims Crypto.com Pay’s Labuan shell is merely “marketing fluff.” Look at their MSP deck from Q1 2023—it still lists “registered under MGA and VG” while the operational routing table quietly bounces US traffic through an unlicensed entity in Labuan with zero gaming authorization. The Maldives Gaming Authority revoked a MID for the same Labuan shell six months ago—did any of you actually check whether that revocation got reflected in Crypto.com Pay’s disclosures? Regulators don’t play “label update roulette”; they look at the live MID feed, see “Labuan B2B,” and treat it as grey by default. The fact that Crypto.com Pay still slaps “EU-compliant” on their website is marketing math, not compliance math. EllieCPA’s Delaware wrapper survived because the Lithuanian acquirer’s name showed up on “every regulator query.” That’s circular reasoning—if Paysera only updates the acquirer name after every audit notice, the trail stops being predictive the second you need it most. And “rolling reserve frozen at 200 % of NGR” isn’t practical math; it’s post-mortem loss. The cost model already broke the day that Klaipėda descriptor appeared, long before the freeze. CasinoOps_iGaming nailed it: regulators read bank feeds, not KYC matrices. The feed doesn’t lie about Klaipėda; the feed doesn’t lie about Labuan. So spare me the romantic notion of a “paper trail”—if your MID routing changes faster than your affiliate manager’s mood, you’re not compliant; you’re just renting time until the next subpoena.

for the love of all things offshore, let's not pretend we're surprised when the regulators start picking off the vendors whose bank feeds scream "grey" louder than a seagull on a chippy truck klaipėda isn't some random baltic town—it's the siren song of shell accounting, and anyone who still thinks it's a compliant route should book a holiday there and see how many "natural persons" actually live above the mushroom farms. you don't build a MID under a lithuanian shell just to comply; you build it to disappear around corners, and regulators know it. the fact that three different operators are now recounting identical tales of frozen rolling reserves and backdated ubo timelines tells me we're not dealing with outliers—we're dealing with a business model masquerading as compliance paperwork. even crypto.com pay's labuan "license" reads like a prank when you glance at the maldives regulator's public revocation list—yet half the industry still treats their deck as gospel because the design is pretty. the only thing cleaner than these mid tracks is the whiteboard in a compliance officer's head after they've spun those ubo revisions for the fifth time. regulators aren't playing whack-a-mole; they're playing chess, and they've already moved three pawns into position while we're still arguing over whether the paper trail is "clean enough." so tell me—when the next nv audit drops and the freeze hits, will we blame the psp for not updating fast enough, or will we finally admit we knew the klaipėda descriptor was ticking from the day we signed the mid? ah well, we'll see