If we’re paying north of $0
LatAm onboarding latency with Sumsub is killing my FTD conversion in Brazil—six seconds on paper, twenty on a dodgy Claro network, and we’re still bleeding 2.8 % crypto chargebacks. Jumio’s $0.57 is a joke when it triggers the Akamai IP score like a traffic spike.
New to this, soaking it up.
Hell, every time I see "Instant Face Match" flashing on a vendor slide I picture an intern at Sumsub’s office sprinting from the server rack to the latency monitor with a stopwatch and a caja de café in hand—because six seconds in a demo room means zip in São Paulo during a Claro outage at 3 p.m. Tuesday. Lee_Vault, you’ve nailed the paradox: cheaper per-check does not equal cheaper per-paying-customer when your LatAm funnel bleeds FTDs and rolls straight into 2.8 % crypto CBs. Jumio’s $0.57 is just the sticker price; once your Akamai IP score drops because Jumio uses AWS edge nodes outside LatAm and your Brazilian user’s request takes a world tour, the fraud index stays flat but your true cost per good-funded deposit skyrockets past $2.30 once you weight the rolling reserve dragged by those late-stage chargebacks. The real mismatch isn’t KYC alone—it’s the monitoring stack sitting on top of that latency data. If your vendor still thinks “instant” ends at face-match and forgets about the 3-second rule for Travel-Rule blockchain pings, you’re optimising for the wrong SLA. In Brazil we learned the hard way: spend the extra $0.18 on a CDN-tiered Sumsub instance in São Paulo and drop the Akamai dependency if your churned sessions are above 18 %.
ever wonder why we still let vendors call a 6-second "instant" when claro’s taking a coffee break every single afternoon in sao paulo? i remember back in the old school offshore days—latam was just "where we hide the skimmers" ah well, we'll see.
my first latam brand we went with a top-brand identity vendor priced at $0.42/check because their demo room in miami had fiber. shipped them a bunch of dutch-curacao IP users just to test the hype. latency out of amsterdam hit 14 seconds on a ti phone sitting in rio; by week two our brasilian users sent me screenshots of "error 408 request timeout" while holding their cnpj printouts in the other hand. jumped over to a local ISP-peering identity stack—$0.68/check, took us 1.2 seconds average in rio and 2.1 in bogotá. chargebacks on crypto deposits dropped from 2.7 % to 0.9 % inside two months.
now the new lot never dealt with that pipeline pain because they assume “the cloud is global, right?” wrong. your travelling rule pings don’t care about regional latency budgets. i’ve seen mid-tier vendors bill you $0.39 for what’s basically a lambda in us-east-1 and then charge $1.40 in rolling reserve when a brasilian user bounces off after 9 seconds because the blockchain ping missed its 3-second sli.
so tell me: are we still buying the marketing term "instant face match" or should we start demanding the vendor publish their median sli per country in the contract, not the demo room?
Seen this movie before, operators.
What do you actually mean by "Travel-Rule blockchain pings" when Hannah mentioned the 3-second SLA? Like, is that some kind of real-time transfer ID check or...?
New to this, soaking it up.
yeah nah the travel rule pings are basically the id data packets that bounce between your casino’s compliance desk and the blockchain explorer the moment a user deposits crypto, so both sides can tick the “i know who sent this and where it came from” box. think of it as a quick ping-pong: your system shoots off the customer’s wallet hash plus their name and doc id to the travel-rule vendor (like Notabene or Sygna), that vendor stamps it with a time-stamp and then it gets routed back to you—if the whole round trip takes longer than three seconds you either get a red flag or the deposit sits in limbo because the regulator’s scanner just timed out. in practice this is why sumsub’s demo room “instant” can still brick on a saturday night in mexico city when their singapore node decides to take a coffee break—those pings never hit the latam peering cloud in time, so your 0.9 % fraud index quietly ticks up to 2.1 % because the travel rule “unknown sender” stamp kicks in and your rolling reserve doubles overnight. ah well, we'll see
Launched a few, lost money on more 😉
Wait—who actually told the Brazilian user that a Miami demo room’s fiber can stand in for their Claro outage at 3 p.m.? Jumio’s $0.57 is dirt cheap until you watch the Akamai IP score crater because your São Paulo subscriber’s traffic circles back to US-East-1, the Travel-Rule ping from Notabene hits a 3.4-second timeout, and suddenly your rolling reserve eats the deposit instead. We moved our whole identity stack to a Colo at Tivit’s datacenter in Osasco last month, paid $0.08 more per check, and the median SLI in Brazil dropped from 6.2 seconds to 1.8—our crypto CB rate in LatAm slid from 2.9 % to 0.6 % inside six weeks.
Asking daft launch questions — that's the job.
funny how we’re still debugging a fib that started life in a miami demo room with fiber fatter than a curacao skimmer’s prepaid sim. six seconds there, twelve here, and the vendor’s invoice doesn’t come with a Claro outage clause tucked inside—just “instant face match” stamped in neon. let me ask this: if your Travel-Rule ping misses its own 3-second timeout, does the vendor refund the $0.57 you saved or the rolling reserve they helped you bleed into next week? ah well, we'll see
Launched a few, lost money on more 😉
Can’t help but notice we’ve all spent more time debugging Miami fiber myths than actually processing good deposits in LatAm. The vendor sheets keep flashing “instant,” yet our Brazilian crypto users still stare at a spinning beach ball while Claro refreshes at 3 p.m.—and suddenly the $0.57 KYC invoice looks like pocket change compared to the rolling reserve chewing through next quarter’s NGR.
If the real SLA isn’t face-match latency alone, but the combined travel-rule ping, Akamai hop and Claro coffee break, how do you even begin to write that into an MSA without a clause that says “demo room fiber excluded during São Paulo outages”?
New to this, soaking it up.
Had this exact same Claro-São Paulo-death-ping last summer when a “top-brand identity vendor” convinced me their Miami fiber demo meant squat. Dropped them a user from Vila Madalena, $0.39/check, and our travel-rule ping came back marked 4.1 seconds—because their Singapore node had decided to sip espresso at peak load. By Friday the refund queue was fatter than Real Madrid’s salary cap. Now I rent rack space in São Paulo for $0.07 more and laugh whenever a vendor starts slinging “instant face match” while standing under a palm tree somewhere with fiber thicker than the Curacao skimmers of yesteryear 😂.
Here to argue, not to nod along.