The Real Opportunity in Brazil's CPF Nightmare for Tourists

Imagine landing in Rio de Janeiro, excited to explore, only to hit a wall when trying to book a hotel. You need a CPF (Brazilian taxpayer number) to pay online. You don't have one. The hotel offers an alternative form, but that requires a Brazilian phone number. To get a phone number, you need a CPF. Catch-22. Your only option? Show up in person and pay.

This story, posted on Pieter Levels' blog, resonated with thousands. It's a relatable frustration for anyone who's tried to navigate Brazil's bureaucracy as a tourist. But here's the thing: while the post points to a real friction point, it overstates the problem. The claim that this makes booking hotels "impossible" is misleading. Most international booking platforms like Booking.com, Expedia, and Airbnb don't require a CPF. They handle payment abroad, bypassing the local tax system. Tourists who book through these channels rarely encounter the problem.

So who actually feels this pain? Smaller local hotels, guesthouses, and tour operators that aren't on global OTAs. These businesses rely on direct bookings via their websites or phone calls, but their payment systems are built around CPFs and local phone numbers. When a foreigner tries to book, the system breaks. The result: lost bookings, frustrated guests, and a reliance on word-of-mouth or WhatsApp to get paid.

At PainSignal, we track 13 problems in Travel & Tourism, with an average severity of 3.6 out of 5. Among them, a "small retreat business needs flexible payment processing" (severity 3/5) and a "tour company relies on OTAs with high commission" (severity 4/5). These aren't isolated incidents—they show a pattern of payment friction that hits local businesses hardest. The CPF catch-22 is just the tip of the iceberg.

What the original post misses is the opportunity. There's a clear gap for a payment solution that works for tourists without a CPF. Imagine a fintech product that integrates with local booking systems, allowing tourists to pay via credit card or international transfer without ever needing a Brazilian tax ID. The merchant receives settlement in BRL, and the platform handles compliance. For indie hackers and vibe coders, this is a prime niche: a focused, high-friction problem in a specific geography, with a clear customer segment (small hotels and tour operators) and a willing payer (tourists who want to book unique spots).

Consider the scale. Brazil welcomed over 6 million tourists in 2024. Many travel beyond the big cities to smaller towns, beach hostels, or eco-lodges. These places are often the most authentic experiences, but they're also the most underserved by global payment infrastructure. By solving this single pain point, you could unlock a massive, underserved market.

The technology is straightforward: a simple payment gateway that generates a local payment link, accepts international cards, and converts to BRL. The hard part is compliance—handling foreign exchange, anti-money laundering, and the ever-changing Brazilian tax rules. But that's exactly the moat. Most global fintechs won't bother with a niche like "tourist payments in Brazil." That leaves the door open for a scrappy indie hacker who understands the market.

To make this concrete, look at the data. We've seen problems like SettleFlow, a payment processing issue for retreat businesses, and numerous others that mirror the friction described in the original post. These problems share a common thread: local businesses wanting to accept foreign payments but unable to because of CPF requirements. A solution that plugs into their existing booking workflow (even a simple CRM or WhatsApp bot) could be built in weeks, not months.

The real question isn't whether the problem exists—it clearly does. It's whether you see it as a complaint or a blueprint. The author of the original post did everyone a favor by highlighting this friction. Now it's up to builders to turn that frustration into a product.