Smart City Africa Digital public services need an interoperability spine, not a portal
Why African cities should build digital services on a shared identity, payment and data-exchange layer — and what the OECD and World Bank evidence implies for procurement and pilot logic.
Most digital-government failures in African cities are not failures of intent or of front-end design. They are integration failures: each new service rebuilds identity, payment and notification from scratch, agencies do not share a working data backbone, and residents end up carrying the integration burden in person and on paper. The honest reframe is to stop treating digital public services as a series of portal launches and to start treating them as instances of a shared platform — what the World Bank and OECD now call digital public infrastructure (DPI). The interoperability spine is where the work lives.
The World Bank’s recent work on digital public infrastructure for digital governments puts trusted identity, payment rails and data exchange at the centre of a working platform. Without a secure, accessible identity layer, every service has to verify residents from scratch; without a payment layer, fees and disbursements get re-invented for each form; without a regulated data-exchange layer, sectoral databases stay locked into the systems that produced them. Each of those gaps shows up at the front end as a longer queue or an unreachable service — but the cause sits one layer down.
The OECD’s review of digital government draws a parallel point from the demand side. Public administrations move closer to being open, transparent, participatory and trustworthy when they redesign around services that residents and businesses actually use, with explainability and accessibility designed in. The OECD’s separate work on AI in public procurement adds a procurement-side caveat: most government AI projects are still in pilot or exploration phases with limited scaling and limited public documentation. That is not a reason to avoid the work — it is a reason to procure for transparency, exit and portability from the start.
UNECA frames Africa’s digital transformation along four dimensions — infrastructure, affordability, skills and e-government — and shows the interaction between them clearly. A city that connects schools and clinics through a coherent telecommunications plan but does not invest in the identity, payment and data-exchange layer underneath ends up with islands of digital service. A city that builds the interoperability spine first but skips the connectivity work has a clean architecture nobody can reach. The defensible path is to do both, at the same speed, on a shared procurement and governance plan.
The practical implication for cities and metropolitan authorities is that “digital public services” is a programme, not a project. The constituent parts — service-journey mapping, an open-standards interoperability layer, a data-governance regime that holds up to inspection, accessible identity and payment rails, procurement contracts that protect open standards and exit, and a community-engagement and complaint path — are interdependent. Sequencing them as discrete pilots without a connecting architecture is the failure mode the OECD review describes. Sequencing them under a shared interoperability spine is what turns digital public services from a slogan into something residents can use, contest and improve.
Talk to us about applying this in your city.
Which themes fit best is highly city-specific. Tell us a little about the city, the partners involved, and what kind of decision you're trying to make. We'll come back with the right entry point.