Preparation Checklist for Zambian PSPs Joining the National Financial Switch

Content authorBy EGSPublished onReading time12 min read
An IT analyst monitors network activity at a multi-screen workstation in a modern operations center, illuminated by cool blue light.

Joining the National Financial Switch (NFS) takes Bank of Zambia (BoZ) designation plus admission and certification by Zambia Electronic Clearing House Limited (ZECHL), with a settlement arrangement either directly with BoZ or through a sponsoring bank. Engineering work only becomes meaningful once scope and settlement responsibility are fixed in writing along with the rules and fees.

What must be agreed before integration?

Fix the service scope and the participation route before a single endpoint is built. Do the same for the settlement model and the governing rules, and for the fee schedule and named accountable parties. Architecture decisions inherit from those agreements, and a launch date committed before them is a guess dressed as a plan.

Scope means naming the exact transaction types you intend to run, with the channels behind them and the direction of flow. Settlement model determines whether your treasury or someone else's carries the obligation. Rules determine your liability when a transaction fails halfway.

The volume you're joining is substantial. The Bank of Zambia reported that NFS transaction value rose 36.5 percent to K180.1 billion in 2025, up from K131.9 billion the year before.

Growth at that rate changes what "ready" means for you. A platform sized against last year's industry volumes will meet certification and then struggle in its second quarter of production, which is why capacity assumptions belong in the scope conversation.

Which approvals remain external decisions?

Neither you nor your engineering partner approves anything. BoZ decides designation under the National Payment Systems Act, and ZECHL decides admission to the scheme. Build the plan around that reality instead of around a target go-live.

Designation applications go to the Deputy Governor at BoZ and must carry prescribed documentation. Under the February 2025 designation requirements, the certificate is issued only after the applicant meets the requirements and pays the annual designation fee, and it authorizes activity at specified places of business.

Because the certificate is scoped to authorized activity, any service you add later than your application sits outside it. Write your designation scope wide enough to cover the twelve months after launch, then treat every addition beyond it as a fresh regulatory conversation.

What participation documents are required?

ZECHL participation needs a completed application and signed acceptance of the applicable scheme rules. Infrastructure certification and fee commitments belong with a declared service scope. Confirm the current forms and rule versions with ZECHL directly, along with fee schedules and interface specifications, because published versions age.

The fee structure has three components. Revenue for the switch comes from a one-time application fee and annual participation fees, with a per-transaction fee charged to participants, according to the AfricaNenda SIIPS 2023 country case study on Zambia.

A per-transaction component means your pricing model and your participation cost move together, so the unit economics you present to your board should be modeled at the volumes you expect in year two. Scheme rule acceptance also binds you to amendments agreed later, which is a governance commitment as much as a legal one.

Who carries settlement responsibility?

Someone must stand behind your net position daily, and the scheme requires proof of who that is. Participants hold either a settlement account with the Bank of Zambia or documented sponsorship by a settlement bank.

Non-bank participation runs through sponsorship, and the evidence pack is specific. The scheme rules require participants to either hold a settlement account with BoZ or provide proof of a settlement sponsorship arrangement with a settlement bank.

What to assemble before you approach ZECHL:

  • A signed sponsorship agreement naming the settlement bank, the account, and the mandate holders

  • Written liquidity responsibilities, including who funds a shortfall and within what window

  • Named reconciliation contacts on both sides, plus a documented escalation path with response times

Sponsorship is a credit decision made by your bank, not a technical step, and banks price it against your operational maturity. That's why arranging sponsorship early tightens your reconciliation design, since the bank asks the same questions a reviewer would.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

How does one transfer prove readiness?

Infographic showing transaction auditing steps in a minimalist financial workspace with rounded cards, arrows, and flat vector icons.

One transfer traced end to end exposes dependencies that passing individual application programming interface (API) calls never reveals. Follow the money from message construction through to settlement evidence, and the gaps surface on their own.

Isolated API completion tests your code. A traced transfer tests the agreements behind your code: whether your identifiers survive the round trip and whether your finance team can prove the money moved.

Scale gives the exercise weight. BoZ recorded that NFS participant use cases in production grew to 160 at end-2024 from 134 a year earlier, with 29 participants live on e-money.

Each of those use cases was certified separately. So readiness is a property of each service you declare, which argues for launching a narrow first transaction type and widening once your reconciliation holds under real volume.

How does ZECHL switch the transfer?

The switch validates your message and routes it to the beneficiary institution. It relays the response back on the same path. Your job is to submit a standards-compliant message and preserve every identifier the switch hands back.

All participant interfaces and messages on the NFS are built on the ISO 8583:1993 standard, per ZECHL. Field-level discipline matters, since the retrieval reference and the trace number are what let you match a dispute six weeks later to a log line. This is the same core concern addressed by payment switch engineering.

Keep your own record of the request timestamp and the response timestamp, along with the response code and any reversal raised. Record the operator or system that initiated it. Audit records built after a dispute arrives are never as complete as records written during the transaction, and the scheme's dispute process assumes you have the latter.

How does the beneficiary process funds?

The receiving institution validates the beneficiary and posts to the account or wallet. It returns a response the acquirer can act on. Everything hard about this sits in the failure paths.

The ISO 8583 flow analyzed by David Chanda and Simon Tembo of the University of Zambia shows why. Where a failure occurs after authorization, the acquirer sends a 1400 reversal and the issuer reverses the uncleared credit, with funds still available because the receiver never had access to them.

That design only protects you if your posting logic keeps credits uncleared until the response round trip completes. Build duplicate prevention on the original trace identifier, because a retried message carries that identifier and a fresh one carries your internal request ID, and confusing the two is how double credits reach customers.

What proves reporting and settlement?

Proof is a chain: your transaction records match ZECHL's net settlement report and your reconciliation closes against it. Your settlement bank evidences the funds movement. Any broken link means you cannot declare readiness honestly.

ZECHL calculates net settlement positions and transmits settlement instructions to BoZ, which acts as settlement agent, with settlement taking place once daily at 16:30 through the Zambia Interbank Payment and Settlement System (ZIPSS).

A single daily cycle means intraday exposure is carried by participants between cut-off and settlement. Your treasury needs an intraday liquidity view of the growing net position, not a next-day report, because by the time a reconciliation break appears in yesterday's file the liquidity decision it should have informed has already passed. Assign finance sign-off to a named person with a deadline, and define what an unresolved exception blocks.

What belongs in the readiness matrix?

A readiness matrix lists every dependency with eight columns, among them the internal owner and the acceptance condition. Anything without an owner and an acceptance condition is hoped for.

The matrix exists because three organizations control your timeline. BoZ's 2024 figures showed NFS participants spread across production, pilot and user acceptance testing stages simultaneously. Five participants were in e-money pilot and three in UAT at year end.

That spread tells you something useful: participants sit in pre-production states for meaningful periods, and the ones that move fastest are the ones whose blockers are visible to all three parties at once. Share the matrix with ZECHL and your settlement bank, since a blocker nobody outside your building can see is a blocker nobody outside your building will clear.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

What must the PSP provide?

You supply everything about your own platform that another party must verify. That covers intended services and projected volumes, along with platform architecture and security controls. Message mappings sit with endpoints and certificates, as do the settlement model and reconciliation rules. Support contacts and business continuity procedures belong there too.

Security evidence carries disproportionate weight. The NFS scheme rules require participants to adhere to the Payment Card Industry Data Security Standards and to maintain mandated data security standards covering e-wallet and account data.

Treat your mappings document as the contract between your product team and your engineers. Most certification delays I've seen in switch integrations trace back to a field that two teams defined differently, and a written mapping signed by both sides removes that category of problem before testing begins.

What must ZECHL confirm?

ZECHL confirms participation status and the current interface specifications. It also confirms connectivity arrangements and certification steps, plus test environment access and cut-off times. Report formats and dispute processes sit with the conditions for entering production. Get each in writing with a version number.

Service levels are defined formally. The NFS rules commit ZECHL to maintaining a Master Service Level Agreement covering availability and response, along with load and accuracy. Batch service and measurement fall under it as well, as does technical assistance, alongside an automated Dispute Management System for notifying disputed transactions.

Since disputes run through a defined system, your operations team needs trained access to it before launch. Ask ZECHL for the dispute notification timelines in writing and build them into your support rota, because a deadline you discover during an incident is a deadline you'll miss.

What must the settlement institution confirm?

Your settlement bank confirms sponsorship terms and account setup, along with mandates and funding arrangements. It also confirms the settlement reporting format and who owns exceptions, plus what it accepts as proof that settlement completed. Vague answers here become disputes later.

Bank obligations around customer funds are set by regulation. The Directives on Electronic Money Issuance, 2023 govern e-money issuers' operations in Zambia and the handling of customer funds held with regulated institutions.

Ask the bank one question most applicants skip: what document will you issue that my auditor will accept as evidence settlement occurred? If the answer is a statement line with no reference to the NFS net position, your reconciliation has a gap you'll only find at year-end audit, and closing it then costs considerably more than specifying the report format now.

Which tests establish launch readiness?

Launch readiness is established by a named test set with objective exit criteria, each with an owner and a pass threshold agreed in advance. Connectivity and functional tests come first, along with negative path and timeout tests. Reversal and duplicate handling tests sit with reconciliation and settlement tests. Performance and security tests follow, as do failover and operational acceptance.

The regulator watches specific numbers after you go live. Godwin Sichone of the Bank of Zambia listed transaction approval rates and processing times among the quality of service metrics BoZ monitors when he presented to the International Telecommunication Union (ITU) in May 2026, with an industry required approval rate benchmark.

Set your test exit criteria to those same metrics. If BoZ measures approval rate and processing time in production, a test suite that passes on functionality but never measures either leaves you blind to the one dimension your supervisor will raise first.

What support must exist after launch?

Production support needs monitoring and alerting, along with defined incident severities and escalation paths to both ZECHL and your settlement bank. Reconciliation deadlines and dispute handling sit with change control and capacity management. Disaster recovery and clear ownership of round-the-clock cover belong in the same model. The switch runs continuously, so your support model has to as well.

Dispute timelines are prescribed. Under the ZECHL clearing house rules, participants must first attempt settlement by mutual agreement within seven days of the aggrieved party giving notice, with unresolved matters referred to ZECHL for interpretation and then to the Bankers Association of Zambia.

Seven days sounds generous until you account for weekends and a counterparty whose named contact has left. Keep a current contact register for every participant you transact with and refresh it quarterly. Treat an out-of-date register as an operational risk item.

How can EGS map the engineering work?

EGS can map the engineering half of this checklist: architecture review against the scheme's interface specifications and payment platform integration. Transaction processing design and test planning sit with production support. Approval timelines stay with BoZ and ZECHL, and no engineering partner can shorten them.

The engineering half is not the small half. NFS volumes grew 47.9 percent in 2025 to 207.8 million transactions, and that growth lands on participant platforms as sustained load and support demand.

What that implies for your build is straightforward enough. The design decisions that matter most are the ones governing failure paths and reconciliation, because those are the ones that scale badly when volume doubles and the ones regulators measure.

Discuss your National Financial Switch readiness with EGS and map the engineering work required for launch.

Start building your financial platform?

Speak with EGS engineers about open banking, payment infrastructure, cloud systems, and enterprise software.

Get in Touch →

Contact BoZ before offering the changed service and compare it with the activity stated on your designation certificate. Ask whether the change needs an amended application, new evidence, or another approval. Update ZECHL, your settlement bank, test scope, customer notices, and internal controls before production use.

Use synthetic or masked records instead of live customer data whenever testing does not require production values. Restrict access by role, separate test credentials from production credentials, record administrator activity, and delete temporary files after testing. Document the controls so your certification evidence covers data handling as well as message security.

Complete a disaster recovery rehearsal before production approval, then repeat it after major changes to infrastructure or transaction processing. Test restoration of transaction records, message replay controls, certificates, contact lists, and reconciliation files. Record recovery time, data loss, unresolved defects, and the owner responsible for each correction.

A PSP can seek certification for multiple transaction types, but a narrow first release is easier to test and reconcile. Start with the service whose identifiers, reversals, settlement reports, and support procedures are proven. Add further services only after reviewing production results and confirming that each remains within the approved designation scope.

Track the number and value of transactions that match across your ledger, switch reports, and settlement evidence. Measure unmatched items, duplicate records, missing reversals, investigation age, and the time needed to close each exception. Set pass thresholds before testing, then require finance sign-off on every unresolved item at the exit review.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

A project manager in business casual attire discusses a document intake process with a team in a modern office, focusing on a large monitor.

Bank document intake workflow: A readiness checklist

This article gives you a checkpoint-by-checkpoint method for testing a document intake process before you turn it on. It includes a worksheet structure you can copy into a spreadsheet and the evidence each control needs to produce.

Two business partners collaborate on configuring a POS terminal in a modern office, surrounded by payment devices and colleagues.

EthioPay for Ethiopian Banks: Turn Readiness into a Delivery Plan

This article explains how an Ethiopian bank moves from "we want to participate" to a dated, costed integration plan for the country's domestic card scheme and instant payment rails. It covers service selection and a phased release sequence.

A modern smartphone displaying a mobile banking app lies on a wooden desk, surrounded by abstract payment cards and a notebook.

AfriGO Card Readiness: Plan Your Nigerian Bank’s Rollout

This article is a readiness guide for moving from "we're considering it" to a controlled pilot on Nigeria's domestic card rails. It covers role definition and launch scope, then maps the transaction flow so you can assess systems and assign requirement ownership through the workstream matrix that holds the whole program together.

A professional seated at a desk uses a smartphone and payment card, engaged in online banking in a bright, modern office.

G2P Payments in Africa: Build Reliable Social Payment Infrastructure

This article traces the full lifecycle of a government social payment in Africa, from eligibility approval through to reconciliation and investigation evidence. It assigns operational ownership at each system boundary and sets out how to control exceptions and assisted access.