Doocat

How African Banks Should Decide Where to Host Customer Data

Content authorBy DoocatPublished onReading time12 min read
IT specialists monitor data in a modern control room, surrounded by large screens displaying analytics and metrics in a cool blue glow.

Decide by mapping every copy and access path of your customer data first, then checking the binding rules in each country you serve before comparing hosting models. Location is an output of legal obligations and control requirements. A provider gets approved after that evidence exists, never before.

Three location concepts are not interchangeable

Data residency is where data physically sits, and localization is a legal command to keep it there. Cross-border transfer is the act of data moving or becoming readable from another jurisdiction. Mixing them up is how approval packs fall apart under supervisory questioning. Residency is a choice your architecture makes. Localization is a choice the state has already made for you.

Kenya shows the gap between the two. Under Section 50 of the Data Protection Act, 2019, the Cabinet Secretary can require that certain processing happen only through a server or data center in Kenya, and Regulation 26 of the 2021 General Regulations turns that into a requirement to either process locally or keep at least one serving copy in a Kenyan data center.

Read that carefully and you'll notice the serving-copy option permits a foreign primary and demands a domestic replica, which means your compliance answer depends on which copy you call authoritative. Write that distinction into your data classification before anyone opens a vendor proposal.

Where does banking data actually travel?

Infographic on digital signatures and compliance essentials, featuring clean vector design, soft blue gradient background, and simple icons.

Customer data leaves the primary database within seconds of being written, and your approval has to cover every destination. A deposit posted in a branch lands in the core banking platform, then propagates to a replica and a backup target as well as the reporting and monitoring systems that watch it.

Each of those stops has an owner, and the owner sits outside your institution. Verizon's 2025 Data Breach Investigations Report, drawn from 12,195 confirmed breaches, found that third-party involvement doubled to 30% of all breaches in a single year.

The number matters here for a specific reason. If roughly one breach in three now arrives through someone else's environment, then the perimeter of your hosting decision is the perimeter of your supplier chain. Approve the chain or approve nothing.

Primary systems hold more than records

Your primary systems hold identity. Customer profiles and scanned national ID documents sit across the core banking platform and the mobile channel, with biometric enrollment data and card credentials in the integration layer that feeds your reporting.

Regulators have started naming these categories rather than leaving them to interpretation. The Central Bank of Nigeria's June 2026 circular covers "payment transaction data" generated in Nigeria, which practitioners read as receipts, transaction logs, balance histories, and card details tied to Nigerian accounts.

That breadth is the point worth catching. When a definition reaches logs and balance histories, it captures systems your technology team classifies as supporting infrastructure, so a scoping exercise that only inventories the ledger will under-report your obligations.

Secondary environments create hidden locations

Backups and logs are where approved architectures quietly become unapproved ones. A disaster recovery site in another country and a support engineer screen-sharing into production each create a storage or access location nobody drew on the diagram.

Temporary copies made during incidents are the worst offenders because they're created under pressure and rarely deleted on schedule. Verizon's researchers found the median time to remediate leaked secrets in a GitHub repository was 94 days, which gives you a sense of how long forgotten artifacts survive.

Three months of undetected exposure tells you something your vendor's architecture diagram won't. Residency controls that depend on human discipline during an outage will fail during an outage. Build the location constraint into the tooling, with deletion evidence you can produce on demand.

Which rules govern the hosting choice?

Identify five rule sets per country before you shortlist anything. Cover the privacy statute and the banking act with its subsidiary directives, then the outsourcing rules and cybersecurity requirements, plus the unwritten supervisory expectations your frontline examiner applies in practice. Skip the last one and you'll pass the legal review while failing the inspection.

The map has gotten denser fast. ALT Advisory's Data Protection Africa tracker, updated in January 2026, counts 43 data protection laws across the 55 African Union member states, with five more in draft.

Here's what that density implies for a bank with operations in four or five markets. You're managing the intersection of four or five independent regimes, and the binding constraint will be whichever country has the strictest localization rule. Scope the strictest jurisdiction first and work outward.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Mandatory rules need primary sources

A requirement is mandatory only when you can point to the statute or the circular that creates it. Law firm commentary and vendor compliance pages are navigation aids. They are not evidence, and a supervisor will not accept them as such.

Nigeria's current obligation sits in a specific instrument. Circular PSS/DIR/PUB/CIR/001/004 requires that all payment transaction data generated in Nigeria be stored and managed in Nigeria from 1 January 2027, which applies to deposit money banks and payment solution providers.

That deadline is now weeks away, which creates a practical test for every proposal on your desk. Ask the vendor to cite the clause, not summarize it. If they can quote the circular reference and tell you which of their components it touches, they've done the work. If they answer with a certification logo, they haven't.

Recommended controls need separate treatment

Label every control as either compulsory or recommended, and keep the two lists apart. Blending them inflates your cost estimate and makes it harder to defend the controls that genuinely are required when a vendor pushes back on price.

South African practice illustrates why the line moves. The Prudential Authority's Directive 3 of 2018 and Guidance Note 5 of 2018 remain the only published instruments on cloud computing for banks. In Joint Communication 2 of 2025 the Authority and the Financial Sector Conduct Authority confirmed they've begun drafting a binding instrument, to be published for consultation.

So a control that's guidance today becomes a standard tomorrow, and the consultation draft is your early warning. Treat anything flagged in a live consultation as near-mandatory in your architecture even while you record it as recommended in the approval pack, because retrofitting after the instrument lands costs more than building for it now.

Which hosting model fits the bank?

Score the hosting options on one weighted matrix rather than debating them narratively, because a narrative argument always rewards whoever speaks last. Weight the criteria before you see the scores, and get the board risk committee to sign the weights.

Nine criteria carry the decision:

  • Legal feasibility and regulator access, which together act as gates rather than scores

  • Latency to your channels, resilience, and the skills your team actually has in-house

  • Concentration risk, total cost, scalability headroom, and the complexity of exiting

Context sets your realistic options. The Africa Data Centres Association reports the continent holds 360 MW of operational capacity, roughly 0.6% of global capacity, with 238 MW under construction.

Scarcity that severe changes how you weight cost. In a thin market, the cheapest compliant option today is rarely the resilient one in three years, so weight exit complexity and capacity headroom higher than a European bank would.

Domestic hosting maximizes local control

In-country hosting answers the residency question outright and keeps your supervisor's access rights uncomplicated. It also hands you a harder engineering problem, because a single domestic facility is not redundancy and a second rack in the same building is not a disaster recovery site.

Test the local market honestly before committing. South Africa held 40.76% of Africa's data center market in 2025, and Johannesburg carries most of the hyperscale builds, which means capacity outside a handful of metros thins out quickly.

That concentration has a direct consequence for your recovery plan. If your country has two credible facilities and both sit on the same grid and the same fiber route, your recovery time objective is a statement of intent. Measure the separation in power source and network path, not kilometers, and write the measurement into the approval evidence.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Regional hosting can balance trade-offs

A neighboring jurisdiction can give you better infrastructure while keeping the transfer lawful, provided your home supervisor can still reach the data. That last condition is the one that kills most regional proposals, and regulators state it.

The Bank of Ghana's Outsourcing Directive instructs regulated institutions not to outsource to a jurisdiction that is inadequately regulated or has secrecy laws that hamper access to data by the Bank or the institution's external auditors.

Notice what that test is measuring. It's whether your regulator and your auditors can get in. So a regional option in a jurisdiction with strong privacy law but weak mutual cooperation arrangements can fail, while a nearby market with modest legislation and a cooperative supervisor passes. Assess the access path, then the legal regime.

International cloud expands capability

Global cloud platforms give you services and geographic redundancy no African facility currently matches, and they bring transfer restrictions and a long subcontractor chain with them. Both halves of that sentence are true at once, and the decision turns on which workload you're placing.

Concentration deserves particular attention. The Financial Stability Board's survey of 294 financial institutions found respondents rely on a narrow set of major providers and use at least two on average, with the same four names appearing most frequently worldwide.

The industry-level finding has a bank-level reading the report doesn't spell out. If your peers across the market sit on the same two providers, your institution-specific exit plan protects you from a provider failure but not from the correlated outage that takes your competitors down simultaneously and puts the supervisor on the phone to all of you at once. Plan for the systemic case separately.

Which technical controls preserve bank control?

Control over hosted data comes from keys and logging. A foreign-hosted system where you hold the keys and own the audit trail gives you more practical authority than a domestic one where the vendor administers everything.

Build the evaluation around least-privilege access with named individuals and encryption in transit and at rest. Require bank-held keys and tenant segregation, with immutable logs you can export and a documented path for your regulator to see what it needs. Remote administration deserves its own line, because support access is where residency breaks quietly.

The Bank of Ghana's Cyber and Information Security Directive makes some of this explicit as it requires verification of jurisdiction and data residency alongside current certifications including ISO/IEC 27017 and SOC 2 Type II.

Certification lists are the easy part to verify and the weakest part to rely on. An ISO 27017 certificate tells you a process existed on audit day. Your key ownership tells you who can read the data tomorrow.

What must vendor contracts guarantee?

The contract must name the countries where data is stored and processed, and require written approval before any of them change. Everything else in the agreement depends on that clause holding, because a provider that can relocate your workload unilaterally can void your compliance position overnight.

The European Banking Authority's outsourcing guidelines set a useful drafting benchmark. For critical or important functions, the agreement must specify the location where data will be kept and the provider must notify the institution of any proposed change. The outsourcing register records the country for every arrangement regardless of criticality.

Beyond location, insist on named subcontractor disclosure and audit rights that survive sub-outsourcing. Require defined incident notification windows and direct regulator access, with certified secure deletion and termination obligations that bite.

The register requirement is the clause most African banks skip, and it's the one that makes the rest enforceable. Without a maintained inventory, you cannot prove at inspection which contract governs which dataset.

What evidence supports final approval?

Approval rests on a documented pack. Assemble it as a checklist and treat any missing item as a blocking condition rather than a follow-up action, because follow-up actions after go-live have a poor completion record.

The pack needs:

  1. Data-flow diagrams covering every stored copy and access path, with the legal analysis per country and any regulatory correspondence or written approvals attached

  2. The risk assessment, target architecture, key ownership statement, and resilience test results

  3. Provider attestations, the signed contract, the subcontractor register, the incident response plan, and evidence that the exit procedure has been executed in a test

The Financial Stability Board's third-party risk toolkit, published December 2023, covers the full relationship lifecycle from due diligence through exit, and supervisors increasingly use it as a reference point.

Of everything on that list, the tested exit is the item that converts the pack from paperwork into assurance. A plan that has never been run is a hypothesis.

Can Doocat fit the approved model?

Doocat can fit, and the way to find out is to test it against the architecture you've already approved. Bring your data-flow requirement and your jurisdiction list to the first technical conversation.

Doocat is a banking platform built for microfinance institutions and banks by Energize Global Services, a fintech company founded in 2007 with delivery centers across Europe and Africa. The platform is Kubernetes-native with independently deployable microservices and runs on AWS, GCP, Azure, private cloud, or on-premises infrastructure. Greenfield deployments go live in 12 to 20 weeks.

That deployment range is the part your procurement team should press on. A platform that genuinely runs on-premises and in cloud supports more than one approved location model, which matters when your Nigerian entity faces a localization deadline your Kenyan entity doesn't.

Ask for written answers on processing locations per module and support access paths, plus subcontractors and deletion evidence. Request a demo and bring those questions to it.

Ready to digitise your financial institution?

Talk to our team about your roadmap and discover scalable digital banking solutions tailored to banks, fintechs and microfinance institutions.

Request a Demo →

Before choosing a location, list each dataset, stored copy, processing system, country, responsible owner, access route, and retention period. Include backups, logs, replicas, support tools, and incident-created files. This inventory shows where data can be stored or viewed and which controls each location requires.

Assess the data flow separately for each country where customers, systems, or support staff are located. Identify the strictest applicable localization or access rule first, then test whether one architecture satisfies every jurisdiction. Keep country-specific exceptions in the approval record instead of treating the region as one legal market.

Yes. A backup stored in another country creates a cross-border transfer, even when staff never open it. Remote access from abroad can also create a transfer without moving the primary database. Record the backup provider, storage country, encryption arrangement, access permissions, and deletion process in the data-flow assessment.

Ask where support personnel are located, which systems they can reach, how access is approved, and whether every session is logged. Require named accounts, time-limited permissions, bank-controlled keys where possible, and evidence that emergency access is reviewed and removed after the incident ends.

Reject the proposal when the provider cannot identify storage and processing countries, disclose subcontractors, support regulator access, or prove secure deletion. Reject it when the exit plan has not been tested or the architecture depends on staff following manual residency steps during an outage. Missing evidence is a blocking issue.

Schedule a Meeting

Book a time that works best for you

You Might Also Like

Discover more insights and articles

Two diverse professionals engaged in a friendly discussion over a tablet in a bright, modern office with large windows and blurred coworkers.

Murabaha Financing: Contracts and Examples for African Banks

This article walks through how murabaha financing becomes a working bank product: the transaction sequence and the controls your core system has to enforce. It is written for the teams who have to build the thing and then defend it in an audit.

A mid-aged manager reviews documents at a warm wood desk in a sunlit office, with a monitor displaying analytics in the background.

SACCO Management System: A Buyer’s Guide for Kenyan SACCOs

This article walks through how a Kenyan savings and credit cooperative can define what it actually needs from new software and check vendor claims against evidence before it plans a migration that doesn't break member balances. It ends with a checklist you can score vendors against before any price talk begins.

Close-up of hands holding a smartphone displaying a banking app, set in a cozy home office with blurred background elements.

Mobile Money Interoperability in Ghana: How GhIPSS MMI Works

This article maps the four transfer flows supported by Ghana's national mobile money interoperability platform and shows who owns each step of them. It covers transaction direction and the questions to settle before a new connected channel goes live.

A business manager discusses loan strategies in a bright office, holding a tablet displaying a banking dashboard, with employees working nearby.

How African MFIs Can Reduce Fraud in Cash Loan Collections

Cash collection fraud shrinks when every repayment carries a unique, device-generated receipt reference tied to one borrower and one loan, and when the officer who collects cash never posts or reconciles it. Add daily handover matching and an independent borrower complaint channel, and most leakage becomes visible within 24 hours instead of months.