Digital public infrastructure architecture
Digital Public Infrastructure architecture connects identity, trust, data exchange, payments, and service design into a governable public-service backbone.
What you get
- Country readiness diagnostic and maturity roadmap
- Identity, PKI and trust-services architecture
- Interoperability model — hub or federated
- Base-registry canonical data models
- Payment and G2P integration design
- ToR, technical annexes and M&E for IFI financing
Applied at: IBM · UNDP & EU · World Bank-funded programmes · PIR2-IT · 59 countries
What it means in practice
In practice, DPI architecture means designing digital identity, trust services, interoperability, payment rails, and citizen-facing services as one coherent operating model rather than as disconnected systems procured in isolation.
Common DPI patterns
Digital identity and national PKI, base-registry interoperability (a government ESB hub or federated X-Road-style exchange), e-signature and trust services, payment rails and G2P transfers, and life-event services built on once-only data reuse.
Typical architecture and governance patterns
Core patterns: digital identity, PKI trust services, interoperability and API layers, payments, life-event service design, public cloud and sovereign cloud alignment, data sharing controls, and execution-ready operating models. Execution context: cross-institutional transformation, regulated environments, public-sector modernization, and delivery settings where control matters as much as speed. Outcome: citizens prove who they are once, institutions reuse data instead of re-collecting it, and the platform survives the end of the donor loan.
Why this matters
Governments often fail when they buy technology by component instead of designing public-service infrastructure by architecture. DPI matters because it turns policy ambition into platforms that can scale nationally, remain interoperable, and stay under institutional control.
Related capabilities
Impact in numbers
Figures as recorded on named engagements — each one is listed on the Projects page.
How I approach it
- Diagnose readiness. Governance, institutional capacity and technical maturity, with a maturity-ladder roadmap.
- Anchor trust. National eID, PKI and e-signature as the foundation every service relies on.
- Pick the exchange model per country. Central govESB hub or federated X-Road-style exchange, depending on readiness.
- Fix the base registries. Population, civil registration, cadastre, vehicles and business — canonical models and once-only reuse.
- Add payments on top of identity. Instant payments, ISO 20022 and G2P transfers tied to eligibility.
- Finance and supervise. ToR, technical annexes and M&E for World Bank and other IFI operations, then supervision of delivery.
Where it was applied
- IBM · 2008 – 2011Romanian national interoperability backbone (SOA / govESB): ePassport, eID, eCadastre, eHealth and civil registration over national PKI; 48 data structures defined.
- IBM · 2009 – 2011National eID and citizen identity in 11 countries, including Romania, Moldova, Poland, Spain, Egypt, Nigeria and UAE.
- IBM · 2009 – 2015SSEDIC — 5-year consultation with 200+ eID experts on the Single European Digital Identity Community.
- UNDP & EU · 2014 – 2015Armenia digital identity and Police IT (US$60M committed); Georgia 112 emergency services architecture (US$50M committed).
- PIR2-IT · 2024 – PresentDPI in 35 states; government data exchange with 39 data structures defined; e-CODEX / ECRIS cross-border judicial exchange.
Where programmes usually go wrong
- Buying registries, portals and ID cards as separate tenders with no shared trust anchor.
- A central database where federation was the politically viable option.
- No canonical data models — every integration becomes a custom project.
- Financing the build but not the operating cost after the loan closes.
- Measuring success by systems delivered instead of services used.
Questions worth asking before you fund it
- Which registry is authoritative for each data item, and who owns its quality?
- Can a citizen prove identity online today without visiting an office?
- Is the exchange layer vendor-neutral and based on open standards?
- Who pays to run the platform in year five?