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.