If Praxis is flipping 3-5 bps cheaper per deposit than PaymentIQ in Curacao, why does our…

Imagine spending months tuning your cascading so that Praxis undercuts PaymentIQ by three basis points and still watching Polish ZEN partners bleed approvals like a sieve at 78 % while ING’s gateways laugh all the way to the 94 % mark. Curacao licence is waving in the wind like a red flag over a compliance minefield, and the KYC strings coming out of Polish ZEN look like they’ve been written in crayon instead of ink. The routing table isn’t the culprit here—it’s the MID’s DNA that’s rotting under Curacao’s rules. ZEN in Poland sits in the same sandbox as ING, yet the difference in decline rates isn’t just a rounding error—it’s a full sixteen-point swing. Praxis vs PaymentIQ pricing is almost meaningless when the backend is choking on KYC velocity: missing PESEL, mismatched ID scans, or even a postcode that hasn’t been registered since 2012. Curacao’s rolling reserve and KYC refresh cycles hit harder than ING’s, where they can push documents through a local bureau in hours instead of days. Add rolling chargebacks on ZEN because Polish banks treat Curacao MIDs as second-class citizens, and you’re back to square one regardless of how cheap the interchange is. Hidden costs aren’t hiding—they’re front and centre. Every 78 % approval at ZEN burns margin on chargebacks that ING never sees. Factor in the rev-share clawbacks when the GGR slips below the MID’s payout threshold, and you’ve priced the “3-5 bps cheaper” argument straight into the ground. Fix the KYC pipeline before you tweak the cascading; otherwise you’re optimising the wrong maths altogether.

PESEL... is that like a Polish SSN? 🤔 And if one's missing or out of date, does the whole thing just flat-out reject on ZEN? Or is it more like the system sends it to manual review and we lose time (and customers)? Go easy on me here, total noob about the local nitty-gritty!

PESEL isn’t some fancy polish thing, it’s just Poland’s national ID number, the one that sits on every Pole’s birth certificate, driving licence, even their fridge when they order a telco sim. the whole KYC check on ZEN chokes on two things: missing pesel or a mismatch between the id scan and the pesel name/date of birth combo. if the customer types his name slightly wrong at checkout or the scanner croaks on the id photo, the gate slams shut before the payment even hits the PSP — no manual review, just a straight 403 with a “contact support” line that 78 % of players never bother with. meanwhile ING’s local bureau runs the same data through a polish civil registry api in 20 minutes, so even if the pesel is dodgy they queue it for a quick call and move on. Curacao’s rolling reserve adds insult because the MID coughs up chargebacks long before the KYC paperwork ever catches up — and by then the player’s already bought another coffee and clicked away.

Poland’s KYC stack has a sneaky hidden cost most miss: the mid-month household ID cross-check. Every Polish bank’s gateway (yes, ING too) quietly links PESEL to the registered address in the Powszechny Rejestr Mieszkańców—so if your customer’s PESEL says Warsaw Śródmieście but the utility bill says Pruszków, even a perfect name/DoB match will get rejected at acquirer auth before it hits PSP. ZEN’s Curacao MID runs that cross-check only once a week because the rolling reserve clock forces the PSP to batch KYC docs; ING gateways hit the same registry every single live transaction via a local sandbox API that updates in 30-second real time. That’s the 16-point gap you’re staring at—nothing to do with basis points.

Yeah, so we’re all chasing those magic 3-5 bps savings while the real killer sits right in the PESEL-to-registry mismatch dance Curacao forces us to do on a shoestring schedule.