A remittance company might have a sleek mobile app, a fast user interface, and competitive exchange rates. But none of that matters if it cannot get money into a recipient’s bank account, mobile wallet, or hand at a cash pickup location in the destination country.
“Accessing local banking systems” is the unglamorous plumbing that makes the entire industry work. It involves a complex web of licensing, partnerships with local financial institutions, and technical integrations with domestic payment rails. The design of this access layer determines the speed, cost, and reliability of a transfer.
The licensing prerequisite
Before a remittance company can operate in a country, it typically needs a government-issued license. The type of license and the difficulty of obtaining it varies dramatically by jurisdiction.
In the United States, for example, there is no single federal money transmitter license. A company must obtain a separate license in nearly every state. This process can take years and cost millions of dollars in legal and compliance fees.
In the European Union, the Payment Services Directive provides a more unified framework. A license issued in one EU member state can be “passported” to allow operations across most of the bloc.
Many countries in the Global South have their own unique regimes, ranging from highly permissive to extremely restrictive. Some countries require a joint venture with a local partner; others mandate that all remittances flow through the central bank.
Direct bank account holding
The most capital-intensive approach to local access is for the remittance company to open its own bank account in the destination country. This requires establishing a legal entity, passing local due diligence, and maintaining an ongoing relationship with a local bank.
Once the account is established, the company can prefund it with local currency. Payouts are made directly from this account via the domestic payment rails (such as ACH, SEPA, or local RTGS systems).
This model offers the most control and often the lowest per-transaction cost. However, it requires significant upfront capital and ongoing treasury management to ensure the account is always sufficiently funded.
Partnering with local banks
Most remittance companies do not have the scale or resources to hold accounts in every market. Instead, they partner with local banks that act as payout agents.
In this model, the remittance company sends instructions to its partner bank, which then disburses funds to the recipient. The partner bank handles the integration with the local payment rails and the “last mile” delivery.
The tradeoff is cost and dependency. The partner bank charges a fee for each transaction. If the partnership sours or the bank decides to exit the remittance market, the company may lose access to an entire corridor.
Connecting to mobile money networks
In many developing countries, particularly in Sub-Saharan Africa and Southeast Asia, mobile money has become the dominant form of digital finance. Millions of people who don’t have bank accounts use services like M-Pesa, GCash, or Wave as their primary financial tool.
Remittance companies access these networks by establishing technical integrations with the mobile money operators. This typically involves an API (Application Programming Interface) connection that allows the remittance platform to credit funds directly to a recipient’s mobile wallet.
These integrations can be built directly with the mobile network operator or through an aggregator—a company that has already done the work of connecting to multiple mobile money systems and offers access via a single API.
The role of aggregators and “Payment as a Service” providers
Building direct integrations with dozens of banks, mobile money operators, and local payment systems across different countries is a massive undertaking. Many smaller remittance companies offload this complexity to specialized providers.
These “Payment as a Service” (PaaS) or aggregator companies have already done the licensing, built the integrations, and established the local partnerships. A remittance company can connect to the aggregator’s single API and gain access to its entire network of payout options.
The tradeoff is an additional layer of fees and dependency on a third party. The aggregator also controls the relationship with the local rails, which can limit the remittance company’s ability to negotiate better rates or prioritize certain delivery methods.
Technical integration with domestic payment rails
Regardless of whether a company uses its own accounts, a partner bank, or an aggregator, the final step is integrating with the country’s domestic payment rails. These are the systems that actually move money between accounts.
Common examples include:
- ACH (Automated Clearing House) in the U.S. for batch-processed transfers.
- SEPA (Single Euro Payments Area) for euro-denominated transfers in Europe.
- Faster Payments in the UK for near-instant domestic transfers.
- UPI (Unified Payments Interface) in India for real-time mobile payments.
- Pix in Brazil for instant payments between any account.
These systems have their own message formats, settlement schedules, and compliance requirements. A technical integration is not a one-time event; it requires ongoing maintenance as the rails evolve and update their specifications.
Cash pickup networks
Despite the growth of digital finance, cash pickup remains a critical channel, especially in countries with low bank account or mobile wallet penetration.
To offer cash pickup, a remittance company must partner with a network of physical agents. These can be dedicated agent locations, retail stores (like pharmacies or supermarkets), or post offices.
Managing a cash pickup network is operationally complex. It requires ensuring that agents have sufficient cash on hand, monitoring for fraud, and handling disputes when a recipient claims they didn’t receive their funds.
Large Money Transfer Operators (MTOs) like Western Union and MoneyGram have spent decades building these agent networks. Newer fintech entrants often partner with these existing networks rather than building their own.
