Why can't a US vertical SaaS platform reuse its payments program in Latin America?

Because Latin America is not one market and none of it runs the way the US does. Acquiring economics differ by country, the dominant rails are local instant-payment systems rather than the card networks, the regulator is a national central bank with its own KYC and data-residency rules, and settlement and FX add a layer the US program never had to think about. The strategy and the model logic carry over. The infrastructure does not.

What payment rails matter most in Latin America?

The local instant-payment systems, more than the card networks. In Brazil that is PIX, which went from launch to dominant in a few years and is largely free and real-time. In Mexico it is SPEI, with the CoDi QR layer on top. Colombia is rolling out its own interoperable instant system. A platform that only accepts cards leaves most of the addressable volume on the table, because in several of these markets the instant rail, not the card, is how people and businesses actually pay.

What translates from a US payments program to Latin America and what does not?

What translates is the thinking: product judgment, the ISV-versus-PayFac model decision, the monetization and margin-compression patterns, and the right questions to ask a provider. What does not translate is the infrastructure: the acquiring economics, the rails, the regulatory relationship and the settlement and FX mechanics all have to be rebuilt for each market. Operators who lead with the strategy and rebuild the stack do well. Operators who assume the US plumbing ports do not.

What are the common ways a platform enters Latin American payments?

Three patterns recur. A US or global platform partners with a cross-border specialist that already holds the local rails and settlement, the model dLocal and EBANX built. A Latin-America-native company builds in-market first and then expands, the path Nubank took. And a vertical SaaS platform embeds local payments through a gateway or managed partner, which is the same build-versus-buy decision it faced at home, just with a different set of providers and a steeper regulatory layer.

Cross-Border Embedded Payments: What US Vertical SaaS Gets Wrong About LATAM

When a US vertical SaaS platform with a working payments program starts looking at Latin America, the conversation almost always gets filed under international expansion. New geography, new sales team, translate the product, hire a country manager. That framing is the first mistake, and it is an expensive one, because the hard part of Latin America for a payments-present platform is not go-to-market. It is that you are walking into a different payments stack with different rails, different regulators and different settlement, and the program you spent years building in the US does not port.

The good news is that the strategy ports even when the plumbing does not. The way you think about model selection, monetization and provider tradeoffs is the same on both sides of the border. The infrastructure underneath is not. This piece is the honest version of that gap: what actually breaks, what carries over and the patterns that work for operators who get it right.

Latin America is not international expansion for a payments-present platform. It is a different payments stack. The strategy ports. The infrastructure does not.

The four things that actually break

These are the parts of a US payments program that do not survive contact with the region, in roughly the order they surprise people.

1. Acquiring economics

The take-rate math you built in the US assumes a US interchange and processor structure, and that structure does not exist in the same form anywhere in the region. Brazil, Mexico and Colombia each have their own acquiring economics, their own interchange dynamics and their own processor landscape, and they are not interchangeable with each other, let alone with the US. Brazil alone has features the US simply does not, like the deeply embedded culture of card installments, where a single purchase is split into monthly payments and the economics of who funds that float run through the whole acquiring chain. If you carry your US spread assumptions across the border, the model breaks on the first real volume.

2. Local rails matter more than the card network

This is the one US operators underweight the most. In several of these markets the dominant way money moves is not the card network, it is a local instant-payment rail. Brazil's PIX went from launch to ubiquitous in a few years, it is real-time, it is largely free and for huge swaths of commerce it is simply how people and businesses pay. Mexico has SPEI for interbank transfers with the CoDi QR layer on top, and Colombia is rolling out its own interoperable instant system. A platform that lands in the region accepting only cards has quietly excluded most of the volume before it processed a transaction. The rail is not a feature you add later. In these markets it is the market.

3. The regulatory layer

Your US payments compliance does not transfer, because the regulator is now a national central bank with its own rulebook. The Banco Central do Brasil and Banxico in Mexico set the terms for how payments operate, how merchants are onboarded and verified and increasingly how data is handled and where it lives. Brazil's data-protection regime adds residency and handling obligations on top. Standing up in one of these markets is closer to launching a regulated local business than shipping a feature, and the platforms that treat it as the latter find out otherwise during their first audit.

4. Settlement currency and FX

Even once the money moves, getting it where it needs to go is a new problem. You have to decide whether merchants settle in local currency or US dollars, and either choice carries an FX spread and a hedging cost the US program never had to price. Some markets add capital-control friction on top, so moving funds across the border is not the instant, frictionless step a US-only operator assumes. The FX and settlement layer is where a deal that penciled out on the acquiring spread can quietly lose its margin.

The four things operators get right

It is not all rebuild. The most valuable things a good payments operator carries are the ones that travel, and they travel intact.

Product judgment translates. The instincts that make a platform good at payments at home, knowing what to build, what to buy, where the merchant experience actually matters and where it does not, are not country-specific. A strong product leader reads a new market faster than they expect, because the underlying questions are familiar even when the answers are not.

The model decision translates. Whether to refer, run a managed program or build the full stack is the same structural choice in Sao Paulo as in Atlanta, even though the providers and thresholds differ. If you have worked the build versus buy versus partner decision once, you already have the frame for doing it again in a new market.

The monetization economics translate. The shape of how a platform makes money from payments, and the way that margin compresses as the merchant mix shifts, follows patterns that look familiar across borders. The numbers change but the structure of how a platform earns on payments does not, which means an operator who understands their US economics can reason about the LATAM version quickly.

The operator questions translate. The right things to ask a provider, about downstream risk, about pricing under a shifting mix, about who actually handles a frozen merchant, are the same questions that matter anywhere. A platform that learned to read a US provider knows how to read a local one. The checklist carries even when the names on it do not.

The three patterns that work

Across the operators who have actually done this, three repeatable patterns show up.

The global platform with a local partner. A US or global company partners with a cross-border specialist that already holds the local rails, the regulatory standing and the settlement plumbing. This is the model dLocal and EBANX built their businesses on: one relationship that abstracts away the per-country complexity. It is the fastest way in and the one that keeps the least control, the same tradeoff as buying a managed program at home.

The native company expanding out. A Latin-America-native operator builds deep in one market first and then expands, regionally and sometimes into the US. Nubank is the obvious example, a company that earned its home market before reaching outward. For a US platform this pattern is less a path to copy than a competitor to understand, because the native players move with an advantage on the local stack that an outside entrant has to buy or build.

The vertical SaaS platform embedding via gateway. A software platform adds local payments by integrating a gateway or managed partner, market by market. This is the same build-versus-buy decision the platform already faced in the US, with a different provider set and a steeper regulatory layer. The logic is identical. The diligence is heavier, because now the provider you lean on is also your compliance and settlement bridge into a market you do not natively understand.

What this means for the operator reading this

If you are a US vertical SaaS CEO or CPO weighing LATAM, the move is to stop scoping it as a go-to-market project and start scoping it as a payments-stack project per country, beginning with the one market that matters most to your customers rather than the whole region at once. If you are a PE operating partner diligencing a payments-present platform on a LATAM scaling thesis, the question is not whether the product can expand but whether the payments economics survive the rails, the regulator and the FX in each target market, because that is where the thesis lives or dies. And if you are a LATAM operator reading US payments commentary, the translation runs both ways: the strategic frame is shared, and the operators who win on either side are the ones who respect what does not port.

Wherever you sit, the honest answer is the same one it always is: it depends, on the market, the model and the merchant base. The frame is portable. Which market to enter first, how to structure the stack and where the economics actually break for your platform is the part that only resolves against your specific situation. If you are weighing a move across the border right now, that is the conversation worth having before you commit. Reach out and we will work through yours.

Cross-Border Embedded Payments: What US Vertical SaaS Gets Wrong About Latin America