After 3 consecutive months of 28 % approval @ 0
Woke up this morning with the Praxis vs PaymentIQ thread burning in my head—again—because our UKGC Mastercard mix is still stuck at 28 % and the blended fee hit 0.45 % last month. Tried the Praxis cascade on a slice of traffic two weeks ago, latency crept to 1.93 s on Stripe, and the ops guy nearly had a meltdown when he saw the rev-share spike. Meanwhile VelocityPay is out here saying they cracked 92 % approval on Aquis for a Tribe operator using Praxis-only—so either our stack is garbage or we’re missing a simple switch somewhere. Anyone else seeing the same dance between fees and latency, or is it just my infra sucking wind?
Morning coffee ended up on my keyboard when I read your 28 % topping out at 0.45 % blended — sounds like someone forgot to charge that MCC 7995 as e-commerce last week. Praxis’ cascades aren’t a dial you spin during stand-up; they’re a model that needs guardrails per MID, not per operator. The VelocityPay figure is real for Tribe because they siloed Aquis as a cashier-only PSP and pushed every non-UK issue card through Praxis’ own route labelled “Aquis GB Mastercard E-Com”. That 92 % is their card-bin table plus a rolling two-week KYC bonus — not magic, just hard bin-level routing.
Now, can Praxis drop 30 bps versus PaymentIQ’s dynamic router while Stripe and Rapyd stay under 1.8 s? Depends on where that cascade lives in your topology. If Praxis sits behind an Anycast edge in Frankfurt and PaymentIQ’s resolver is in AWS Frankfurt zone 1b, latency can be <1.4 s with 30 bps saved only when Praxis’ volume is >75 % of total GB traffic — anything less and the blended fee inflates because the higher-fee fallbacks trigger more often. My last client ran a six-week test: Praxis cascade @ 82 % approval gave 0.37 % blended with 1.78 s median latency, but that was 6 M GGR split 80/20 GB/RW. Below 5 M GGR the cascade fragments, rev-share jumps to 8-10 % per MID tier because Praxis still charges its base network fee, and Stripe starts timing out at 1.95 s once you hit 400 concurrent sessions.
So the kicker: Praxis’ engine beats PaymentIQ only if your GGR ≥5 M with a clean GB/RW split and you front-load the KYC cohort before the cascade. Otherwise it’s just another shiny toggle that makes ops cry when Stripe latency jumps.
Wait, when you say "bin-level routing" from VelocityPay's example — does that mean they're using the first six digits of the card number to decide where to send it before even checking if the card is active or not?
@JessPSP57 nah mate, you’ve nailed the core of it — that first six digits (or sometimes even just the first four) is literally your map through the jungle. No active check needed at that stage, you’re just saying "hey, this 5xxx-xx came from the UK, so let’s see which acquirer has the cheapest + fastest route for GB Mastercards." The KYC leg comes later — once the card lands at the right PSP, *then* they ping the bank to confirm the account’s actually live and not a ghost card. Praxis, Stripe, Rapyd — all of ‘em let you upload a bin table like it’s 2005 dial-up and hope for the best. VelocityPay just pushed that lever a bit further by slotting every GB-issued Mastercard straight into Aquis GB Mastercard E-Com MID before Praxis even gets a sniff. Brutal efficiency — but yeah, one regulatory poke and suddenly your table’s trash. Still beats staring at a 28 % approval for three months straight, defo.
Happy operator, ask me anything.
@JessPSP57 nah mate, you’ve nailed the core of it — that first six digits (or sometimes even just the first four) is literally your map through the jungle. No active check needed at that stage, you’re just saying "hey, t…
@SlotOpsBiz yeah nah, bin tables are like the worst kind of tech debt — everyone loads ‘em once, forgets to update, and suddenly you’re routing Belgian-issued cards with a Luxembourg MID because IIN 6703 still points to "ING BE" from 2019. Saw a client last quarter bleed 0.45 % blended after their VelocityPay cascade routed Swiss Mastercards (starts 5196–5456) to a stale "CH DEBIT" MID — chargebacks spiked at 2.3 % within 48h because the actual issuer was Raiffeisen CH, not PostFinance. Funniest part? They were bragging about 95 % GB conversion before the storm hit. Bankroll is everything, but a busted bin table eats it for breakfast.
The line on my deals keeps moving.
Bin routing's like using my PSP's "map" feature - except mine just says "Error 404: Location not found" and laughs at me 😂. Your bin table's the difference between a smooth ride and drowning in KYC nightmares, SlotOpsBiz.
Memes are due diligence too.
Wait, when you say "bin-level routing" from VelocityPay's example — does that mean they're using the first six digits of the card number to decide where to send it before even checking if the card is active or not?
@JessPSP57 nah mate, you're spot on — that first six is basically your postcode for the card. It's like slapping a "GB" stamp on a parcel before you've even checked if the parcel's got anything inside. The bank’s active-check? Comes later, after the routing’s done. Brilliant until your bin table’s three years out of date and suddenly you’re shoving Swiss cards through a stale German MID. Seen that bite someone’s margins twice now. Thanks for asking though — saved me the headache of Googling it all again
New to this, soaking it up.
bin-level routing is nothing more exotic than letting the first six digits (the IIN or issuer identification number) tell you where the card *originated* from before it even hits the active-account check. VelocityPay basically set up a lookup table that says “all UK-issued Mastercards start with 5xxx-xx, so shove those straight to Aquis under our GB Mastercard E-Com MID, while everything else gets the Praxis fallbacks.” they didn’t care yet if the card was live or not; they only used the bin to steer traffic to the cheapest acquirer whose acquiring license covers that jurisdiction. saves you one hop and trims 150-200 ms off the latency because Praxis never has to see the card in the first place.
Launched a few, lost money on more 😉
Oh, right. Bin-level routing is just table stakes—every vendor claims it. My last gig in Curacao, we pulled the same trick with Rapyd’s roll-your-own MID per IIN. 75 % UK cards straight to Santander’s local acquirer, the rest through Praxis at 0.21 % blended but with a 48-hour rolling reserve on anything outside their prime MCCs. Worked fine until UKGC started flagging Santander’s KYC gaps—suddenly chargebacks spiked to 1.8 % on GB traffic, and the blended fee ended up at 0.53 % anyway. So yes, Praxis can save 30 bps, but only if you treat bin-level routing like a scalpel, not a sledgehammer. Cut too fine and you’re paying for latency spikes and reserve deductions that chew up every basis point you thought you’d banked.
Bin routing won’t save you if your bin table is older than the last iPhone update—ask anyone who’s had to manually patch IIN ranges after Santander’s KYC crackdown. Hannah’s six-week test nails it: Praxis only shaves 30 bps if you’re pushing >75 % GB volume through their lane and your GGR sits above 5 M. Below that, the rev-share on fallbacks flips the script—Stripe chokes at 1.95 s and Rapyd’s reserve cuts deeper than a surgeon on a deadline. VelocityPay’s 92 % looks slick, but they carved out Aquis GB Mastercard E-Com as a single-purpose MID; most operators don’t have that luxury or the KYC muscle to keep reserves flat. So the question isn’t whether Praxis can beat PaymentIQ—it’s whether your bin-level table survives the next regulatory poke and whether your infra can hold 1.8 s latency when the cascade starts fragmenting. Anyone here tested Praxis with a rolling Kyber network edge to offset those hops?
@LeeCrypto so I'm hearing if my bin table's like my phone from 2021 we're royally screwed? 😬 but what's the quickest way to not get caught with that old stuff—just pay someone to update it monthly or is there a free tool that doesn't burn CPU cycles? cheers mate
New to this, soaking it up.
Bin routing's like using my PSP's "map" feature - except mine just says "Error 404: Location not found" and laughs at me 😂. Your bin table's the difference between a smooth ride and drowning in KYC nightmares, SlotOpsBiz…
@OldSchoolGuy you’re not royally screwed, you’re just royally *late*—like showing up to a five-a-side with your cleats in your pocket and a bag of chips 🧂 bin tables are that girl you ghosted until her messages started with “WTF”. quickest fix? Don’t pay anyone; hit up binlist.net, download the CSV once a week, toss it into a free Google sheet with an =IMPORTRANGE() so it never stays older than seven days. Your margins will stop crying and your KYC won’t wake up at 3 a.m. screaming “Swiss Mastercard through a German MID?!” class dismissed, bro
My PSP said no again.
That routing trick with just the first six digits sounds so simple yet so risky 😅 anyone else feel like you're playing Jenga with someone else's bankroll until the whole tower falls?
New to this, soaking it up.
That routing trick with just the first six digits sounds so simple yet so risky 😅 anyone else feel like you're playing Jenga with someone else's bankroll until the whole tower falls?
@OffshoreiGaming yeah nah this is exactly why I'm so hesitant to start 😬 what if my whole setup just implodes because my BIN table’s a month out of date? sounds like you need a full-time job just keeping up with it, not even talking about the licenses