After two years of burning cash on BetConstruct and NetEnt feeds that never synced to our…
Ugh, BetConstruct still owes us €23k in unpaid chargebacks from that nightmare rollout in Curacao — two years later and their middleware couldn’t tell live bets from archived ones if you paid it. Softswiss’ raw JSON feeds finally gave us the visibility to chase down those FTDs before they buried us under rolling reserves. Anyone else still stuck with feeds that spit out “sync errors” like a broken slot machine?
Learning from the operators who did it, go easy 🙏
Is rolling reserve *that* number they just automatically freeze from your GGR? Or is it more like a rolling window they dip into when chargebacks pile up? Still figuring this out...
New to this, soaking it up.
you ever tried to bail out a sinking boat with a teacup and still think you're winning — that’s what rolling reserve feels like until you crack the nut.
here’s the deal: when players file chargebacks, the processor (or acquirer, or sometimes the jurisdiction) doesn’t wait for you to scramble — it just yanks money from your GGR slice, up to the agreed percentage, and parks it in a reserve account that “rolls” meaning they keep taking fresh slices out of every new win while the old dispute works its way through appeal. suppose you’re doing €500k GGR monthly with a 10 % rolling reserve: first month they hold €50k, second month they take another €50k while still freezing the first slice, so after two months you’ve got €100k locked and the money keeps moving like a conveyor belt — hence “rolling”. now multiply that by chargeback hell because your feed couldn’t flag the ftds in time and you’re staring at €23k that should never have left the pot in the first place. with softswiss’ raw json feeds we saw every bet hit the api within milliseconds, tagged the early signs of skin-in-the-game problem players, and cut off the bleeding before the rolling reserve had a chance to feast on us — turned a leaky boat into a watertight locker, roughly.
Seen this movie before, operators.
yeah the rolling reserve horror show writes itself once your feeds are deaf and blind 🔥 JackBiz nailed the conveyor belt image—once chargebacks pile up they don’t care if you’re already underwater, they just slice another chunk from whatever GGR you ring in that month. i still get chills thinking how €23k of our Curacao rollout just sat there two years because BetConstruct’s middleware spat out “sync errors” like confetti at a wedding—meanwhile Softswiss’ raw JSON shows every bet heartbeat before it even hits the P&L, so now we can freeze FTD accounts same-day instead of letting them bleed us dry while the reserve rolls on. question for OpsLead_Pro: if a jurisdiction freezes a 10 % rolling reserve but you win an appeal and claw back the money three months later, do they release the whole frozen slice at once or does it drip-feed back into your ledger over time?
Asking daft launch questions — that's the job.
gotta love how a €23k chargeback snowball becomes a €100k rolling reserve horror show when your feed decides to take a coffee break every time a bet lands 😭 been there, ran it on CPA and watched the payouts get rejected one by one because the NetEnt feed couldn’t tell the difference between a live punt and a rerun — Softswiss JSON kept us alive, otherwise we’d be praying to the chargeback gods like it’s 2021 all over again
The line on my deals keeps moving.
Softswiss JSON is the closest thing we’ve got to a chargeback exorcist these days. BetConstruct still calling? Laughable. Two years on €23k and they’re “investigating” — classic. My Georgian host kept me on life support with NetEnt’s rubbish feed until I ditched them for Softswiss; now I see every push notification the second it lands, FTDs flagged before they even top up their wallet. Last month alone we chopped three players red-flagged by the bot for turning over 3x deposits in 48h — no more rolling-reserve picnic, just clean ROI.
Traffic quality wins.