PAPSS vs. Traditional Settlement: A Clear-Eyed Guide for Banks That Need to Use Both

The Pan-African Payment and Settlement System launched commercially in early 2022 with considerable fanfare. Afreximbank and AfCFTA positioned it as the infrastructure that would finally close the intra-African payments gap — enabling local-currency settlement between African nations without routing through New York or London, reducing costs, compressing timelines, and supporting the monetary sovereignty of member-state central banks.

Three-plus years in, the honest assessment is more nuanced than the launch narrative. PAPSS is a genuine and important development in African payments infrastructure. It is also not yet operating at the scale its architects envisioned, not yet live across all intended markets, and not a replacement for traditional settlement infrastructure in any of the use cases where traditional rails remain superior.

This matters for treasury teams, compliance officers, and business development heads at banks and fintechs, because the strategic question is rarely “PAPSS or SWIFT.” It is: which corridors and transaction types does PAPSS actually serve well today, where does traditional infrastructure remain essential, and what does the technology layer look like that allows you to use both intelligently?

What PAPSS Actually Does — and What It Doesn’t

The Core Mechanics

PAPSS performs three functions: payment processing (routing transactions between participating commercial banks in near real time), clearing (netting obligations between banks to reduce gross liquidity requirements), and settlement (final discharge of obligations through central bank accounts, with Afreximbank providing settlement guarantees).

The structural advantage over traditional correspondent banking is significant in principle. A payment from Nigeria to Kenya through conventional channels typically routes through a USD correspondent account, incurring an FX conversion at each end. PAPSS routes it directly between the two central banks’ accounts at Afreximbank, keeping the transaction in Naira and Shillings throughout and eliminating that intermediate dollar conversion. Afreximbank’s cost estimates suggest this can reduce transaction costs by 20–40% on qualifying intra-African corridors. Settlement finality happens through central bank accounts, which means PAPSS transactions carry a level of settlement certainty that is important for institutional participants. This is not a fintech workaround — it is genuine central bank-backed infrastructure.

The Real-World Adoption Gap

Here is what the promotional material tends to understate: PAPSS is only as useful as the corridors where it is actively live and where central bank participation is fully operational. As of mid-2026, PAPSS has been launched across a growing number of African markets, but the depth of integration varies considerably between countries. Some central banks have full operational connectivity; others have announced participation but have not yet reached the stage where commercial banks can route live transactions reliably.

For a treasury team evaluating PAPSS for a specific corridor, the relevant question is not whether PAPSS exists, but whether PAPSS is reliably operational for that specific pair of countries at commercial volumes. The answer varies, and it requires verification with your settlement provider or directly with PAPSS rather than relying on the official participant list. Building multilateral central bank infrastructure across 55 member states is genuinely complex, and the progress since 2022 is real. PAPSS is the right infrastructure for intra-African local-currency settlement. The question is which corridors are operationally ready today — and that answer requires corridor-level due diligence, not a general readiness assumption.

Where Traditional Settlement Infrastructure Remains Essential

SWIFT and correspondent banking have been the backbone of international payments for over five decades, and that longevity reflects genuine capability. SWIFT connects more than 11,000 financial institutions across 200+ countries. No regional system matches that footprint, and none is designed to. SWIFT gpi has significantly improved settlement speed and tracking transparency on major corridors — same-day settlement with end-to-end tracking is now standard on most high-volume routes.

For transactions that must settle in USD, EUR, or GBP — commodity payments, international trade finance, large corporate treasury sweeps — correspondent banking provides deep, reliable liquidity through established nostro/vostro structures that PAPSS is not designed to replicate. The legal and compliance frameworks are mature, well-understood by counterparties globally, and deeply embedded in trade finance instruments like letters of credit and documentary collections. The nuance worth noting: traditional rails are not standing still. The narrative that PAPSS disrupts a static correspondent banking system misses the ongoing investment banks and SWIFT have made in improving speed, transparency, and cost on their own infrastructure.

The FX Liquidity Dimension

One area where traditional correspondent banking retains a structural advantage is FX liquidity management for major currency pairs. A bank maintaining USD nostro accounts at money-centre banks in New York has access to deep intraday credit facilities, overnight sweeps, and FX swap programs that allow precise management of hard-currency positions at scale.

PAPSS changes the liquidity calculus for intra-African corridors specifically: because transactions net multilaterally before central bank settlement, the gross prefunding requirement falls significantly compared to bilateral correspondent accounts. A bank that previously needed to pre-fund a USD nostro to cover Kenyan-shilling payments into Zambia can now settle those flows through PAPSS with a smaller local-currency buffer. CFOs modelling the capital efficiency case for PAPSS onboarding should include this liquidity saving in the analysis — it is often the most compelling near-term financial argument for participation. But for non-African currency FX management, for exotic currency pairs, and for the hedging instruments that large corporate treasury teams depend on, traditional rails and the banking relationships they underpin remain the relevant infrastructure.

The Routing Decision: A Practical Framework

Experienced payments strategists do not approach this as a binary choice. They approach it as a routing decision — made at the corridor, currency, and transaction-type level, and ideally automated through intelligent payment infrastructure. The table below reflects how that decision plays out across common scenarios:

A critical note on the table above: the “PAPSS” recommendations should be read as “PAPSS where the corridor is operationally live.” Before deploying PAPSS for any production payment flow, verify current central bank participation status for your specific origin-destination pair. The PAPSS participant list is a starting point, not a guarantee of operational readiness.

The Technology Layer: Why the API Question Matters More Than the Rail Question

For most banks and fintechs, the more important strategic question is not “which rail” but “what technology layer allows us to use multiple rails intelligently.” This is where the Global Payouts API architecture becomes the central discussion.

A well-designed payouts API abstracts the complexity of the underlying settlement networks. A bank can expose a single, consistent interface to its corporate clients while the platform routes each payment to the optimal rail — PAPSS for an intra-African naira-to-cedi transaction, SWIFT for a USD supplier payment to Germany, a local RTGS for a domestic settlement. From the client’s perspective, it is one payment instruction. The routing intelligence lives in the platform.

The strategic benefits of this architecture are significant: corporate clients get a unified international payment solution without needing to understand the underlying network topology; the routing engine selects the lowest-cost, fastest path in real time; compliance screening is applied consistently regardless of rail; and adding a new corridor — say, a newly live PAPSS market in Francophone West Africa — requires no client-side re-engineering. For banks evaluating whether to build or buy this capability, the build-versus-partner question deserves honest analysis. Building a genuine multi-rail payouts API with intelligent routing, real-time FX management, and consistent compliance across PAPSS, SWIFT, and domestic RTGS systems is a multi-year technology investment. Partnering with a provider that has already built it compresses that timeline from 12–18 months to 3–6 months of integration work. The trade-off is control and margin; the benefit is speed and reduced technical risk. The banks winning on cross-border payments in Africa are not the ones with the most direct rail connections. They are the ones with the technology layer that makes routing decisions invisible to the client.

Treasury and Liquidity Management: The Operational Implications

Modelling the PAPSS Capital Efficiency Case

For treasury and finance teams at banks evaluating PAPSS participation, the capital efficiency case is worth modelling carefully. Under traditional correspondent banking for intra-African corridors, banks typically pre-fund USD nostro accounts to cover expected payment volumes — capital that earns little while sitting idle and is exposed to USD liquidity risk.

PAPSS’s multilateral netting model changes this. Because obligations net across all participating banks before final central bank settlement, the gross prefunding requirement falls. The exact saving depends on your payment flow patterns — specifically, whether your inbound and outbound flows in a given currency corridor are reasonably balanced. Banks with naturally offsetting flows will see the largest liquidity benefit; those with heavily one-sided flows will see less. The modelling exercise is straightforward: take your current intra-African corridor payment volumes, estimate the prefunding requirement under PAPSS versus your current nostro structure, and compare the freed-up capital against PAPSS onboarding costs and ongoing participation fees. In most cases where the corridor volumes are meaningful, the payback period is 12–18 months. For banks already constrained on USD correspondent lines, the case is often stronger.

Real-Time Position Management Across Both Rails

One operational complexity that deserves attention: running both PAPSS and traditional rails simultaneously requires treasury systems capable of providing real-time visibility across both. An institution that has excellent nostro position management for SWIFT flows but manages its PAPSS prefunding position manually is creating a gap that will cause problems at volume. The investment in consolidated treasury dashboards — surfacing open positions, pending settlements, and FX exposures across all active rails in real time — is not optional infrastructure for a bank running a hybrid payment stack. It is the operational foundation that makes the hybrid model sustainable.

Strategic Implications for Banks Operating Across Regions

For institutions operating across multiple geographies — pan-African banks, MENA institutions expanding into Africa, European banks serving African corporates — the PAPSS question sits within a broader strategic context.

Gulf Cooperation Council banks are particularly well-positioned to benefit from PAPSS connectivity. The GCC countries are significant trade and investment partners for Africa, and the bilateral payment corridors — Nigerian businesses importing from the UAE, Kenyan companies settling with Saudi suppliers — carry significant volume. Connecting to PAPSS, either directly or through a technology partner, opens African businesses to a regional bank’s client base in a way that pure SWIFT connectivity does not.

European and Asian banks serving African corporates or operating African subsidiaries face a client-retention question. As African businesses gain access to faster, cheaper intra-African payment options through PAPSS-connected providers, they will naturally gravitate toward banking partners that can offer those options. A European bank that serves a pan-African corporate but cannot offer PAPSS settlement for intra-African flows is offering an inferior product for a growing portion of that client’s transaction volume. The competitive dynamic is not yet acute — PAPSS adoption is still early enough that most corporate clients are not yet demanding it. But the direction of travel is clear, and the institutions building PAPSS connectivity now will have a capability advantage when client demand firms up over the next two to three years.

PAPSS Onboarding: What the Journey Actually Involves

For banks evaluating PAPSS participation, the implementation journey is manageable but requires honest scoping. The key dimensions are central bank approval (participants must be licensed and approved by their home-country central bank, which manages final settlement obligations on their behalf — timeline varies significantly by jurisdiction), technical integration (PAPSS provides a gateway; institutions with existing ISO 20022 capabilities typically find the integration lift manageable, though testing and certification take time), compliance mapping (AML, KYC, and sanctions-screening workflows need to be extended to PAPSS-routed transactions, which is largely configuration rather than re-architecture), and liquidity strategy (determining the optimal prefunding level for expected PAPSS volumes and building the monitoring infrastructure to manage it in real time).

One dimension that is often underestimated is client education and go-to-market. Corporate and SME clients may be unfamiliar with PAPSS, and the cost and speed benefits are not self-evident without a clear explanation. Banks that have driven strong PAPSS adoption among their client base have typically invested in targeted communication campaigns — explaining the specific corridors where PAPSS is available, the expected improvement in settlement times, and the cost difference relative to traditional rails. The partnership route — integrating through a provider that already has PAPSS connectivity — is worth serious consideration. It can reduce a 12–18 month build to a 3–6 month integration, at the cost of some margin and control.

The Practical Bottom Line

PAPSS and traditional settlement infrastructure are not in competition. They serve different use cases, and the institutions that will operate most effectively in African payments over the next decade are those that have invested in the technology layer to deploy both — intelligently, at the transaction level, based on corridor, currency, and client need.

The strategic priorities that follow from this are concrete:

• Conduct corridor-level due diligence on PAPSS operational readiness for your highest-volume intra-African routes — do not assume that AfCFTA membership translates to live PAPSS connectivity.
• Model the capital efficiency case for PAPSS participation using your actual payment flow data, including the liquidity saving from multilateral netting.
• Evaluate the build-versus-partner question for your payouts API layer honestly, with realistic timelines for an internal build.
• Invest in the treasury visibility infrastructure that allows you to manage positions across both rails in real time. Running a hybrid payment stack without consolidated position management is operationally unsustainable at any meaningful volume.

PAPSS is genuinely important for African payments. So is SWIFT. The banks that treat this as a binary choice will be outcompeted by those that treat it as a routing problem — and build the infrastructure to solve it well.