To serve a foreign market, companies have long assumed they must put something on the ground there: a subsidiary, a bank account, a local team. Each entity adds compliance, accounting and filing obligations that accumulate quietly. Much of what actually requires local presence is narrower than it looks — often it is simply the ability to receive and send money in that market's currency and on its rails.

What local presence is really for

Strip the assumption down and the requirements are usually three: customers in a market need to pay you, you need to pay suppliers there, and you need to hold value in the local currency. Only the first of those sometimes demands a local entity, and only for particular regulated activities. The rest is about access to rails, not about ownership of a company.

Reaching markets through the network

SUPA's model reaches markets through participants and rails rather than through subsidiaries. A unit holds around ten currencies, sends payouts on local rails, and accesses cards and card acceptance through licensed partners. Card networks, local instant schemes, SWIFT and other rails sit behind rail adapters, and AI routing evaluates available paths by cost, settlement time, reliability and regulatory fit. The operator gets the reach without standing up a company in every country.

  • Around ten currencies in one unit.
  • Payouts on local rails; cards and acceptance via licensed partners.
  • Reach through participants and rails, not local subsidiaries.
  • Routing selected per operation across available paths.

Where an entity is still needed

This is not a claim that entities are never required. Some activities are locally licensed and demand a local presence; cross-border reliance is not permitted everywhere and local-law limits are checked per jurisdiction. Balances sit with licensed partners, as SUPA is not yet a bank. And reliance agreements do not transfer legal responsibility — each party keeps its own duties.

The point is to stop treating a subsidiary as the default first step. For many operators, the reach they need can be assembled from participants and rails, leaving entities for the cases that genuinely require them.

In short:

  • Much of "local presence" is really access to rails and currencies.
  • Units reach markets through participants and rails, not subsidiaries.
  • Payouts run locally; cards come via licensed partners.
  • Entities remain necessary where an activity is locally licensed.

See how reach is assembled: protocol.