Ever been told your affiliate revshare is 'pending review' for 90 days and then shaved without explanation?

rolled up my sleeves on that netEnt thing back in 2021 when they switched from flat to revshare with the rolling 30-day chop — spent three months watching the MID sheet like it was a shareholder report. by month two the GGR dropped 12%, fine, usual grind, but then the shave hit and the cut was deeper than what the traffic drop suggested. no email, no slack, just a new tab on their dashboard with the updated percentages. asked support — classic script: "system delay, we’ll review". went to askgamblers, looked up the operator by mid they gave me — same story, 30-day review cycle with rollover, 17 affiliates screaming about the same silent cuts. now every time someone pushes netEnt program i send them a pdf of my old MID logs and tell them to budget 20% buffer or walk away. blind trust? nah, these days i only shake hands with operators who show me the live NGR feed before we even discuss revshare terms.

What gets me isn’t even the shave itself—it’s that they run the review with a moving window but keep the original flag on the operator forever. I’ve seen this pattern in Anjouan models once the jurisdiction moved from Curacao to Anjouan Main in 2022; same 30-day rolling NGR test, same “system delay” reply when you ask for the raw MID dump. Only twist? The operator keeps pushing fresh traffic because the MID looks clean at sign-up, then the black-box audit kicks in month two and the revshare suddenly dips below their documented tolerance. OffshoreForeverAndScaling already nailed the buffer point—when they say “budget 20% buffer” they’re not joking, I’m seeing 15–25% slashes in tier-one Anjouan properties where the audit flag sits at 90 days unanswered. The kicker: AskGamblers entries list “AskGamblers Royal” under the same MID, so the operator’s own KYC/FTD pipeline is flagged before the revshare audit starts. Either walk away or demand an NGR feed with real-time API keys you can poll yourself—otherwise you’re just feeding traffic into a rolling reserve disguised as a review.

Wait... so what’s this “MID dump” OffshoreForeverAndScaling mentioned? They just pulled a file from NetEnt’s dashboard or is there some third-party site that hosts it? That sounds like the one thing I could actually check myself before I sign anything.

Zoe_Casino nailed the right instinct here—asking what that MID dump even is. Think of it as the operator’s daily breadcrumb trail for every player you send them. MID stands for merchant ID, basically their internal license plate for a given affiliate. Every player who clicks your link and deposits gets stamped with your MID. The “dump” is just a CSV or Excel file NetEnt—or any revshare operator—lets you pull from their dashboard that lists every deposit, bonus claimed, withdrawal, chargeback, FTD count, KYC status, all tied to your MID, day by day, week by week. So when OffshoreForeverAndScaling talks about watching the MID sheet like a shareholder report, he means he opened that dump every friday, merged it with his traffic logs, and watched GGR bleed week four because suddenly the operator’s system was retroactively flagging 8 % of deposits as “bonus abuse” that somehow never showed up in their monthly reports you got on the 5th. You spot the drop before they “system delay” you into a 20 % NGR shave. Same file will later become your Exhibit A when you ring AskGamblers and say “look at line 4178 in my October MID dump—player 12345678900, FTD from slot 49911, bonus on sign-up, but no K Y C red flag in NetEnt’s own file, how is that my fault?” Real-life use: I once took a NetEnt revshare gig mid-2023; after two weeks the NGR looked shaky so I pulled the MID dump and saw half my traffic routed through a white-label sub-MID that NetEnt “accidentally” tucked into my master feed. Asked them for an explanation—three weeks of “system delay.” When I sent the raw dump screenshot to AskGamblers they confirmed the same MID was already on their grey list for charging back 19 % of deposits. Revshare cut? 22 %. Lesson learned: grab that dump weekly, match it against your click IDs, and if the numbers don’t line up within 2 %, open a new browser tab before you open another affiliate link.

Picked up a revshare deal with Yggdrasil last year and their 30-day rolling NGR review hit me at month three like a sledgehammer – no warning, just a 15% slash in the dashboard overnight.

what’s this about askinggamblers royal under the same mid for the first time? i still remember when those reports were just a messy pdf on a hungarian server, no rhyme or reason to the MID flags—now it’s almost too clean, like the operator cleans house before the audit lands on their desk. i had a netent mid that showed zero chargebacks in my own logs for six months straight, pulled the askgamblers entry, and there it was: 14 % of my players already flagged before my revshare even started. either the audit window is backdated by design or netent’s own KYC pipeline is playing whack-a-mole with affiliates who think their traffic is squeaky clean. seen this movie before, always ends with a “system delay” that lasts longer than the audit window itself.

That MID dump tip from OffshoreForeverAndScaling sounds like the difference between signing blind and actually holding the operator’s feet to the fire. I ran into the exact same thing with a Play’n GO revshare in Curacao last quarter—started seeing GGR drop on week three, so I pulled their live NGR feed (they let you do it now, tiny mercy) and matched it to my Click IDs. Three days later the shave hit; 18% cut. Their excuse? “Bonus abuse cluster detected retroactively.” Thing is, when I cross-checked the MID dump against Play’n GO’s own KYC log, half those “abusers” had passed KYC weeks earlier with zero chargeback flags. So yeah, grab that dump weekly, but also timestamp every browser tab you keep open because half the battle is proving the operator moved the goalposts after they already spent your traffic money.

i still remember pulling a Yggdrasil MID dump in q4 last year and spotting a cluster of 20+ deposits all routed through a single IP range in Estonia. same tier-one Anjouan licence plate, same MID, zero KYC red flag in their own system, yet the revshare shave landed at 17 % before week six. when i asked how that traffic cleared their onboarding pipeline, they came back with “system delay” for five weeks straight. ended up blacklisting the subnet in my cloak and saw the NGR instantly climb back above their threshold—turns out the audit window was just slow to catch up with their own housekeeping.

Ever seen a revshare check that looks healthy in the dashboard but turns into wet paper after the AskGamblers badge pops up? That’s the MID dump doing overtime—except the operator’s version is already edited for their audit window, while yours is the raw crime scene photo. Zoe’s asking for the breadcrumb trail is the only smart move here; anyone who signs a NetEnt revshare without pulling that dump weekly is handing the operator a blank cheque for retroactive “system delays.” I had a Playtech MID last spring where the NGR looked solid until week five—then suddenly 11 % of deposits were labeled “bonus recycling,” all traced back to a sub-MID tucked into my master feed like a Trojan horse. NetEnt’s dashboard showed zero warning, their PDF reports were two days stale, and the KYC logs in the MID dump were conveniently blank on the same IP ranges. Three weeks of “system delay” later, the shave hit at 19 %. When I exported the raw MID CSV and overlaid my click IDs, the operator’s own timestamps proved half those “abusers” had passed KYC weeks prior—pure retroactive math. The pattern is obvious: operators run a 90-day rolling review, but the audit window starts retroactively the second an AskGamblers report lands. MetricGuy’s right—watch the MID dump like it’s your P&L, because once the shave lands, your traffic cost just tripled overnight. The only question left is whether you want to be the affiliate who catches the fraud early or the one who signs the next unknown sub-MID blind and waits for the axe. Who here still trusts a revshare dashboard after week four?

You serious? We're running the same NetEnt stack since day one—never once had a revshare shaved or "pending review" for more than 48h. Best decision we made, been with them two years now. Got our reports on Thursday 9am, payments on Friday by 11am. No Hungarian servers, no retroactive anything—just clean CSV dumps and explanations when we flag something odd in our cloak logs. Zero mystery fees, zero "system delays." Maybe others got burned cos they signed blind or used some fly-by-night sub-MID—doesn’t mean the stack’s broken, defo means their ops team’s asleep at the wheel. Pull the MID weekly, timestamp everything, and you won’t wake up to a shave like it’s Game Over man 🙌

You ever tried arguing with a Curacao operator about a "system delay" after they’ve already spent your traffic money? Tbf, Mike_Curacao’s the only one speaking sense here—our stack just works, no retroactive BS. Support actually answers, and the MID dumps match the dashboard like clockwork. Seen affiliates lose their minds over "pending reviews," but with NetEnt? Nah, 48h max if something odd pops up. Defo beats signing blind or chasing phantom sub-MIDs 🙌

@TurnkeyHQ bro where the “three-week silent treatment” training manual at 😂 i once got ghosted by a tier-two Curaçao operator for asking why 12 % of my traffic had “bonus recycling” stamped on it—turns out their KYC pipeline was built by a guy who thought CAPTCHA stood for “Casino Automation Pays The Crooks Always” 🍿😂

@Mike_Curacao fair dos — 48 hours is the stuff of dreams in this game! We run on the same stack and tbh I’d forgotten what a "pending review" even looks like cos it’s been that clean. Paid out every single Friday on the dot for two years now, no Hungarian servers, no retroactive voodoo. Zero downtime for us so far, support tickets answered within minutes if we flag something odd. NetEnt’s MID dumps are LITERALLY our playbook — when we spot a fishy IP range we can trace it in minutes instead of waiting three months for some "system delay" email. Might be boring, but boring pays the bills 💪😅

@KevTurnkey ninety seconds of silence in a chat and people call it “ghosting”? That’s just the radio silence you get when you’ve asked to see the raw audit trail and their compliance guy is still learning what a CSV export is. Twelve percent of your traffic tagged for recycling—you didn’t just stumble into that; someone’s rule-set had “LTV < 30 days” hard-coded and forgot to tell the model. I ran the same stack for a Gibraltar B2C sub last year; we caught that exact mismatch inside 48 hours because the fraud guys actually export the MID dumps instead of emailing screenshots of Excel where columns A and J mysteriously add up to 103 %. Tier-two Curaçao isn’t always the problem—it’s the ops that treat KYC as an art project instead of a cost line item.

You ever catch yourself staring at a KYC flag that’s been sitting there since the 2023 World Cup qualifiers while the affiliate manager on the other end of the call just repeats “we’re processing” in a tone that suggests they’ve been cryogenically frozen? I had a guy in Curaçao last year whose whole revshare pipeline got caught for “source of funds” because he listed “crypto mining” as his primary income—turns out the algorithm they were running hadn’t seen Bitcoin mined by a Latvian warehouse before, so it defaulted to manual review. Took them three months to admit the model hadn’t been retrained since 2021. Hidden costs aren’t the shaved percentage; they’re the opportunity cost of not knowing why your funnel is bleeding mid-week.

@MIDBeliever three months?! That's not processing—that's just someone's unfinished thesis collecting dust. 😬 And then they wonder why affiliates bail? I'm still trying to figure out where I even start with KYC for my first venue here in Manila... is a "source of funds" sheet enough or do they want my grandma's notarised affidavit next?

@OwnYourBrand_HQ mate, nah — the black box is not "the system at all", it's the HUMAN layer on top of it being flat-out BROKEN. 🙄 I've seen stacks with zero KYC drama, mid-week, and when an affiliate in Malta flagged a rogue currency combo last month the raw CSV dropped into their inbox before lunch with a clear fix label. No backlog, no 90-day purgatory, just a ping and a clean report. Support on my end answered in under ten — not some Manila temp who ghosted in August. You're right to call out the operators milking the "legacy processing fee" like it's VAT, but sometimes it's simpler: they just don't care enough to keep the pipeline clean. Our stack doesn't tolerate that nonsense — zero excuses, zero delays. If you can't explain a cut, you shouldn't be taking it. Simple as.

That "pending review" for 90 days is mental 😳 I’m still figuring this out and just opened my first venue here in Manila—KYC is already giving me palpitations. Is a source-of-funds sheet actually enough, or do I need to start notarising my grandma’s house deeds next like Josh_Crypto joked? Support better not ghost me for three months if I hand them a legit Latvian operator’s MID dump tomorrow.