If you need a single dashboard that scores Sumsub, Veriff and Jumio side-by-side on…

Bloody hell, that’s the exact headache I’m nursing right now in Bogotá. You’re not overselling it—OFAC wallet screens are the silent millstone on Pix corridors where three million a day switches hands on Tron and nobody in ops has the budget for a triple-verification loop. Sumsub’s hit-rate looks stellar on paper, but what they don’t advertise is how long the rolling reserve stays locked while the AML team waits for the second batch of images because the first set came back “false-positive insufficient lighting” in a São Paulo favela with dodgy Wi-Fi. In LatAm casinos where the MID usually expects a 14-day reserve release, waiting 48–72 hours for an OFAC hit that still ends up at Veriff for a manual re-screen—where the senior analyst charges $85/hour—sinks your daily NGR faster than a fraudster learning to mimic facial liveness. The nuance they skip in the Visa slide deck is the jurisdictional bite: Mexico and Colombia treat Sanctions lists as secondary; they prioritize identity corroboration first. So Sumsub’s 0.09 % false-positive figure on OFAC SDN-plus crypto wallets becomes irrelevant when the local regulator still demands three matching docs, including a notarised utility bill in the same name. You roll the dice on skipping Jumio, get a clear sanctions screen, but you breach the local KYC manual and land in a fine loop. Bottom line: the lowest false-positive hit-rate is only half the story; tier the vendors by secondary screen depth per jurisdiction before you let the 6-second face-match seduce you.

What exactly counts as a "secondary screen" here? Is it like an extra step they do on top of the sanctions check, or is it another vendor layered in just in case the first one missed something? 😅 Still trying to picture how that slows things down so much in practice.

saw LeeCrypto’s question bouncing around — yeah, “secondary screen” is exactly that layer they bolt on because the first check didn’t look far enough. imagine you run a casino in Medellín and Sumsub scans the OFAC SDN list against your incoming Tron wallet. it flags 0.09 % nonsense — lighting issues, pixelated screenshots, but worst of all it never asked “does this Tron address actually own the Brazil-issued CPF?”. so your ops team flips to Veriff or Jumio not to retest the sanctions hit (that already came back clean), but to pay that senior analyst $85 an hour to dig through Brazilian utility companies, bank statements, CPF ownership records — all stuff the regulators in Mexico or Colombia still demand before they let you release a rolling reserve. it’s a second vendor yes, but also a second bunch of documents, translations, notary stamps, and every extra day the reserve stays frozen you’re bleeding the NGR because Pix settlements aren’t waiting for bureaucracy. when RevShareBeliever talks about 48–72 hour waits with manual re-screens, that’s the secondary screen chewing up man-hours while the Tron $3 M/day corridor keeps flowing past your locked MID. the new lot never dealt with that; they see 0.09 % false positives and think the fight’s won, but down here the fight’s really over who can produce notarised proof that a favela resident in a screengrab actually owns the Tron wallet they funded with a Pix that cleared yesterday at 3:17 p.m.

Man alive, this sanctions dance in LatAm is no joke if you’re juggling a Pix + Tron operation where $3 M/day just keeps spinning. We moved off Sumsub last quarter in Costa Rica after three incidents where the OFAC hit came back clean, but the local regulator still held the MID because the wallet’s CPF ownership matched to a tax debt — the kind of thing Sumsub’s primary scan never looks at. So we layered Jumio strictly for the CPF + ID triangulation layer. Yes, the hit-rate on sanctions itself dropped from ~0.09 % to near zero because Jumio’s secondary screen checks the CPF against federal tax liens; that’s the detail Emma247 nailed. But the real cost isn’t the extra $0.18/check — it’s the 56-hour rolling reserve freeze each time a tax flag flips up. What I don’t get is why nobody quotes the compliance uplift per jurisdiction: in Colombia the tax lien lookup is mandatory for sanctions clearance; in Panama it’s optional but they slap a 12 % rolling reserve anyway. Sumsub’s paper stats look shiny until your finance team slaps a 14-day reserve on every OFAC-clean case because the local AML manual still requires the tax check. My 2 cents: pick the vendor whose secondary screen actually covers the local KYC manual chapter-by-chapter, not just the OFAC false-positive number. That’s where the bleeding happens.

$3M in Tron-Pix corridors locking up every time OFAC fakes a hit—how is that still anyone’s idea of ‘clean’?

@LeeCrypto yea mate, it’s not just “another vendor” slapped on—it’s a second, deeper sweep through local paperwork the regulators won’t skip. One guy yesterday waited 63 hours because his OFAC clean wallet still needed a notarised CPF tax debt check in Brazil; reserve froze while Jumio re-did what Sumsub’s 0.09 % nonsense already passed. That’s the silent killer—your sanctions hit is sparkling, but a favela utility bill and a CPF match can still ground the MID for days.

That rolling reserve in Bogotá? 14 days on a 3-million-a-day corridor is a 42-million liquidity cliff when Sumsub’s OFAC comes back clean but your CPF-to-ID triangulation lands you with a tax lien the AML manual treats as a secondary screen. Jumio knocks that time down to 36 hours for us in Costa Rica, but only because we built the CPF lookup directly into their API call—extra $0.18/check and a one-time dev spike that paid for itself inside two weeks. Mexico’s worse: regulators still want the physical notary stamp on the utility bill delivered to their office, so even an instant Jumio hit leaves you with a notarised-doc queue that hangs up the reserve for an extra five days.