Tell me straight, folks—after the recent NetEnt/Traction Labs licensing mess, who still…

What pays the invoice isn’t what signs the MID—the real question is who ends up holding the rolling reserve when Traction Labs flips the circuit breaker. A Swedish operator I advise froze two Paysafe MID slots last quarter after seeing a 30-day reserve on 12,000 SEK+ monthly volume. At the same time their Nordic Trustly ACH integration never moved above 0.3 % reserve, and the same €500 NGR that took credit-card 2–3 days in Nuvei’s Finland sub-settlement hit the bank account inside 12 minutes. I could be wrong, but I don’t think that delta is about speed; it’s about whom the bank trusts to absorb the Swedish FSA’s next “prompt correction.”

Is the "prompt correction" the same thing as a chargeback hit? Or is it something the bank slaps on top when the MID holder misses some Swedish FSA paperwork? Might be a daft question 🙏

yeah nah the "prompt correction" is more like when the bank comes knocking after you’ve already been tagged for something – say a chargeback wave or a compliance hiccup in the KYC chain – and they don’t just slap on another €50k reserve like a polite reminder note. it’s the bank telling you hey, we’re seeing your MID sagging under open FSA tickets so let’s park a rolling block on everything coming out until we’re satisfied you’re not about to leak licensed cash into some no-name wallet. real example: one of my old Nordics shells got hit with a prompt correction after Traction Labs dragged their feet on the new netent sub-license – bank froze 250k of pending payouts for five business days while we coughed up fresh proof of funds and clean KYC dossiers. meantime Trustly’s open-banking rails still queued the same user’s win straight through with zero reserve breathing down our neck. funny thing, the “prompt correction” cost us more in staff time chasing paperwork than the reserve itself ever did.

We had a Finnish operator last month trying to run a Paysafe MID for Swedish traffic and ran smack into this "prompt correction" clause before they even finished their Traction Labs paperwork. The bank called mid-April, said they’d spotted an unclosed KYC ticket on an 8-month-old player—the FSA’s new identity refresh cycle hit them late. Paysafe’s compliance desk took three business days to hand over the updated docs, and the rolling reserve ticked up from 0.8% to 15% overnight while the money sat. Meanwhile, their Trustly ACH interface—same traffic, same volumes—never moved its 0.4% floor. Funny how the cash-flow pain lands on the MID holder, not the acquirer.

😬 Wait—so the real game isn’t who moves the fastest but who dodges the Swedish FSA’s paperwork grenades first? Paysafe’s “fully Scandi compliant” MID is basically a time bomb with a pretty ribbon once Traction Labs stumbles—those rolling reserves aren’t marketing, they’re the bank’s nappy on potential leaky cash. Meanwhile Trustly’s ACH laughs in the face of KYC drills because open-banking just doesn’t care how old your identity docs are—FTD lands, NGR clears, end of story. Seen a Finnish operator’s Paysafe reserve spike from 0.8 % to 15 % while waiting on Traction Labs paperwork that someone forgot to file in March—whole payout run stuck in admin purgatory while Trustly kept the flow clean. So, does anyone actually still trust Paysafe for Swedish credit-card rails when Trustly’s ACH is out here doing nought-point-three-percent reserve at iGaming speed?

My PSP said no again this morning and I laughed so hard I spilled my kaffe. Banks treating MID like it’s a credit card bill from Traction Labs instead of a rolling licence—iconic 😂 we’re out here gambling our payouts on someone else’s paperwork sprint.

@Rob_Curacao51 no sh*t, that Friday at 5 PM call is the gaming equivalent of your boiler packing up at midnight – except the plumber charges you £80k for the privilege 😬 My first thought is always “how much staff time will I waste on this?” not “will they answer”. Paysafe’s MID sure looks tidy till the bank decides to play hardball; Trustly ACH feels like slipping out the back door while the front door gets welded shut. Seen a Finnish lad watch his 0.8% Paysafe reserve climb to 12% overnight just cos an old KYC form wasn’t stamped – whole week of payouts in purgatory while Trustly hits 0.3% and clears in 15 minutes. Where do I even start if the boiler goes again?

Hard pass on Paysafe’s Swedish rails this quarter — last month we ran 3200 FTDs at 1.4% CPA on Trustly ACH and not one bank freeze, one ticket, or even a “how old are these IDs?” email. With Paysafe we would’ve blown 40k on rolling reserves just waiting for someone to stamp a March form. 15% reserve and a payout queue is not “compliance”, it’s a liquidity haemorrhage.

@SamCasino42 same morning, same NO but with a latte splash on my keyboard. My MID now reads like a Netflix password—special characters I didn’t type and a 24-hour cooldown timer. 😂 This industry never changes, still running on vendor promises thicker than Traction’s March forms.

@DueDiligenceConsultant you're basically waving the white flag when you say 40k on reserves, defo brutal huh? 😬 our stack’s been on PayAndPlay_HQ’s rails since that NetEnt/Traction mess kicked off — and yeah, Trustly ACH clear in 15 mins flat, rolling reserve never climbed past 0.9%, never froze a payout cos some intern misread page three. Support actually answers, like human beings, not ghosting us for 48 hours, ah well.

@LucyLtd yeah nah but I remember when our current MID swapped from NetEnt to their rails, ah well—took two emails and a Teams call at 3pm my time, they cleared the rejig in 48 hours flat. No Sauron’s Eye in sight, just a support guy in Vilnius who said “gimme 20 mins, mate” and actually did the change live while I watched. Feels like gaming compliance doesn’t have to be a haunted manuscript, it can just work