EU operators hitting 2

Just picture the accounting nightmare you get when Trustly chargebacks at 2.7% start to erode the same GGR pool that BCB ACH sits on for five days after payout. I’ve watched rev-share on Neteller Corporate land inside 24h, only to watch 1.8% of the same player’s turnover evaporate in chargebacks before KYC even finishes its dance. Look, the problem isn’t the bank—it’s the model. At what GGR threshold does Trustly turn from “oh, another 3% cost bucket” to “license to launder with instant reversals”? Most Tier-1 operators I audit cap at 0.6% on the KYC stack and 3DS at registration. Two-thirds of the 2.7% we’re seeing are FTD wallets that vanish before the first 3DS roundtrip; banks flip the chargeback because the user never validated the card, not because the merchant failed. BCB’s T+5 is painful, but it’s still better than running 2.7% reversals with zero cover because your rolling reserve hasn’t reached the MID drawdown yet. I had a Curacao license last cycle: moved 30% of volume to Trustly, kept Neteller Corporate as settlement window. Result? GGR dropped 2.2% in three weeks while FTD ratio doubled. Neteller Corporate kept rev-share cash flowing so I could still pay affiliates, but the rolling reserve was bleeding 1.5% a month before chargeback interest kicked in. Bottom line: if you can’t hit 0.8% chargeback on Trustly with strict 3DS+KYC, you’re funding your competitors’ marketing budget—simple as that.

So... what's this "MID drawdown" thing again? 🤔 I thought the rolling reserve was the scary part... is that where you get your margin eaten if the MID runs dry? Or am I mixing this up?

MID drawdown is when the merchant account's available balance gets dipped into by the processor because the rolling reserve wasn’t big enough to cover chargebacks. picture it like your wallet getting lighter while you’re still waiting for Trustly’s T+5 to settle—only the money’s already gone. example: you’re sitting on a £100k GGR day, Trustly comes in at 2.7% chargeback rate. if your rolling reserve is only 5% and the MID runs dry after week two, the processor pulls the shortfall from whatever’s left of your Neteller Corporate settlement (the one that cleared in 24h). suddenly you’re paying for yesterday’s FTD party out of today’s affiliate payouts. not fun when your rolling reserve is still playing catch-up with last month’s rolling reserve.

hah, LeeCasino you want me to believe Trustly’s 2.7% reversals are just because “the model” failed, but i’ve launched three brands on Curacao back when the regulator signed papers with a fernando scribble and still remember when Neteller charged thirty cents a ticket flat, no questions asked. in those days we counted chargebacks on fingers and had change left over to buy the CFO a beer. now the new lot scream bloody murder if ACH slips from T+2 to T+5, but let me tell you about the time BCB held a €180k settlement for seven days because we dared mention “rolling reserve disclosure” in the contract—t+7, mind you—and guess what? the chargeback rate that month was 0.3%. three days vs seven, same pain, different decade. ScaleOrDieOffshore you’re right that banks run the back office, but only because operators forgot how to run their own KYC stack past the registration form. i had a player last quarter who “done this 10 times” and still managed to upload the same blurry id front and back for both face and address proof—took my ops guy two weeks to notice because the passport expiry date was photoshopped with a crayon. meanwhile Neteller Corporate settled in 24h because Neteller Corporate actually does KYC before the first deposit hits their ledger, not three chargebacks later. funny how that works. and LeeCasino your Curacao experience echoes what i saw in Manila: push 30% of volume to Trustly, watch the GGR haemorrhage like a gutted tuna, then blame the bank. but let’s be real—the rolling reserve you mention is usually sized for the MID drawdown scenario only after the damage is done. BCB’s T+5 ACH delay is annoying, but it gives you a five-day buffer to look at the FTD wallet flags before the money ever leaves the merchant account. Trustly’s 2.7% chargeback rate? that’s not a payment method problem, that’s a compliance amnesia problem. most Tier-1 operators i know who sleep at night keep Trustly at 0.7% max by slapping 3DS v2 at registration and freezing the wallet until the ID scan hits the KYC chain—no exceptions, no appeal. otherwise you’re basically inviting every 19-year-old in Estonia to “test” your welcome bonus with a stolen Paysafecard and disappear before the first withdrawal window even opens. Spreadsheet_24 mixing up rolling reserve and MID drawdown is like confusing a band-aid with a tourniquet. the rolling reserve is the cash parked with the processor that cushions the first wave of chargebacks; the MID drawdown is when that cushion collapses and the processor starts reaching into your next-day Neteller Corporate settlement to cover the overdraft. in practice it looks like this: morning comes, rev-share lands in your master wallet, you glance at the dashboard and see a £20k MID drawdown hit because last week’s Trustly reversals blew through the 5% reserve. happy payout day, right? affiliates get their slice, you get your mortgage payment, the processor gets the shortfall—until the next month’s rolling reserve has finally grown back to cover the hole. the numbers don’t lie, but the way you size that reserve sure does. so here’s a war story: we tried to run Trustly at 2.2% chargeback on a Curacao license—same setup as LeeCasino’s sample—only to watch the rolling reserve bleed 2.4% a month while the Neteller Corporate rev-share was locked in 24h. by month three we were paying our affiliate program twice: once for performance, once to cover the MID shortfall. we flipped the switch, jacked the KYC requirements to passport + utility bill + liveness selfie at registration, dropped Trustly exposure to 0.5%, and—miracle of miracles—the rolling reserve actually started growing instead of evaporating. lesson learned: if your chargeback rate on Trustly is north of 1%, you’re not running a casino, you’re running a charity for fraud rings masquerading as players.

Sitting in my Sao Paulo flat at 2am with a cold cup of coffee and a spreadsheet that already had three red flags on Trustly volume—because, yes, I’m that operator—what finally broke my sleep wasn’t the BCB T+5 delay but the moment the Neteller Corporate rev-share landed and I had to manually move £18k from affiliate payouts into a MID drawdown hole. LeeCasino you’re dead right: if Trustly’s hitting 2.7% with FTD wallets ghosting before KYC even starts, that’s not a settlement window problem, that’s an identity problem. Emma247 when you mentioned the passport drawn with a crayon I actually laughed out loud because my KYC ops girl just sent me a screenshot of a player using a screenshot of his ID against a screenshot of his face—both taken at the same minute in the same lighting. Neteller Corporate settled that 24h later because they do the KYC before the deposit posts; Trustly lets the deposit hit the ledger while the paperwork chases the wind. BCB’s T+5 is tough, but Trustly’s instant reversals are worse because the money’s already gone before you know it’s stolen. RevShare_King the MID drawdown picture you painted—processor dipping into next-day Neteller Corporate to cover yesterday’s FTD party—is why I’m now running Trustly at 0.45% with liveness + biometric + two utility bills at registration. Rolling reserve was sized at 8% last month and we actually saw it climb instead of bleed. But LeeCasino still got me stuck: at what GGR does Trustly flip from “another cost bucket” to “license to launder”? My current slice is 15% of total volume and I’m sweating at 0.45%, but if I push to 30% with a 0.9% rate, is that the tipping point where the rolling reserve gives up and the MID drawdown starts robbing from tomorrow’s affiliate payouts? Anyone actually pulling this off at scale without bleeding through the floor?