By Bonaventure Ogeto · Published · Last verified: 2026-11-04
PAPSS in Southern Africa: where it works today
The short answer
PAPSS's June 2026 coverage sheet lists South Africa, Zambia, Malawi and Zimbabwe among the countries its network reaches, with South Africa marked as requiring additional integration where applicable[PAPSS, checked 2026-11-05]. A listing is not a working corridor: ask your bank, and the bank at the other end, whether they can send and receive a PAPSS payment for yours, in writing.
Source: Mctaba Labs, “PAPSS in Southern Africa: where it works today”, last verified 2026-11-04, mctaba.com/learn/payments/cross-border/papss-southern-africa
Mctaba Labs builds payment integrations for businesses across Africa. This guide is written to be useful whether or not you ever hire us.
Where does PAPSS work in Southern Africa today?
PAPSS is the Pan-African Payment and Settlement System, and it publishes its own answer to this question. Its June 2026 network coverage sheet lists South Africa, Zambia, Malawi and Zimbabwe among the countries its network reaches, with South Africa marked as requiring additional integration where applicable[PAPSS, checked 2026-11-05]. For builders in this region, those four are the names to check against your corridors.
Read the sheet for what it is: a map of reach, not a promise about your payment. The sheet sorts countries under two headings, countries with live participants and countries its reach extends across[PAPSS, checked 2026-11-05], and the copy we read does not let us say which heading each Southern African country sits under. Either way, a country on the sheet tells you that PAPSS can reach some institution there. It does not tell you whether your bank can send, whether your supplier's bank can receive, or in which currency and at what price.
So the advice is the same as before the sheet, only sharper: ask your bank, and the bank at the other end, whether they can send and receive a PAPSS payment for your corridor, and get the answer in writing. This page sets out how to do that, what PAPSS would change in your integration, and which routes you can verify and build on today. For the wider map of regional rails, see cross-border payments in Southern Africa.
What does the note next to South Africa mean for you?
That a South African sender should expect work before the first payment. PAPSS marks South Africa as requiring additional integration where applicable[PAPSS, checked 2026-11-05], and the sheet does not say what that integration is or who must do it. Read it as a warning, not a schedule.
In practice the question goes to your bank: does it participate, for which corridors and currencies, through which product, and from when? If the answer is "not yet", nothing in your code changes. If it is "yes", you still need the receiving bank's confirmation and a small test payment before customers depend on it.
How do you check whether a PAPSS payment will work for you?
Treat it like any rail you have not used before: confirm it end to end before a customer depends on it.
- Ask your bank whether it can send PAPSS payments, to which countries and banks, in which currencies, and under which product. Ask for the answer in writing.
- Ask the receiving side the same question. A payment rail only works when both ends are connected, so your supplier's or recipient's bank must confirm too.
- Read PAPSS's own coverage sheet, not a summary of it, and note its date: the copy we checked is the June 2026 sheet[PAPSS, checked 2026-11-05]. Third-party lists, including bank FAQs and news articles, can lag behind changes.
- Ask for the full price: the fee at each end, the exchange rate used and any intermediary charge. Compare it with the route you use today.
- Send a small real payment and time it, from instruction to the money being usable at the other end.
- Ask how you will see what happened: which statuses and return reasons you will receive, and in what report.
The questions to put to the bank fit in one short table:
| Question for your bank | Why it matters |
|---|---|
| Can you send this corridor over PAPSS, and through which product? | It decides whether there is anything to integrate at all |
| Is the receiving bank connected? | A payment rail needs both ends |
| Which currency is debited and which is credited? | Conversion is where cross-border cost hides |
| What does it cost, end to end? | Only the total can be compared with today's route |
| How long until the money is usable? | Your customer promises depend on it |
| Which statuses and return reasons come back? | Your reconciliation has to map every one |
What would PAPSS change in your integration?
Probably less than you expect. Settlement systems sit behind banks and payment providers: your code calls a bank or a provider, and that institution chooses the rail. If your bank starts carrying a corridor over PAPSS, expect the change to reach you through the bank's own channel: a new product, new pricing, new statuses or new timing.
That has two practical consequences:
- Do not make PAPSS a dependency in your product plan until your bank offers it for your corridor, in writing. Build on what is confirmed and treat PAPSS as an option your bank may add.
- Keep your payout layer rail-agnostic. If every payout records which route carried it, with that route's reference and statuses, a new rail is a configuration change. The same pattern is laid out for the South African TCIB change in the TCIB deadline and how to migrate payouts.
If you want a second pair of eyes on a cross-border payment design, Mctaba Labs payment integration reviews it as part of scoping a build.
Can you use PAPSS for payments to Zambia?
Zambia is on PAPSS's sheet, so the question is whether your bank and your recipient's bank can use it for your corridor. Until both confirm, Zambia has routes you can verify and build on:
- Mobile money through an aggregator. pawaPay covers Airtel, MTN and Zamtel in Zambia[pawaPay markets page, checked 2026-11-04], so one integration reaches all three networks. The build is in the pawaPay integration tutorial.
- MTN directly. MTN's MoMo Developer Portal has a go-live page with the steps to apply for production[MoMo Developer Portal go-live page, checked 2026-11-05].
- Bank payments to suppliers, through your bank's foreign payments channel and with the documents it asks for: under the SARB's Currency and Exchanges Manual, Authorised Dealers may only make foreign currency payments for imports against specified documentation[SARB, checked 2026-11-05].
The Bank of Zambia regulates payment systems[Bank of Zambia, checked 2026-11-04], and the country's own rails are covered in payments in Zambia for builders.
Can you use PAPSS for payments to Zimbabwe?
Zimbabwe is listed too, and the same rule applies: your bank's written confirmation, not the listing. The routes you can verify today depend on whether you are collecting or paying:
- Collecting from Zimbabwean customers. Paynow's express checkout supports EcoCash, OneMoney, InnBucks and O'mari wallets as well as Visa/Mastercard and ZimSwitch cards[Paynow developer docs, checked 2026-11-04], and 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].
- Sending money from South Africa to a person. Mama Money charges a fee of 5% or less to send money to an EcoCash wallet in Zimbabwe[Mama Money, checked 2026-11-04]; the full comparison of routes is in sending money from South Africa to Zimbabwe.
- Paying a supplier. Your bank's foreign payments channel, with the documents it asks for.
The country's rails, from ZimSwitch to the ZiG, are mapped in payments in Zimbabwe for builders.
Can you use PAPSS for payments to Malawi?
Malawi is on the sheet as well, so ask both banks. It is the corridor where checking every option pays most, because the cost of getting money there from South Africa is high. A paper on the SARB's site, using World Bank data, found an average cost of 19.4% to send $200 from South Africa to Malawi[SARB-hosted paper, checked 2026-11-05] and 17.2% to send $500[SARB-hosted paper, checked 2026-11-05], against a sub-Saharan average of 8.78% for $200 and a 6.49% global average in Q1 2025[SARB-hosted paper, checked 2026-11-04].
Routes you can verify for Malawi today:
- Mobile money through an aggregator. pawaPay covers Airtel and TNM in Malawi[pawaPay markets page, checked 2026-11-04], so the aggregator you use for Zambia may cover Malawi too.
- Bank payments to suppliers through your bank's foreign payments channel.
The Reserve Bank of Malawi's payment systems page lists the Payment Systems Act (No. 15 of 2016)[Reserve Bank of Malawi, checked 2026-11-05]; the country guide is payments in Malawi for builders, and the cost data is examined in remittance costs in Southern Africa.
How does PAPSS relate to TCIB and SADC-RTGS?
They overlap in places, and only one of them has a deadline you can cite. Inside the Common Monetary Area, regulation decides the route: settlement system participants must stop routing smaller cross-border EFTs within the CMA through SADC-RTGS by 31 March 2027 and execute them through the TCIB payment scheme from 1 April 2027[Government Gazette, checked 2026-11-05], where smaller means an EFT not exceeding R5 million[SARB, checked 2026-11-04]. Zambia, Zimbabwe and Malawi sit outside the CMA, so that directive does not set their route; your bank does.
Two of those countries appear on both maps. PayInc's 2025 report says TCIB is operational in South Africa, Namibia, Lesotho, Eswatini, Zambia and Zimbabwe[PayInc Business Report 2025, checked 2026-11-05], so for Zambia and Zimbabwe your bank may have two regional options, or neither. Ask which one would carry your payment, and why.
Whether PAPSS and TCIB will connect, and when, is not something we could confirm from either system's own pages. Plan on today's routes and treat any future link as a bonus. The regional settlement picture is in SADC-RTGS and the Common Monetary Area and TCIB explained for developers.
Should you design around PAPSS now?
Not as a dependency. Design around routes you can confirm, and leave room for PAPSS to arrive through your bank. In practice:
- Choose today's route per corridor from what you can verify: an aggregator for mobile money, your bank's foreign payments channel for supplier payments, a remittance partner for payments to people.
- Record the rail, its reference and its statuses on every payment, so adding a rail later is configuration.
- Ask your bank about PAPSS at every review, starting with the four Southern African countries on the sheet, and test it with a small payment the day it is offered.
For the full regional picture, see payments in Southern Africa. When you want a cross-border payment flow built so a new rail is a switch rather than a rewrite, Mctaba Labs payment integration does that work.
Frequently asked questions
- Can a South African business send a payment over PAPSS?
- Only through a bank that offers it. PAPSS's June 2026 coverage sheet lists South Africa but marks it as requiring additional integration where applicable[PAPSS, checked 2026-11-05], so ask your bank whether it can send PAPSS payments for your corridor and get the answer in writing.
- Does PAPSS cover Zambia, Zimbabwe or Malawi?
- PAPSS's June 2026 coverage sheet lists Zambia, Malawi and Zimbabwe among the countries its network reaches[PAPSS, checked 2026-11-05]. A listing does not tell you whether your supplier's bank is connected, so confirm with the banks at both ends before you rely on it.
- Can developers integrate with PAPSS directly?
- This page does not point to a PAPSS developer API because we have not verified one. Plan on reaching any settlement system through a bank or payment provider, which chooses the rail for you.
- Is PAPSS connected to TCIB?
- We could not confirm a live connection from either system's own pages, so do not plan around one. Inside the Common Monetary Area the route is set by regulation: smaller cross-border EFTs within the CMA go through the TCIB payment scheme from 1 April 2027[Government Gazette, checked 2026-11-05], where smaller means not exceeding R5 million[SARB, checked 2026-11-04].
- Why does the route to Malawi matter so much?
- Because the cost can be high: a SARB-hosted paper puts the average cost of sending $200 from South Africa to Malawi at 19.4%[SARB-hosted paper, checked 2026-11-05], so every route your bank offers is worth comparing.
Need this integration built?
Mctaba Labs builds payment integrations across South Africa and the region: PayShap, pay by bank, card gateways, mobile money and cross-border payouts, with the webhooks and reconciliation that keep the money matching the books.
Talk to the payments team