Folks who grab the Curacao sub-license at ~EUR 2 k and outsource the cashier to…
So the math on EUR 2 k sub-licence + CryptoLogic white-label barely keeps the lights on at EUR 1 M GGR? 🤔 Would anyone take a second look at the bankroll rakeback spreadsheets before they lock in another EUR 56 k “done for you” package?
Learning from the operators who did it, go easy 🙏
Grace, you're staring at the wrong dial. The EUR 2 k sub-license isn't supposed to carry the whole stack of compliance licenses like a mule—it’s the door hinge, not the roof truss. CryptoLogic’s White-Label does give you a cashier and tech backbone, but you still need your own layer of analytics to know where the rakeback ends and the disaster begins. I’ve seen operators book 15 bps rolling reserve on EUR 1 M GGR with that stack and still miss the leak: 8 bps KYC bottlenecks eating the other 7 bps alive. That leak is invisible until you run daily MID feeds through an ACH-preprocessor that flags velocity spikes the moment a player hits EUR 50 k turnover in 48 h. Without it, FTDs and chargebacks wipe the rakeback math before you even smell the first euro of the "EUR 2 k net" promise.
I keep my own cost models 📊
What's an ACH-preprocessor in plain words? Is that something we just plug into CryptoLogic's backend or do we need another vendor for that? It sounds like the kind of thing that would eat another EUR 5 k a month if it's not already bundled... and I don't even know what to search for to find it 😅
the question isn't whether you need velocity monitoring—of course you do. the problem is where the hell that velocity flag lives. most white-labels give you a dashboard, but they’re blind to MID hits before the cashier catches fire. so an ach-preprocessor isn’t some fancy add-on; it’s the glue between crypto rails and traditional banking feeds that tells you *today* if your star EUR 100 ftd player is about to blow past €50k in 48h because the front-end cashier only notices when the chargeback lands. think of it as a bouncer at the door: the white-label serves drinks, but the preprocessor decides who’s on the guest list before the crowd storms the bar. and yes, it usually lives as a standalone pipe—cryptoLogic doesn’t build that stack themselves, so you’re shopping around for a vendor who speaks ISO8583 and samurai-grade velocity rules. you’ll spend maybe 3k–5k a month on the licence, plus another 200–300 for the feed mapping, but the alternative is chasing ghost rakeback while your rolling reserve silently swallows the difference.
Launched a few, lost money on more 😉
Crazy how it all boils down to pennies... 😅
I get Grace’s math pinch—EUR 2 k licence feels like skating on thin ice when the "done for you" package just whacks another EUR 56 k on top. But then Lee drops that horror story about the 8 bps KYC leak and my brain short-circuits—how do we even fight fires we can’t see?
NickCuracao nailed it: you need that ACH-preprocessor bridge before the chargeback lands, no two ways. But Steve just popped the obvious question everyone’s too afraid to ask—where *exactly* does that preprocessor live in the stack? Because if CryptoLogic’s dashboard is already shouting “ERROR: NEED MID FILTERING” every time I blink, I don’t want to pay someone another EUR 5 k a month just to glue two APIs together.
Is there a mid-tier vendor out there that bundles this dirty work into something close to the EUR 2 k licence fee? Or do we all end up playing Jenga with third-party feeds and pray the bouncer doesn’t eat our margins alive?