
The entry ticket is what you see
When a fintech decides to add a country, the conversation usually starts with the setup: how long it takes to integrate the local payment method, open accounts, sign a provider and pass testing. It’s a concrete cost, with a start and an end date, and it fits neatly into a roadmap.
The problem is that it’s the smallest number. We learned this firsthand: we’ve spent years running ramps, QR payments and virtual accounts in several countries, and the cost that weighs most doesn’t show up on launch day. It shows up six months later, when something changes.
What weighs on you later
A payment scheme isn’t a fixed part. It’s a living system, with rules that get updated, participants that come and go, and regulators that adjust the framework. In recent years, several countries in the region have launched instant payment systems, updated their foreign exchange and virtual asset rules, or moved forward with interoperable QR codes.
For an operator, each of those changes means new work: adapting the integration, reviewing compliance processes, updating reconciliation, notifying clients, and sometimes switching banks or providers. And it doesn’t happen once. It happens every year, in every country.
The costs that aren’t on the roadmap
When we talk to teams considering expansion, we usually walk through this list. None of these items appear in the demo:
Banking relationships. Opening accounts is the start; keeping them, with each bank’s reviews and requirements, is ongoing work.
Local liquidity. Having local currency available when users need it, including outside banking hours, ties up capital.
Compliance by jurisdiction. KYC, monitoring, reporting and limits differ from country to country and keep changing.
Reconciliation. Every rail reports payments differently. An unidentified payment is a support, accounting and compliance problem.
Support and incidents. When a scheme goes down or a bank delays credits, someone has to detect it, explain it and fix it.
People. All of the above requires a team that knows each market.
How to measure the real cost
A practical way to estimate it is to change the question. Instead of “how much does it cost to integrate this country?”, ask “how much does it cost to keep it running for three years?”. A few questions help:
How many times have the regulations or the scheme changed in that country in recent years?
Who on the team will track those changes, and how many hours will it take?
How much liquidity needs to be tied up to operate without interruptions?
What happens to users if a correspondent bank closes the account?
What does a day of downtime in that country cost?
If the answers, multiplied by the number of countries, add up to an uncomfortable number, that’s a good sign it’s worth comparing options before building.
Build or integrate
There’s no single answer. For some companies, running a key country directly is a competitive advantage worth building. For others, especially when the goal is to be in several markets at once, it makes more sense to integrate infrastructure that already operates there and keep the team focused on the product.
A practical signal: if your product team spends more time dealing with banks, reconciliation and regulatory changes than building features for your users, the cost of operating already outweighs the cost of integrating. At that point, it’s worth reviewing which parts of the operation truly differentiate your business and which can be handled by a specialized provider.
What matters is comparing providers on the cost of operating, not just the cost of integrating: who absorbs scheme changes, who maintains the banking relationships, who answers to the local regulator, and how your team finds out when something changes.
The part we take on
At Manteca, we run that layer for our clients. Teams that integrate our API connect once, and we take care of keeping the rails, liquidity, reconciliation and compliance running in each market. When a scheme changes, the adjustment is on us.
If you’re considering new countries and want to see how much of that cost we can absorb, tell us what you’re building at manteca.dev.
M
Written by
Manteca
Considering adding a country, payment method or ramp to your product?
Tell us what you want to build. We’ll be in touch.
