Strategy7 min read

Attacked but Not Breached? The 72-Hour Reporting Decision Every Fintech Needs to Be Able to Prove

Under Nigeria's Data Protection Act, not every cyberattack is a reportable breach. Here is how the 72-hour test works, and the decision record that proves your call.

Since Friday, 30 October 2026, Nigerian fintechs have been dealing with a wave of cyberattacks. Lendsqr's CEO, Adedeji Olowe, wrote publicly that his company had been "battling a wave of cyberattacks" since that day. He also wrote that it had lost no money and no data. Other firms have reported losses, but those figures have not been independently verified.

During an incident, your team has to answer two questions: do we have to report this, to whom, and by when? And if you decide not to, can you prove that was the right call?

This piece walks through the Nigeria Data Protection Act 2023 (NDPA) test, the other clocks that may apply, and a decision record you can build now. It is not legal advice.

Attacked is not the same as breached

The NDPA defines a "personal data breach" as a breach of security "leading to or likely to lead to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or access to, personal data" (s.65).

Two things have to be true: a security failure, and personal data affected or likely to be affected. An attack on your source code or payment infrastructure that touches no personal data is a serious incident, but on that definition it is not an NDPA personal data breach.

An NDPC official reportedly made the same point to BusinessDay: such an attack "does not automatically constitute" a reportable breach. Note "automatically". You still have to check, and show that you did.

The 72-hour test

If personal data is involved, s.40(2) sets the clock. As a data controller, you must notify the Nigeria Data Protection Commission (NDPC) "within 72 hours of becoming aware of a breach which is likely to result in a risk to the rights and freedoms of individuals."

Three details change how you run an incident:

  • The clock starts at awareness, not at the attack. Your detection and escalation timestamps become evidence.
  • Risk is the threshold. You may weigh how well your controls worked, "including any encryption or de-identification of the data", what you did afterwards, and the sensitivity of the data (s.40(7)).
  • You can notify in phases "without undue delay" (s.40(9)). Missing facts are not a reason to miss the clock.

Each notice must name a point of contact, the likely consequences and the measures taken or proposed (s.40(4)). The NDPC's General Application and Implementation Directive (GAID 2025, Art 33(5)) adds the date or period of the breach, a risk-of-harm assessment and an estimate of the people at real risk.

If you are a processor for another company, you must notify that controller "on becoming aware of the breach" and answer its questions (s.40(1)).

When you must tell your customers

Where a breach is likely to result in a high risk to individuals, the Act says you must "immediately" tell the affected people, in plain language, with advice on how to protect themselves (s.40(3)). If contacting each person directly is not feasible, a public notice is allowed.

GAID gives a practical test for high risk. A breach is likely high-risk where the person "may become a victim of fraud, identity theft or exposure of sensitive personal data" (Art 33(2)). For a fintech holding account details, BVNs or transaction histories, that test will often be met.

GAID Art 33(3) is stricter: notify affected people "immediately after becoming aware of the breach", with no "high risk" qualifier. If you are close to the line, plan for the stricter reading.

The part most teams miss: the record of every breach

Section 40(8) is the obligation that applies whether or not you notify anyone:

"A data controller and data processor shall keep a record of all personal data breaches, comprising the facts relating to the personal data breach, its effects and the remedial action taken in a manner that enables the Commission to verify compliance with this section."

It covers all breaches, not only the notifiable ones. GAID also requires your Data Protection Officer's semi-annual report to cover "breach notification to the Commission and to data subjects" (Art 13(5)(m)), and the audit return asks you to confirm the notice "was sent to the NDPC within 72 hours", or "Not Applicable".

"Not applicable" is a claim. The breach record is how you support it.

Other clocks that may apply

The NDPA is not the only regime. Check these too:

  • CBN, for deposit money banks and payment service banks. The 2024 Risk-Based Cybersecurity Framework requires these banks to report all cyber incidents "not later than 24 hours after such incident is detected", personal data or not.
  • CBN, for other licensed institutions. Most fintechs (payment service providers, mobile money operators, switches, microfinance banks and lenders) are not covered by it. We could not confirm the clock in the framework that applies to them. Check your own CBN framework and licence conditions.
  • The Cybercrimes Act. Law-firm commentary reports that the 2024 amendment shortened the time to report cyber threats or attacks to the relevant sectoral computer emergency response team from seven days to 72 hours (s.21). We have not read the amended text, and commentaries differ on whether the clock runs from detection or from the attack. Take advice.
  • National-scale incidents. GAID Art 33(4) asks you to give "immediate information" to all relevant authorities, including the NDPC, where it may help contain "imminent data breaches on a national scale". A coordinated, sector-wide wave may be that kind of situation.

A one-page decision record you can build now

Use one record per incident, answering the questions a regulator would ask:

  1. Detection: when it was detected, by whom, and when it was escalated. This is your "awareness" time.
  2. What happened: the systems affected and the attack type.
  3. Personal data: was any involved or likely to be involved? Which categories, and roughly how many people and records?
  4. Risk assessment: the s.40(7) factors (controls such as encryption, steps taken, the nature and sensitivity of the data), and the fraud or identity-theft test.
  5. Decision: notify the NDPC, notify customers, notify the CBN or a CERT, or none. Who decided, when, and why.
  6. Notices sent: to whom, when, and what was said. Include later phased updates.
  7. Remediation: the actions taken, with dates.

Keep it timestamped and hard to edit after the fact. A log assembled after the event is weak evidence.

From Olowe's account of the current wave, the basics are: reissue every access token, enforce two-factor authentication on email, cloud, code and money consoles, remove former staff, rotate keys, and phone-verify any change to a payment destination.

NDPA penalties are maximums. For a controller or processor of major importance, the cap is the greater of ₦10 million or 2% of the previous year's annual gross revenue (s.48). The bigger risk is being unable to explain your call when the NDPC, the CBN or a partner bank asks.

If you can't produce this record today, that is the work we help teams scope: incident and decision logging, audit trails, and the reporting that sits on top. The first conversation is a free, no-pressure 45-minute structured call: start the conversation. For the prevention side, see our piece on the basic gaps behind Nigerian bank breaches.


Sources: Nigeria Data Protection Act 2023 ss.40, 48 and 65, and the NDPC GAID 2025 Arts 13 and 33, read directly; CBN Risk-Based Cybersecurity Framework for DMBs and PSBs (2024), read directly. The NDPC official's remark and the unverified loss reports: BusinessDay, 7 November 2026. The attack wave and controls: Adedeji Olowe, 4 November 2026. Cybercrimes Act s.21: law-firm commentary (Templars, August 2024); the amended text was not reviewed. This is a summary, not legal advice.

Daniel Okoronkwo

Daniel Okoronkwo

Founder, Swiftascale Technologies

Daniel founded Swiftascale to help growing businesses build the operational foundations they need to scale without breaking. He has worked with SMEs across professional services, technology, and consumer sectors, helping them diagnose operational gaps and implement systems that produce measurable results.

Connect on LinkedIn

Ready to act on it?

Book a free consultation.

We talk through your specific situation — no slides, no generic frameworks. Just a direct conversation about what is getting in the way of your growth.

Book a consultation