SECTION I. Introduction

This section provides an overview of why identification matters for development and an introduction to core identity-related concepts, including the lifecycle of creating and managing identities, types of ID systems, and the main stakeholders and roles involved in creating, managing, and overseeing ID systems. Finally, it concludes with a framework for assessing the development of an ID system and determining what types of investments to focus on.

ID 101: Basic concepts

“Identity” and “identification” can mean different things in different contexts. For the purposes of this Guide—and the ID4D agenda more broadly—identity refers to the characteristics or attributes that make a person unique. Common identity attributes used for official purposes typically include basic biographic data (e.g., name, age, address) and/or biometric features (e.g., a facial image, fingerprints, iris scans). Identity providers collect relevant attributes as part of registration, and then provide proof of that identity in the form of an identity document (ID) or credential (e.g., a unique number, card, digital certificate, or mobile ID) that can be used as the basis of future interactions, (i.e., to authenticate the identity of the credential holder).

As summarized in

Figure 3, ID systems help identity providers—and other entities who rely on them (“relying partners”)— answer three fundamental questions: (1) “who are you?”, (2) “are you who you claim to be?”, and “are you authorized or eligible for something?” As described in Section I, these three questions are fundamental to service delivery and the fulfillment of rights and obligations. Both public and private sector institutions need to know who people are (question 1) and be able to trust that they are “really themselves” over time (question 2) as a part of many basic social, economic, and political transactions.

Figure 3. The role of ID systems

Furthermore—after confirming that a person is who they claim to be—service providers (i.e., relying parties) often need to know or verify specific attributes of a person to determine their eligibility for accessing a right or a benefit (question 3). For example, after confirming the identity of a person using an ID card and fingerprint (authentication), a social services employee may need to then verify their income level to determine whether the person is eligible for certain benefits (authorization). For basic attributes (e.g., age), the same ID system used for authentication may be able to provide the information needed for authorization/eligibility determination. In many other cases, however, service providers will need to maintain or access additional information that is beyond the scope of the ID system itself (e.g., as in the income level example given above).