---
title: "Payment-Data Localisation and Personal-Data Localisation Are Different Rules: Where Nigeria's Two Regimes Diverge"
canonical: "https://theupsidejournal.com/articles/nigeria-payment-personal-data-localisation/"
published: "2026-11-11"
column: "The Beltway Byte"
author: "Olusegun (Olu) Olufunmiloye"
subtitle: "The Central Bank of Nigeria sets where covered payment records are kept, while the Nigeria Data Protection Act governs when personal data may be transferred abroad."
description: "Nigeria’s CBN circular fixes where covered payment transaction data is kept. The Nigeria Data Protection Act 2023 governs when personal data may leave Nigeria."
---

# Payment-Data Localisation and Personal-Data Localisation Are Different Rules: Where Nigeria's Two Regimes Diverge

*The Central Bank of Nigeria sets where covered payment records are kept, while the Nigeria Data Protection Act governs when personal data may be transferred abroad.*

## Executive Summary

Nigeria’s payment-data localisation rule sets a place for keeping and managing payment records. Its personal-data law sets conditions for sending information about people abroad. The Central Bank of Nigeria (CBN) requires covered payments participants to store and manage transaction data generated within Nigeria in Nigeria, with full compliance effective 1 January 2027. The Nigeria Data Protection Act 2023 (NDPA) already regulates transfers of personal data out of Nigeria. A payment record that identifies a person can bring both rules into play. An operator therefore needs evidence of where the payment record is kept and a separate legal basis for any transfer of personal data it contains.

## Where the two regimes diverge

A Nigerian server answers a question about location. It leaves open a question about disclosure if a copy goes to an overseas service provider. Conversely, a lawful basis for sending personal data abroad does not establish that the underlying transaction record is stored and managed in Nigeria. Calling both requirements data localisation obscures the difference at the point where a compliance team has to approve a system.

The Upside Journal’s [analysis of the CBN’s payments circular](https://theupsidejournal.com/articles/nigeria-payments-data-rule-oversight-instrument/) examines the wider supervisory purpose. The distinction here is narrower. The CBN tests the activity of a payments participant and the origin and location of its transaction data. The NDPA tests whether the information concerns an identifiable person and whether a controller or processor may transfer it from Nigeria. One service can have several data flows, each with a different answer to those tests.

## What does the CBN require by 1 January 2027?

The CBN Payments System Supervision Department supervises Nigeria’s payments system. Its 15 June 2026 circular, reference PSS/DIR/PUB/CIR/001/004, was signed by director Rakiya O. Yusuf. Paragraph 2 covers financial institutions and participants facilitating payments within Nigeria. It requires the payment transaction data generated within Nigeria to be stored and managed there in accordance with applicable Nigerian data protection laws and regulations. The circular gives 1 January 2027 as the effective date for full compliance with that requirement.

A **payment system participant** in this context is an institution involved in facilitating payments. The circular is addressed to categories including deposit money banks, microfinance banks, mobile money operators, switching and processing companies, and payment solution service providers. The list matters when a payment product is sold through several organisations. A merchant may deal only with a branded interface while a different entity switches the transaction and another maintains the ledger. The [analysis of the CBN’s regulatory sandbox](https://theupsidejournal.com/articles/cbn-regulatory-sandbox-2-0/) provides context on the regulator’s relationship with payment operators. For localisation, the practical starting point is the function each entity performs and the records each holds.

**Payment transaction data** describes records of payment activity. The circular uses the term without defining a field-level boundary. An authorisation record, a settlement extract and a reconciliation log are useful candidates for an inventory, but the circular does not classify each artifact or specify a technical architecture. It gives no express mirroring exception in the operative clause. Keeping a local database should therefore be evidenced as a fact about the system, while any question about the permissibility of a foreign copy or overseas administration remains a separate interpretation to resolve on the relevant facts.

## When may personal data leave Nigeria?

**Personal data** is information relating to an identified or identifiable individual. The Nigeria Data Protection Act 2023 is the statute governing its processing. Its scope in section 2 includes controllers or processors domiciled, resident or operating in Nigeria, processing that occurs in Nigeria, and certain processing of personal data of a data subject in Nigeria by a controller or processor outside the country. A **controller** determines the purposes and means of processing. A **processor** acts on a controller’s behalf. The **Nigeria Data Protection Commission** (NDPC) administers the Act.

Part VIII sets the framework for **cross-border transfer**, the sending of personal data from Nigeria to another country. Section 41 requires a recognised basis for the transfer. One route is adequate protection applicable to the recipient through a mechanism specified in the Act, such as law, binding corporate rules or contractual clauses. Section 42 explains how to assess adequacy. It asks, among other things, about enforceable rights, redress and public-authority access. A contractual clause supports a transfer only if it affords an adequate level of protection when assessed under section 42. Section 41 also requires the controller or processor to record its transfer basis and the adequacy of protection.

Section 43 provides limited alternative grounds where adequate protection is absent. Two examples are informed consent that has not been withdrawn, with the individual made aware of the risks from the lack of adequate safeguards, and a transfer necessary for performance of a contract with the individual. Those conditions are specific. The fact that an overseas vendor makes a workflow cheaper does not establish that the transfer is necessary to perform the individual’s contract.

The NDPC’s **General Application and Implementation Directive 2025** sets out how the Commission applies the Act. Article 45 and Schedule 5 address cross-border transfers. Aluko & Oyebode’s notice of 17 September 2025 gives 19 September 2025 as the date on which the directive becomes fully effective. These personal-data obligations have their own legal timetable. The January 2027 date in the CBN circular concerns the payments requirement. The distinction helps explain why [data-protection rules can shape competition](https://theupsidejournal.com/articles/regulatory-weaponization-open-banking-data-protection-africa-tech-defense-2026/) even when firms use the same infrastructure. A supplier still needs to demonstrate what happens to personal data when it delivers the service.

## Where can the same record fall under both?

Consider a hypothetical payments processor in Lagos that keeps an authorisation record in Nigeria and sends a copy to an overseas fraud service. The record contains the transaction amount, a timestamp and an account identifier that the recipient can associate with an individual. The original record belongs in the assessment of payment transaction data generated within Nigeria. The overseas copy also calls for a separate NDPA transfer assessment because the identifier makes the data personal. Establishing the privacy transfer basis would not settle whether the offshore arrangement satisfies the **CBN** requirement.

A different hypothetical makes the boundary visible. A business holds personnel records for employees in Nigeria and sends them to a payroll provider abroad. The outbound data may trigger the NDPA transfer rules even if the files contain no payment transaction data within the meaning of the CBN circular. The CBN rule, in turn, does not make identifiability the trigger for localisation. Removing names from a transaction dataset does not resolve whether it is still within the payments rule. Where tokens can be linked back to individuals, the privacy classification may also remain.

At the point of overlap, the more restrictive obligation can determine the design, and both obligations still need their own evidence. Suppose a vendor offers an adequate transfer mechanism but its recovery architecture cannot demonstrate that covered transaction records are stored and managed in Nigeria. The vendor still leaves the CBN question unanswered. Suppose instead that a local service can show where it keeps the ledger but forwards identifiable incident attachments abroad. The local ledger still leaves the NDPA question unanswered. Treating [digital trust as infrastructure](https://theupsidejournal.com/articles/digital-trust-infrastructure-foundation-africa/) means being able to reconstruct these decisions for a particular record and supplier.

## What should an operator map first?

Start with the path of a transaction. Identify who facilitates the payment, where the transaction data is generated and where the record is written, read, restored and managed. Record the location of production data, backup and failover, and check whether the answer holds during an incident. The existing [analysis of fragmented payment systems](https://theupsidejournal.com/articles/africa-payment-fragmentation-infrastructure-tax/) shows why that inventory matters across interfaces. A payment travels through several institutions, and the copies that are easiest to overlook often sit in the systems that reconcile their records.

Then trace personal data separately. Identify the controller, processor and any subcontractor, what information can identify a person, which destinations receive it and what the recipient can do with it. Include feeds, support tickets and diagnostics alongside the main database. Remote access and overseas troubleshooting deserve review on the facts of the arrangement, including whether data is viewed, extracted or copied, instead of assuming the vendor’s marketing label resolves the legal question.

That leaves two sets of records for a launch or supplier change. For the CBN rule, document the payment role, record scope, generation point, storage and management arrangements, and any unresolved interpretation. For the NDPA, document the recipient, purpose, transfer basis and applicable safeguards. Give both records named owners and test the vendor’s answer against a recovery exercise and a support workflow. If a proposed arrangement rests on an exception the circular does not state, obtain a grounded interpretation before relying on it.

## Key Takeaways

- The CBN circular requires covered payment transaction data generated within Nigeria to be stored and managed in Nigeria, with full compliance effective 1 January 2027.
- The NDPA allows outbound transfers of personal data subject to a recognised basis, including adequate protection or a condition under section 43.
- The CBN circular refers to applicable data protection laws generally. The NDPA and NDPC directive supply their own privacy obligations.
- A single payment record can trigger both regimes when it contains information about an identifiable person.
- Operators need separate evidence of where transaction records are kept and the legal basis for any outbound personal-data flow.

## Conclusion

For a payments operator in Lagos and its partners in London or Washington, the first decision is to classify the actual records and trace each copy. That makes it possible to establish where the CBN rule attaches, where an NDPA transfer assessment is required and where the same design has to satisfy both. The cost of treating them as one rule shows up when a team has to revisit vendor contracts, recovery and support after it has already committed to an architecture.
