Centre for Digital Public Infrastructure
english
english
  • THE DPI WIKI
    • 🎉About the DPI Wiki
    • 🔆What is DPI?
    • ✨DPI Overview
    • 📝DPI Tech Architecture Principles
      • 🔗Interoperability
      • 🧱Minimalist & Reusable Building Blocks
      • 💡Diverse, Inclusive Innovation
      • 💠Federated & Decentralised by Design
      • 🔐Security & Privacy By Design
    • 🎯DPI Implementation & Execution Guidance
    • 🆚DPG and DPI
    • ❓What DPI can I build?
    • 🥇First use case for DPI
    • 📘Inputs for designing a DPI informed digital transformation strategy
    • 💰How much does it cost to build DPI?
    • 📢Is my system a DPI?
      • TL; DR - Is my system a DPI?
  • Mythbusters and FAQs
    • 🔯DPI and Mandating Adoption
    • 🔯DPI and Private Competition
    • 🔯DPI and Privacy / Security
    • 🔯DPI and the Digital Divide
  • Technical Notes
    • 🆔Identifiers & Registries
      • Digital ID
        • Capabilities on ID system
        • ID-Auth
        • Face Authentication
        • eKYC/ Identity profile sharing
        • Single Sign On (SSO)
        • QR Code for Offline ID
    • 📂Data Sharing, Credentials and Models
      • A primer to personal data sharing
      • Data standards
      • Verifiable Credentials
      • Building Data Analytics Pipelines
      • eLockers
      • Non-personal Anonymised Datasets
    • 🔏Trust Infra
      • Digital Signatures and PKI
      • eConsent
      • eSign
    • 🛒Discovery & Fulfilment
      • Platforms to Protocols
    • 💸Payments
      • Financial Address
      • Interoperable QR Code
      • Interoperable Authentication
      • Interoperable Bill Payments
      • Cash in Cash Out (CICO)
      • Financial Address Mapper (G2P Connect)
      • G2P Payments
  • Initiatives
    • 🌐DPI advisory
    • 🚀DPI as a Packaged Solution (DaaS)
      • 💡Why do we need DaaS?
      • 🎯DaaS in a nutshell
      • 📦Pre-packaged DaaS kits
      • ♻️Reusable DaaS Artefacts
      • 3️⃣A 3-step process from idea to implementation!
      • 📈Funded DaaS Program overview
      • 👩‍💻Cohort 1: DaaS Offerings
        • Digital authentication
        • Digital credentials
        • ID Account Mapper
      • 🖥️Co-create with us!
      • 💬Upcoming DaaS cohorts
        • Functional Registries
        • AI Assistant
      • ❓FAQs on DaaS
        • Country x DPG MOU /LoI FAQs
        • Ecosystem Participation Terms FAQs
    • 📑DPI Residents Program
    • ⚖️DPI-CPA
    • 💸G2P Connect
    • 📨User Centric Credentialing & Personal Data Sharing
    • ⚕️DPI for Health
    • 🌍Agri Connect (forthcoming)
  • References
    • Glossary
    • Curated Specifications
  • Additional Info
    • 🤝Licensing
    • ✍️Contact Us
Powered by GitBook
On this page
Export as PDF
  1. Technical Notes

Identifiers & Registries

Who is the counterparty? Can I trust them?

Verifying ID & accessing profile data of people, entities, & objects is a crucial foundational function of digital economies. When moving from physical to digital interactions, the first complication is establishing trust as to the identity of the counterparty. It is crucial that this identity is verifiable: i.e. can be authenticated in some means (a mobile one time password, a digitally signed QR code, a biometric fingerprint scan, or even a face ID authentication).

A country should have multiple identities to fulfill multiple purposes and functions across sectors - but one or more of them should provide a foundational capability of authenticating that the individual is who they say they are, and returning a few commonly required data fields (such as name, gender, date of birth, and address) via an open API. Functional identities (such as voter IDs, social protection IDs, or drivers licenses) should also strive to make their profile data accessible via APIs or through other digitally native means.

An identity system is a registry of persons. Countries also need foundational registries of entities (such as businesses, hospitals, schools, etc.) to allow sector-specific digital service providers to innovate based on shared datasets. These registries should provide digitally signed data - to ensure it is tamper proof - and preferably via open APIs (and prevent clunky PDF or excel downloads) to ensure software can directly consume the information. This greatly enhances the speed of service delivery and the competition across sector specific market players.

Key examples of building blocks in this category of DPIs include:

  • Authentication (Mobile, Offline QR Code based, Biometric, Face, etc)

  • eKYC

  • Single Sign On

  • Civil/Functional Registries

  • Entity Registries

  • Object Registries (land,etc.)

PreviousDPI and the Digital DivideNextDigital ID

Last updated 11 months ago

🆔