What we're seeing.

Observations on cross-border finance in Africa — from people who are actually building in this space.

Why SWIFT doesn't work for the Nigeria–South Africa corridor — and what does.

SWIFT was designed in the 1970s for international bank-to-bank settlement. It processes around 45 million messages a day. It has correspondent bank fees, FX conversion markups, and settlement windows measured in days. For two African economies trying to connect businesses and families, it is the wrong tool entirely.

Local payment rails — NIP in Nigeria, RTGS and EFT in South Africa — already settle transfers in seconds within each country. LiquidPay's approach is to treat each country's banking system as a local endpoint. The NGN enters on one side. The ZAR exits on the other. No international wire crosses the ocean.

This isn't a workaround. It's a structural redesign of how the corridor operates. And it's why transfers settle in under 60 seconds rather than 3–5 business days.

More perspectives in the pipeline.

We publish infrequently and deliberately. Only when we have something worth saying.

📊
Coming Soon
Understanding the NGN–ZAR Spread
Why exchange rate spreads matter more than fees — and how to read the real cost of your transfer.
🏛️
Coming Soon
CBN, SARB, and the Compliance Reality
What it actually means to operate compliantly in both Nigeria and South Africa at the same time.
🤝
Coming Soon
The Business Case for Cross-Border APIs
How growing companies are replacing FX desks with programmable payment rails between Lagos and Johannesburg.
💳
Coming Soon
What Nigerians in South Africa Actually Need
Research and observations from the people at the center of this corridor — the diaspora community that moves money daily.