Home Affairs wants your ID. SARS wants your ID. Social Development wants your ID. Each time you log into a different government portal, you enter the same details into a different broken form. This is not digital transformation; it is bureaucracy with a loading spinner. The MyMzansi Digital Transformation Roadmap wants to end this repetition by treating identity, payment, and data exchange as public infrastructure: built once, secured once, and reused by any department or authorised private service.
At the center of the proposal is a Digital Service Unit that reports to the Presidency. Its job would be to stop departments commissioning separate versions of the same wheel and instead mandate shared components. The roadmap also carries an explicit instruction to kill unsuccessful pilots rather than letting them drain budgets indefinitely, and to architect systems so that no single vendor or platform can hold the entire estate hostage.
From forms to rails
Right now, a department that wants to go digital usually photographs its paper process and uploads it. You still queue, photocopy, and fill in the same fields; you just do it in a browser. Each department owns its own silo, so the same citizen ends up with conflicting addresses across databases, and nobody trusts the data enough to automate a decision. The roadmap argues for the opposite approach. Strip a service back to its atomic needs, wire those needs into common rails, and let the interface layer float on top. Identity becomes a verified API call. Payment becomes a standardized gateway. Data exchange happens through protocols every department shares.
The practical difference is stark. Instead of Home Affairs, SARS, and Social Development each running their own verification engines, they would draw from one trusted identity layer. Instead of every new service starting with a six-month procurement to rebuild payment plumbing, developers would connect to existing pipes. The innovation is not in the webpage the citizen sees, but in the components no citizen sees, which every service depends on.
What becomes possible
When government treats identity, payments, and data exchange as reusable infrastructure rather than departmental property, the cost of building a new service drops sharply. A public sector team can focus on the actual service logic, not on negotiating a new security audit for the same ID check. A private developer can build a fintech tool, a property platform, or a health app that authenticates users against government-verified credentials without constructing its own compliance fortress from scratch. The same logic applies to data exchange. If a social grant system can pull verified income data from SARS through a standardized pipe instead of requesting paper proof, eligibility checks become instant and fraud becomes harder.
The roadmap explicitly envisions both public and private builders creating services on these trusted components. This changes the state’s role. Instead of gatekeeping every digital interaction, it supplies the foundation and lets others build above it. Smaller local firms can compete for government-facing work because the barrier to entry falls. You no longer need the capital to build an entire stack; you need the imagination to build something useful on top of one.
The hard part
Shared infrastructure only works if the custody of data is airtight and the APIs stay live. The roadmap acknowledges this by pushing for open standards and modular design, ensuring one vendor failure does not collapse the entire network. This means moving away from the current pattern of massive, monolithic tenders that lock the state into a single
