Eswatini’s payment switch, sandbox, and open banking — and why Namibia is building the same stack

Across Southern Africa, supervisors are pursuing a consistent sequencing: modernise national payment infrastructure first (or in parallel with clear governance), add structured innovation pathways such as regulatory sandboxes, then deepen data and payment initiation access through open finance / API programmes aligned to national standards.

This note compares publicly described initiatives in Eswatini with Namibia’s direction of travel—without pretending timelines are static. Always confirm dates, limits, and participation rules on official central bank and regulator websites.

Eswatini: EPS, the regulatory sandbox, and open banking as a roadmap

National payment systems and fast payments

The Central Bank of Eswatini (CBE) publishes its payment-systems framework—including National Payment Systems Act materials, Fast Payments directives, and interpretation notes—under National Payment Systems – CBE. That page is the anchor for legal and oversight context around retail payments modernisation.

Industry reporting and vendor announcements describe the Eswatini Payment Switch (EPS) platform going live as a national, interoperable switch intended to connect banks and payment-service providers; one public write-up of the go-live is available from the platform partner PayLogic — national interoperable payment switch goes live (use alongside CBE primary sources).

What senior officials said about sequencing

At the EPS Fast Payments product launch, CBE Governor Phil Mnisi outlined expectations for phased rollout, participant onboarding, and transaction limits—material that supervisors and banks typically treat as programme context for pricing, limits, and adoption planning. The Bank for International Settlements published the remarks as BIS Review — EPS Fast Payments product launch (with PDF).

Governor-level speeches are not substitutes for directives—but they help innovators understand intent: interoperable instant payments as the spine for wider digital commerce.

Supervised innovation: CBE FinTech sandbox

For controlled live testing with safeguards, the CBE operates a dedicated intake path described at CBE FinTech Sandbox, alongside institutional context on Financial Technology – CBE.

Open banking as the next layer—not a standalone slogan

Public commentary from CBE leadership (reported in regional press) describes expanding digital payments and working toward open banking–style access to support wallets, merchants, and government flows—consistent with treating API-led access as a phase that sits atop national rails once interoperability and governance are credible.

Independent trackers may still show limited public developer portals for retail APIs—normal when standards and liability models are still converging. The policy signal matters for roadmaps: switch first (or in tight parallel), APIs next, under national law.

Namibia: instant payments, open banking standards, and supervised testing

Instant Payment System (IPS)

The Bank of Namibia has communicated an Instant Payment System programme intended to deliver near-real-time, interoperable low-value payments across banks and, over time, wallets—modelled on proven national instant-payment architectures and executed with specialised delivery partners. Programme milestones have shifted in public reporting; treat launch windows as indicative until confirmed in BoN media releases.

A formal programme kick-off communication remains a useful primary citation anchor:

• Instant Payment Project kick-off — Bank of Namibia

Follow News & Media — Bank of Namibia for updates rather than third-party headlines alone.

Open banking + NAMQR as national standards—not a single vendor feature

Namibia’s policy framing (as reflected in LANCR’s supervisory alignment model) treats open banking and NAMQR as national rails and standards supervised by the Bank of Namibia—covering consent, security, data minimisation, and operational resilience. Product teams should assume certification against evolving specifications, not a one-off integration to a proprietary “portal.”

That is structurally similar to Eswatini’s story: instant, interoperable settlement plumbing, then structured API access with audit trails.

Where LANCR fits

LANCR’s Digital Sandbox is not a replacement for BoN licencing or NAMFISA pathways where applicable. It is where participants rehearse journeys—consent UX, technical conformance packs, monitoring hooks—before wider production exposure. If your roadmap assumes IPS volumes, QR-led initiation, or account-information services, your sandbox test plan should name which national artefacts you map to at each phase.

Shared lessons for product and compliance leaders

1. Rail before ribbon. Instant payment switches create the interoperability assumptions that open-finance APIs rely on.
2. Publish once, cite primary. Prefer CBE, BoN, BIS-hosted speeches, and regulator portals over recycled slides.
3. Sandbox is for evidence. Use cohort testing to generate controls evidence—limits, fraud monitoring, dispute paths—not just feature demos.
4. Cross-border later. Regional convergence (for example G20 payments targets and industry papers on sandboxes) matters after domestic interoperability is credible—see our cross-border sandboxes note.

---

Disclaimer: This article summarises publicly available materials for educational context. It is not legal or regulatory advice. Programmes, limits, and eligibility change—verify on centralbank.org.sz and bon.org.na before making business decisions.