What the guidelines are
In July 2026 the Reserve Bank of Zimbabwe (RBZ) National Payment Systems Department issued its Guidelines on Digital Financial Services (DFS) Security in Zimbabwe, effective from 17 July 2026. They set minimum technical security requirements for DFS, draw on ITU-T recommendations and complement the RBZ Cybersecurity and Resilience Guideline of August 2025, which remains the overarching framework.
Who they apply to
- All RBZ-licensed institutions offering digital financial services, including banks, microfinance institutions, mobile money operators, fintechs and payment service providers
- DFS intermediaries, including aggregators, DFS agents and third-party service providers that operate within or interface with DFS platforms
- Telecom infrastructure controls such as base stations are excluded, but providers must mitigate known risks like SS7 attacks where they integrate with USSD or SMS
Key requirements at a glance
| Governance | Operate within the enterprise cybersecurity framework, with CISO oversight and a dedicated DFS Security Lead; apply zero-trust principles |
|---|---|
| Risk assessment | Formal DFS threat risk assessments at least annually or on significant change, covering device, application, network, authentication and backend threats |
| Mobile and app security | Detect and block rooted or jailbroken devices; obfuscation, anti-tampering and code signing; SAST/DAST in a DevSecOps pipeline; signed SBOMs; rogue-app monitoring and take-down |
| SIM swap and SS7 | Prefer app or token MFA over SMS OTP for high-risk transactions; real-time SIM-change alerts; 24–48 hour hold windows after SIM change for limit increases or recovery |
| Authentication and sessions | User-defined PINs with retry limits; inactivity timeout of 3–5 minutes by default; device binding |
| Data protection | AES-256 or equivalent encryption; TLS 1.2 or higher; no plain-text storage of PINs or tokens on devices |
| Monitoring | Device fingerprinting, velocity and behavioural analytics, geo-location and SIM-change alerts |
| Incident reporting | Report confirmed or suspected compromises to RBZ within 3 hours; quarterly breach and risk-exposure summaries |
| Logs and recovery | Immutable logs with at least five years' retention; defined RTO and RPO; DR testing at least annually |
| Third parties and APIs | Penetration testing and code review of third-party solutions by internal teams or RBZ-approved firms before onboarding; OAuth 2.0 or mTLS, rate limiting and least-privilege APIs |
| Assurance | Annual cybersecurity audit reports by certified firms; independent penetration tests; TLPT for providers of critical payment infrastructure |
Sanctions
The guidelines set out graduated enforcement. Minor breaches, such as delayed reporting, may attract a formal caution or improvement notice. Moderate breaches, such as repeated failure to patch, may lead to monetary penalties or a mandatory third-party audit. Severe breaches, including data breaches or fraud due to negligence, or failing to report within three hours, can lead to suspension of services, rollback of product launches or licence revocation. The RBZ also reserves the right to publish the names of sanctioned providers.
A practical readiness plan
- Confirm scope. List DFS channels (apps, USSD, web, agents, APIs) and every intermediary and third party involved.
- Gap-assess. Map current controls against each section of the guidelines and the August 2025 Cybersecurity and Resilience Guideline.
- Fix reporting first. The 3-hour escalation window is demanding. Define triggers, owners and RBZ channels, and test them in a tabletop exercise.
- Test the channels that matter. Commission independent mobile, API and USSD testing, and validate backend exposure.
- Close third-party gaps. Update contracts with security, breach-notification and API clauses, and require testing evidence before onboarding.
- Build the evidence pack. Prepare for annual audit reports, quarterly summaries and RBZ inspections.
Common mistakes to avoid
- Treating the DFS guidelines as separate from the August 2025 Cybersecurity and Resilience Guideline, rather than building on it
- Relying on SMS OTP for high-value transactions despite SIM-swap and SS7 risks
- Onboarding third-party solutions without penetration testing and code review evidence
- Having no defined process to escalate incidents to the RBZ within 3 hours
- Overlooking agents, aggregators and white-label providers in risk assessments
Frequently asked questions
When did the RBZ DFS Security Guidelines take effect?
The guidelines took effect on 17 July 2026.
Do the guidelines apply to fintechs and payment service providers?
Yes. They apply to all RBZ-licensed institutions offering digital financial services, including fintechs and PSPs, and to DFS intermediaries such as aggregators, agents and third-party service providers.
How quickly must incidents be reported to the RBZ?
Confirmed or suspected compromises, such as fraud, platform downtime or customer data compromise, must be reported within 3 hours, in line with the Cybersecurity and Resilience Guideline. Providers must also submit quarterly breach and risk-exposure summaries.
Who can perform penetration testing of third-party solutions?
Third-party solutions must undergo penetration testing and code review either internally or through RBZ-approved cybersecurity firms, and providers must submit remediation plans for high-risk findings before launch.
Treat readiness as an ongoing assurance programme that improves resilience while making evidence easier to retrieve when the Reserve Bank asks.
SecuriCentrix supports Zimbabwean banks, mobile money operators, fintechs and PSPs with gap assessments, mobile and API testing and evidence preparation.
Free readiness checklists
Work through the checks with your team, then talk to us about any gaps.
Zimbabwe Cyber Resilience Readiness Checklist
23 checks · RBZ cyber resilience guidance
Get the free checklistNamibiaNamibia BID-30 and PSD-12 Readiness Checklist
23 checks · BID-30 and PSD-12 (2026)
Get the free checklistBotswanaBotswana Cyber Readiness Checklist
22 checks · Bank of Botswana, Data Protection Act 2024, Cybersecurity Act 2025
Get the free checklistRelated reading
Sources
This article is general guidance, not legal advice.
