Free readiness checklists for NIS2, DORA, ISO 27001, PCI DSS, POPIA, JS2 and Southern Africa.Get a checklist →

Zimbabwe

RBZ DFS Security Framework 2026: A Practical Readiness Guide

The Reserve Bank of Zimbabwe's Guidelines on Digital Financial Services Security took effect on 17 July 2026. Here is what they require and how to prepare.

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

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

  1. Confirm scope. List DFS channels (apps, USSD, web, agents, APIs) and every intermediary and third party involved.
  2. Gap-assess. Map current controls against each section of the guidelines and the August 2025 Cybersecurity and Resilience Guideline.
  3. Fix reporting first. The 3-hour escalation window is demanding. Define triggers, owners and RBZ channels, and test them in a tabletop exercise.
  4. Test the channels that matter. Commission independent mobile, API and USSD testing, and validate backend exposure.
  5. Close third-party gaps. Update contracts with security, breach-notification and API clauses, and require testing evidence before onboarding.
  6. 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.

Related reading

Sources

This article is general guidance, not legal advice.

Free checklist

Zimbabwe Cyber Resilience Readiness Checklist

23 checks covering the RBZ Cybersecurity and Resilience Guideline, the DFS Security Guidelines and the Cyber and Data Protection Act, with the evidence to keep for each one.