I’m seeing a 30-day rolling window on commission withheld for 3 full months — AGD already…

damn, revshare enjoyer just handed me the exact grenade i've been eyeing from the back of the bus, waiting for someone to pull the pin. when those evo puppeteers drag their 90-day commission timeout into ‘rolling reserve’ they’re not just nickel-and-diming you—they’re playing musical chairs with your cash flow, and the music stopped before the first guy even sat down. you dig into paysafe g2’s transaction-level logs not because they’ll suddenly cough up the missing weeks of csv exports, but because the gaps in their time-series export will tell you exactly where the ledger glitched—or where the internal sql job simply failed to run, buried under some bonus-clogged month-end batch. i’ve seen that particular strain of misfired automation back when curacao ‘confirmed compliance’ by burying traceability six months deep; the hard lesson is never trust the ui, always pull raw data via api (yes, v2, the ugly one that still has mid-layer auth hacks). if you pivot to paddy power betfair’s connected wallet and see the same 30-to-90-day reconciling delay, congratulations—you’ve just mapped the full supply chain of liquidity rape: processor → aggregator → operator → affiliate. at that point escalating to maltese fdl becomes ceremonial; the damage is already done to your daily float. slap every file, api response and email onto a zip with timestamps and forward it to fdl with a one-liner: “prove where each cent has been since inception.” if they want compliance theater, give them theater—straight out of the golden era of ‘cheap curacao’.

Ever touched a MID where the rev-share code runs in Paysafe G2 only to find the same MID being split across two different merchant classifications because some batch job on the 15th of the month flips a flag that was never in scope for the affiliate contract? Happened to me last year—Affiliate ID 94723, base rev-share at 38 %, but Paysafe’s nightly revenue extract had an extra 2 bp row sitting under ‘Bonus Deductions’ labelled ‘Rolling Reserve Adjustment’—no timestamp, no sign-off. Three days of digging showed it was a leftover from a legacy rollover that hadn’t been wired to the new rev-share table in March. EvoPlay Pay simply copied the schema and never switched off the switch. The deeper you go in Paysafe G2, the more you realise their idea of an audit trail is a sequence of CSV dumps you can’t reproduce after the 30-day purge. The raw API endpoint v2/logs/transactions? Still paginates with a cursor limited to 1,000 records; anything older than 60 days gets dumped into a cold storage bucket that costs $0.023 per GB to retrieve—nice little variable cost you didn’t budget for when you signed that 3 % rev-share deal. When the gaps line up—those tell-tale 90-day commission windows—it’s almost never a malicious actor in the next room with a bonus plan. It’s a forgotten script that grew fat on FTD leakage from a dormant skin, now misclassifying affiliate cash flows as “risk exposure” because some risk analyst couldn’t distinguish a real fraud signal from a rev-share threshold breach. Paddy Power Betfair’s Connected Wallet does the same dance: their wallet-side 30-day reconciliation feed reports a settlement date that lags the actual value date by as much as 48 hours if the affiliate flag in their ledger hasn’t been back-filled by the operator’s nightly batch. You’ll spot it because the NGR lines in the raw ledger will have a second entry with an identical transaction_id, but a negative amount—duplicate kill-switch from the operator’s side trying to claw back after the fact. So, before you escalate to Maltese FDL, run two forensic queries yourself. First, pull Paysafe G2’s transaction-level export via API v2 with the MID, affiliate_id, and transaction_type=’commission_withheld’. Look for any record where the created_at timestamp is more than 60 days old but the commission_id still lives in a status of ‘pending’. Second, grab Paddy’s Connected Wallet JSON feed for the same date range and compare the settlement_net field against the net_amount in the Paysafe extract. If they don’t match by more than 0.01 %, you’ve just found your smoking gun: the ledger reconciliation layer is silently cloning transactions and hiding the delta under a ‘rolling reserve’ label that never shows up in the dashboard. Export both files with SHA-256 hashes appended and email them to FDL’s compliance desk labelled ‘Duplicate reconciliation leads to hidden 90-day hold—request full forensic chain from MID creation to final settlement.’ Let them explain why their licensed operator’s ledger contains duplicated entries that re-route affiliate funds into a risk reserve they never authorised in the rev-share contract. Once FDL starts pulling witness statements from Paysafe’s cold-storage team, the bonuses tied to working-capital optimisation suddenly look a lot less shiny.

what's a MID in plain english? when revshare enjoyer mentioned "the same MID being split across two different merchant classifications" i just blanked for a second, is that the operator's bank account number or something sneakier?

kids these days call a MID a "merchant id", and it’s not your bank account or your grandma’s secret stash number—think of it as the processor’s way of ticking your brand inside their ledger so every deposit, withdrawal and payout knows which casino it belongs to. back when curacao licences still cost less than a used ford fiesta, the papers arrived with a slip of paper containing a twelve-digit MID you had to type into the old Paysafe G1 portal; now it’s buried in an api call like `{"merchant_id":"123456789012"}`. picture it like the number plate on a taxi: if you lose control of that plate, some other bloke can run up debts under your name and the money keeps flowing out while the heat lands on you. example on this thread’s mess: your brand signed rev-share at 35 % with EvoPlay Pay, your MID is 987654321098. every player who hits your link makes a deposit to that MID; every wager, win and withdrawal is tagged to 987654321098. when the nightly revenue extract hits Paysafe G2 and pays you a 30-day commission slice, the ledger checks the MID, sees “hey, this MID belongs to affiliate xyz”, and pushes the credit to your connected wallet. flip the coin, and if some batch job—written back in 2021 for a now-defunct skin—still flips a flag from ‘active’ to ‘rolling reserve’, Paysafe will start misclassifying your commission rows as risk exposure instead of cash owed. your daily float suddenly drops because the processor thinks the MID is now “high risk” and slaps a 90-day hold, all because a forgotten sql update once thought rolling reserve was a good idea for dormant skins. fun times.

Funny you two even mention Paysafe G2 because i still have the raw sql dump from that curacao dinosaur skin i killed in q1 2022 — the one that kept complaining about “rogue affs siphoning traffic.” Turns out the “rogue” tag was an old mid-layer join on the legacy rev-share table that never got switched off when the new ggr ledger went live. Paysafe g2’s nightly batch would roll through the dump at 03:17, spot the join flag set to 1 for the old mid (MID 112233445566, rev-share 32%), and append a brand-new row under commission_withheld with the exact amount of the affiliate payout that was already pushed to the wallet three days prior. The flag wasn’t even timestamped—just a bit sitting there since 2019. They finally killed the script when i sent them the full dump with a header that said “stop stealing my traffic, it’s dead.” Funny how an ancient sql snippet outlives the skin it was meant to protect.

Wait, SoftAndReady's forensic playbook just clicked for me because I actually ran into the Paysafe G2 cursor limit last week when I tried to pull a 6-month commission ledger for a new Maltese operator — API v2 spat back exactly 1k rows, then stopped at a cold storage bucket fee warning. That $0.023 per GB isn't listed anywhere in the contract, and the operator signed the 3 % rev-share without asking how much the raw data actually costs once you drift past the "nice UI" window. So yeah, I get why you'd want to burn that whole export to ZIP and hand it to FDL with the clock ticking — but what still bugs me is how many affiliates just shrug and say "paysafe's 30-day purge is industry standard" without checking the fine print that says "unless you're auditing commissions, then good luck." Have any of you actually tried pushing back on Paysafe's support before sending files to FDL? Their replies read like a bot farm cooked up the template at 3am.

yeah LeePayments, that cursor limit’s the real party trick — i was pulling a 4-month rev-share ledger last spring for a malta skin that lost its fdl licence in june, and paysafe g2’s api v2 gave me the classic “you’ve reached your daily quota, try tomorrow” slap when i hit 892 rows. their tier-1 support then sent me a canned reply that the 1k cap is “designed to protect system stability”, as if some random affiliate pulling mid-level data threatens the whole mid-layer plumbing. funny enough, the very same export in pdf format (their so-called “audit ready” dashboard dump) went up to 2,300 rows no sweat — pure theatre to make you think the raw numbers are there somewhere, just out of reach.

Thought the 1k row cap was bad until I tried pulling a year-end commission archive for my little Estonian skin last November and Paysafe G2 spat back “data not found” even though the dashboard showed the cash line. Found out later their cold storage bucket charges $0.023 per GB to rehydrate anything older than 90 days, but their support email said the fee was “included in the processing cost”—which is total nonsense because the contract I signed only listed a flat 3 % rev-share. Emailed FDL asking if this falls under “hidden fees” in the licence terms and got stonewalled for two weeks; ended up doing a manual pivot in Excel from the daily CSV dumps before the 30-day purge hit. Still waiting on an answer—guess maltese patience is part of the licence price.

Paysafe’s G2 feels like it was coded by a sleep-deprived intern who mixed up “audit” with “cold storage taxidermy.” You’re not hunting ghosts when you see 90-day withholds on a MID that ran clean FTDs in Curacao for two years—the ledger is just whispering to a 2019 SQL flag that never learned how to die. Split the MID in Paysafe and yank the raw transaction lines with the old rev-share flag set to 1; that single bit will tell you whether EvoPlay Pay’s nightly batch job is still dancing with dead skins while your commission rots in a queue. If the audit log shows “commission_withheld” stamped three days after the payout already hit your Paddy wallet, you’ve caught the exact row that’s triggering the 3-month rolling reserve—no need to deep-dive G2’s 1k-row curse when one obsolete join can do the math in half an hour. So the next question isn’t how deep you drill, but whose API call you burn first: Paysafe’s death-march export or EvoPlay Pay’s silence?

you ever think these "zombie flags" aren’t just a Paysafe problem? had a skin in Malta last summer where the rev-share row withheld 18k GBP for three months because their internal ledger still read "2022_client_id" in the skins table—turns out their dev team just renamed the columns instead of migrating the damn data. 😂 paysafe’s little curtain-raiser of API cursors and cold storage math is child’s play next to a vendor system that can’t even archive its own ghosts. so tell me, how many other stacks out there are running ledgers that mistake “active” for “we gave up back in 2022”?

Yeah nah, this ghost in the machine racket just made me chuckle and shudder at the same time. We switched to our white-label stack eighteen months ago and I still get chills when I remember the old Paysafe “audit” limbo—three-month withholds, 1k-row cursors, the whole haunted house vibe. With us? Zero drama like that. Raw exports run smooth every night, Curacao skins aren’t haunted by 2019 SQL dumps, and commission lands where it should. Sometimes I wake up thinking we just got lucky—then I remind myself we picked the provider that doesn’t still have cabinets labelled “2019 nightmares.”