Company profile · 3 min read
BlindPay: stablecoin and bank-rail payments API
BlindPay gives fintechs and software teams one API for bank transfers, stablecoin settlement, virtual accounts and compliance workflows.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
What it does
BlindPay is a stablecoin and bank-rail API for global payments. One integration can receive and send fiat, move stablecoins across blockchains, create virtual accounts and handle compliance workflows such as KYC, KYB and transaction monitoring. The YC profile describes the LatAm and cross-border payments problem; the current homepage presents the product as payment infrastructure for companies and AI agents.
The fit is a fintech, marketplace or software company that needs local payment rails and stablecoin settlement without stitching together country-specific providers. The product is technical and regulated. A buyer needs to understand who holds funds, which entity handles compliance, how quotes expire and what happens when settlement fails.
Why I’d look closer
BlindPay exposes an unusually usable developer surface. The docs describe abstracted bank-rail flows and advanced wallet/blockchain flows, sandbox and production instances, webhooks, quotes, authorization and execution. The docs state that BlindPay is non-custodial, with funds remaining under the customer’s control and returned if a payment cannot settle.
Pricing is public. The pricing page lists Basic at $399/month billed annually with 500 customers and 500 compliance checks, Business+ at $1,599/month billed annually with 10,000 customers and checks, and Enterprise custom. The plans include virtual accounts, off-ramp, wallets and international wires, with transaction fees added by the customer. That makes the first cost conversation concrete, while compliance and country coverage still need verification.
The founder context fits the rails. The YC biographies describe Bernardo Simonassi with stablecoin payroll and PicPay instant-payment experience, and Gustavo Marinho with LatAm consumer-finance product experience. The source profile also describes Joao Borges as a blockchain founder and operator.
What I’d ask
Which countries, licenses and payment methods are live for the buyer’s use case? What are the KYC/KYB escalation paths, quote-expiry behavior, sanctions controls and reconciliation guarantees? I’d run sandbox payin and payout flows, inspect webhooks and failed-settlement behavior, and confirm the custody and data boundaries before moving production money.
My editorial take
BlindPay is a credible infrastructure shortlist for teams that need cross-border money movement and can handle the compliance work. The docs and pricing are real advantages. The product earns trust through settlement behavior and regulatory clarity, not stablecoin vocabulary.
Quick facts
| Field | Sourced detail |
|---|---|
| Buyer fit | Fintechs and software teams embedding global payments |
| Public pricing | Basic $399/month billed annually; Business+ $1,599/month billed annually; Enterprise custom |
| Developer surface | REST/API, SDKs, webhooks, sandbox/production instances and public docs |
| Custody claim | Docs state non-custodial processing; verify legal/operational scope |
Sources checked
Checked 2026-09-19.
| Source | Used for |
|---|---|
| YC company profile | Product, founders and payments problem |
| BlindPay homepage | Current infrastructure surface |
| BlindPay pricing | Public plan prices and limits |
| BlindPay docs | Payment flows, custody, compliance and developer model |
Cohort context
BlindPay is listed in Winter 2025. In our 2026-09-18 directory snapshot, 12 of 165 listed companies in that cohort have YC’s primary industry label Fintech (7.3%). 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:19:26.550Z 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 | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Observed |
| Pricing link | Observed |
| llms.txt link | Not observed in this response |
| Markdown alternate | Observed |
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 ↗