Company profile · 4 min read
Kontigo: stablecoin payments for LatAm
Kontigo combines a USDC wallet, cards, local payment rails and APIs for cross-border consumer and business payments in Latin America.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
What it does
Kontigo is a stablecoin-oriented neobank and payments platform for Latinos in the U.S. and Latin America. Its current homepage presents Kontigo Cash for USDC wallets, a card product, Kontigo Pay for local and global payment methods, and APIs for moving money through wallets and agents. The YC profile describes the original wedge as a USDC wallet, BTC savings account and WhatsApp-based private banker for cross-border transactions.
The fit is a consumer or business operating across currencies and payment systems who needs stablecoin rails plus local conversion and payment options. The current site also names an enterprise/API use case, so the buyer may be a company embedding stablecoin checkout rather than only an individual remittance user. This is a regulated, high-stakes product; “simple” is not the same as low-risk.
Why I’d look closer
The product breadth is concrete. Kontigo’s homepage lists a self-custody wallet, cards, local payment methods, recurring payments and API documentation. It names a public customer set including Yummy, Empresas Polar, Cashea, Burger King LatAm and Crossmint, and reports 300K+ users and 800+ companies. Those are company-reported site claims, not an independently verified customer count.
The founders bring relevant regional-fintech context. The YC biographies describe Jesús Alberto Castillo Ferrer as a Venezuelan founder who previously built a micro-lending platform and Gino Guatavita as a fintech/alternative-data builder in Colombia, Mexico and Ecuador. The public API docs expose guides and references for wallet checkout and payouts.
There is also a status item a buyer should not skip. The public blog index links a security-incident report describing unauthorized account access, impact, containment, refunds and security improvements, and a separate sanctions-procedure announcement. That is not a reason to infer current insecurity; it is a reason to read the company’s own postmortem and verify the present controls, scope and remediation.
What I’d ask
Who is the regulated provider for each wallet, card, payout and conversion path? How do self-custody, recovery, sanctions screening and account-access controls work? I’d inspect the postmortem, current security controls, API permissions, fees, supported countries and customer-complaint process before moving money through the service.
My editorial take
Kontigo is a serious fintech infrastructure profile, not a casual “neobank for Latinos” recommendation. The regional product thesis and API surface are specific enough to investigate. The security-incident and sanctions disclosures make current controls part of the buying decision, not a footnote.
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer fit | LatAm consumers and businesses with cross-border payment needs |
| Product surface | USDC wallet, card, local payment rails, APIs and agent-assisted transfers |
| Public proof | Company reports 300K+ users and 800+ companies; not independently verified |
| Status question | Public blog links a security incident report and sanctions review update |
Sources checked
Checked 2026-09-19.
| Source | Used for |
|---|---|
| YC company profile | Product, founders and original launch context |
| Kontigo homepage | Current consumer/API product surface and company-reported customer claims |
| Kontigo API docs | Public developer surface |
| Kontigo blog index | Linked security-incident and sanctions-procedure disclosures |
Cohort context
Kontigo is listed in Summer 2024. In our 2026-09-18 directory snapshot, 12 of 248 listed companies in that cohort have YC’s primary industry label Fintech (4.8%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:17:15.212Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Not observed in this response |
| H1 or H2 heading | Observed |
| Typed structured data | Not observed in this response |
| Docs/developer link | Observed |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗