Cross-border payments in Southern Africa: rails, costs and who runs what

On four kinds of rail, and the right one depends on who is paying whom, in which country, and how much.

• Bank transfers, settled between banks. Inside the Common Monetary Area (South Africa, Namibia, Lesotho and Eswatini), transfers up to a directive's limit are moving onto TCIB by regulation. For other corridors, your bank chooses the route.
• Mobile money, through an aggregator that connects operators in several countries, or through each operator's own API.
• Remittance providers, which move money for people, usually into a wallet, a bank account or a cash pay-out point.
• Cards, when a customer in one country pays a merchant in another.

This page takes each rail in turn: where it applies, what it costs and who sets the rules. For the domestic rails, country by country, start with payments in Southern Africa. The table below is the short version.

Which cross-border route fits which payment

If you need to	Route to use today	What governs it
Pay people or suppliers in Namibia, Lesotho or Eswatini from South Africa	Your bank's payout channel	Smaller CMA cross-border EFTs leave SADC-RTGS by 31 March 2027 and use TCIB from 1 April 2027
Pay a supplier in a SADC country outside the Common Monetary Area	Your bank's foreign payments channel	Authorised Dealers may only make foreign currency payments for imports against the documents the Currency and Exchanges Manual lists
Collect from mobile money users in Zambia	An aggregator or the operator's own API	pawaPay covers Airtel, MTN and Zamtel in Zambia
Collect from customers in Zimbabwe	Paynow, or EcoCash directly	Paynow's express checkout takes EcoCash, OneMoney, InnBucks, Omari, ZimSwitch and Visa/Mastercard
Send money to a person in another country	A licensed remittance provider	One published price: Mama Money charges a fee of 5% or less to send to EcoCash in Zimbabwe
Charge customers abroad by card	Your South African gateway	International card rates apply, for example 3.1% + R1 excluding VAT on Paystack South Africa

Last verified: 2026-11-04. Sources, checked 2026-11-04 to 2026-11-05: Government Gazette, SARB, pawaPay markets page, Paynow developer docs, Mama Money, Paystack pricing. Each row names the route a builder can verify today. Where a rail is not confirmed at its source, it is left out rather than guessed.

If you need one of these routes built into a product, Mctaba Labs payment integration does that work, from the first API call to the daily reconciliation.

A scheduled change with a hard date. SARB Directive No. 1 of 2025 requires settlement system participants to stop routing smaller CMA cross-border EFTs through SADC-RTGS by 31 March 2027, and to route them through TCIB from 1 April 2027^{[Government Gazette, checked 2026-11-05]}. The directive treats transfers between CMA countries as cross-border EFTs^{[SARB, checked 2026-11-05]}, and its limit is an EFT not exceeding R5 million^{[SARB, checked 2026-11-04]}.

Namibia and Eswatini have their own instruments. Eswatini lists its own CMA Retail EFT Payment Directive^{[Central Bank of Eswatini, checked 2026-11-05]}, and Namibia has published PSDIR-9^{[Bank of Namibia, checked 2026-11-05]} and PSDIR-10^{[Bank of Namibia, checked 2026-11-05]} on these transfers, and Namibia's uses N$5 million as its limit^{[Bank of Namibia, checked 2026-11-05]}. The SARB Governor has also described a step with a lower figure: "By late April, qualifying regional transactions of up to R100 000 should move from SADC-RTGS to TCIB."^{[BIS: Kganyago, checked 2026-11-04]} Plan for the directive's full scope and ask your bank which payments it moves first.

For a builder, the key point is who the rule binds. The directive is addressed to settlement system participants, and as the Governor put it, "at the moment, anyone who wants to access the payment system has to go through a bank"^{[BIS: Kganyago, checked 2026-11-05]}. So a fintech's CMA payouts change when its bank's do. The migration plan is in the TCIB deadline and how to migrate payouts, how TCIB works is in TCIB explained for developers, and the settlement background is in SADC-RTGS and the Common Monetary Area.

For Zimbabwe, Zambia, Malawi, Mozambique, Botswana and Angola, no CMA directive sets the route: your bank or provider does, and exchange control decides the paperwork.

From South Africa, exchange control sets the documents for import payments: under the Currency and Exchanges Manual, Authorised Dealers may only make foreign currency payments for imports against specified documentation^{[SARB, checked 2026-11-05]}. On the receiving side, each country has its own rules. In Mozambique, for example, foreign exchange operations linked to foreign trade, payments and receipts for goods and services from abroad included, go through banks^{[Banco de Moçambique, checked 2026-11-04]}. What South African exchange control means for your code is in exchange control for cross-border payments from South Africa, and the supplier-payment build is in paying suppliers in Zimbabwe, Zambia and Mozambique.

Builders often ask whether PAPSS can carry these payments. We could not confirm its Southern African coverage at its source, so the working answer is your bank's; PAPSS in Southern Africa sets out how to check and what to build on meanwhile.

More than the global norm. Sending $200 to sub-Saharan Africa averaged 8.78% in Q1 2025, against a 6.49% global average^{[SARB-hosted paper, checked 2026-11-04]}, according to World Bank data in a paper on the SARB's site. The same paper ranks one South African corridor among the most expensive: sending $200 from South Africa to Malawi cost 19.4%, second on the paper's list of the most expensive corridors into sub-Saharan Africa^{[SARB-hosted paper, checked 2026-11-05]}, and sending $500 cost 17.2%^{[SARB-hosted paper, checked 2026-11-05]}.

Published provider prices are rarer than they should be. One we could verify at its source: Mama Money charges a fee of 5% or less to send money to EcoCash in Zimbabwe^{[Mama Money, checked 2026-11-04]}. On the card side, a South African gateway charges its international rate when a customer abroad pays, for example 3.50% + R1.50 on Peach Payments^{[Peach Payments fees page, checked 2026-11-04]}.

Whatever the rail, the cost has the same three parts: the fee, the exchange-rate margin, and what the recipient pays to use the money. The only fair comparison is the amount that arrives, priced back at the mid-market rate. The method, and the data behind it, are in remittance costs in Southern Africa and sending money from South Africa to Zimbabwe. Charging customers abroad is covered in international cards on South African gateways.

Every country has its own payment regulator, and a regional product answers to each one where it operates:

Who regulates payments in each country

Country	Payment regulator
South Africa	The SARB, which sets the rules and standards and licenses payment institutions
Zimbabwe	The Reserve Bank of Zimbabwe, under the National Payment Systems Act
Zambia	The Bank of Zambia
Malawi	The Reserve Bank of Malawi, which publishes guidelines for authorising payment service providers
Mozambique	Banco de Moçambique, whose prior authorisation each payment service activity needs
Botswana	The Bank of Botswana, under the National Clearance and Settlement Systems Act
Namibia	The Bank of Namibia, which licenses payment service providers in categories set by PSD-1
Angola	Banco Nacional de Angola, which supervises the provision of payment services

Last verified: 2026-11-04. Sources, checked 2026-11-04 to 2026-11-05: SARB, RBZ, Bank of Zambia, Reserve Bank of Malawi, Banco de Moçambique, Bank of Botswana, Bank of Namibia, lex.ao copy of BNA Aviso n.º 2/22. Eswatini and Lesotho are covered in their own pillar. Licensing rules differ by country, so a regional product needs an answer for each one.

Licensing differs as much as the regulators do. Mozambique, for instance, licenses payment service providers as electronic money institutions, funds transfer institutions or payment aggregators^{[Banco de Moçambique, checked 2026-11-04]}, while in Zimbabwe a non-bank that wants to offer payment services applies to the RBZ for recognition through a deposit-taking partner^{[RBZ, checked 2026-11-04]}. A business model that is simple to license in one country can need a partner bank in the next.

In South Africa, the operators behind the rails are clear. SAMOS is the real-time gross settlement system the SARB owns and operates^{[SARB, checked 2026-11-04]}, and PayInc runs the retail schemes: EFT credits and debits, DebiCheck, Registered Mandate, PayShap and real-time clearing^{[SARB media release and FAQ, checked 2026-11-05]}. How payments work in South Africa explains the domestic side.

For a builder, the practical tool is an aggregator that connects operators in several countries through one integration, with operator APIs where you need depth in one market. Coverage has to be checked country by country and in each direction:

• Zambia. pawaPay covers Airtel, MTN and Zamtel^{[pawaPay markets page, checked 2026-11-04]}, and MTN's MoMo Developer Portal has a go-live application for moving to production^{[MoMo Developer Portal go-live page, checked 2026-11-05]} if you want MTN directly.
• Malawi. pawaPay covers Airtel and TNM^{[pawaPay markets page, checked 2026-11-04]}.
• Mozambique. pawaPay lists Vodacom and Movitel, with Movitel for payouts only^{[pawaPay developer docs, checked 2026-11-05]}, which is why direction matters; pawaPay pairs M-Pesa with Vodacom, e-Mola with Movitel and mKesh with Tmcel^{[pawaPay blog, checked 2026-11-05]}, so mKesh is not on the list. M-Pesa Mozambique runs its own OpenAPI portal at developer.mpesa.vm.co.mz^{[M-Pesa Mozambique Developer Portal, checked 2026-11-04]}.
• Zimbabwe. EcoCash runs an official developer portal for its Open API, with a sandbox and certification before go-live^{[EcoCash developer portal, checked 2026-11-05]}, and Paynow aggregates EcoCash, OneMoney, InnBucks, Omari, ZimSwitch and Visa/Mastercard^{[Paynow developer docs, checked 2026-11-04]}.
• Botswana. pawaPay does not cover Botswana^{[pawaPay markets page, checked 2026-11-04]}, so plan a separate route there.

The verdict: start with an aggregator for breadth, add an operator's own API where volume justifies the extra integration, and keep a coverage table per country and direction in your own documentation. The build is in the pawaPay integration tutorial, and the wider set of providers is compared in remittance APIs for Southern Africa, Onafriq explained and Mukuru for businesses. If your customers are in Kenya, where Daraja is Safaricom's developer portal for its APIs^{[Safaricom Daraja developer portal, checked 2026-11-05]}, with sandbox apps for testing^{[Safaricom Daraja developer portal, checked 2026-11-05]}, see accepting payments from Kenyan customers.

As an option to pilot carefully, not a default rail. The SARB and the FSCA count stablecoins as crypto assets^{[SARB and FSCA joint communication on, checked 2026-11-05]}, and say crypto assets used for payments under the FAIS declaration are not payments under the NPS Act, and are not legal tender^{[SARB and FSCA joint communication on, checked 2026-11-05]}. Cross-border use sits closer to exchange control: the draft Capital Flow Management Regulations were published for public comment on 17 April 2026^{[National Treasury, checked 2026-11-05]}, and the draft defines capital to include crypto assets^{[National Treasury, checked 2026-11-05]}.

If stablecoin settlement interests you, run it through a licensed crypto asset service provider, with legal advice on both sides of the border, and keep a conventional rail ready for every corridor. The detail is in stablecoin rails for cross-border settlement and crypto payments regulation in South Africa.

A regional product holds up when it has one shape, whatever its size:

1. One payment model, many rails. Business logic talks to a single interface; each bank product, aggregator or operator API is one implementation behind it. A rail change, such as the TCIB move, becomes configuration.
2. A ledger per currency. Rand, kwacha, metical, pula and the Zimbabwean currencies each get their own balance, and every conversion records its rate, its source and its time.
3. Reconciliation per rail. Each bank, aggregator and operator report is matched line by line every day, so a missing payout is found by you before the recipient calls.
4. A compliance map per country. Who regulates, which licence or partner you need, and which exchange control documents each payment requires.
5. Coverage written down. For every country and direction, which rail you use today, and which you could switch to.

Treasury across these currencies is covered in FX, settlement and treasury for multi-country African apps. The country pillars go deeper, from Zimbabwe, Zambia, Malawi and Mozambique to Botswana, Namibia, Eswatini and Lesotho and Angola.

When you want a regional payment stack built this way, with every rail reconciled, Mctaba Labs payment integration builds payment integrations across Southern Africa.