Page 26 - FIGI: e-KYC use cases in digital financial services

in the open source Hyperledger Project. Especially tems – whether national ID systems, functional
relevant sub-projects within Hyperledger are IDs, or social protection eligibility lists – it can be
deployed without interruption to existing public
a) Hyperledger Indy: tools, libraries, and reusable or private sector programs.
components for providing digital identities root- d) Resilience� The open-source nature of Kiva Pro-
ed on blockchains so that they are interoperable tocol makes it resilient in that no external party
across administrative domains, applications, and can revoke the ability to use the system. In addi-
any other silo. tion to removing vendor lock, even if all external
b) Hyperledger Aries: a shared, reusable, interop- access to the system were cut off, local operators
erable tool kit designed for solutions focused would be able to provide a then-current copy of
on creating, transmitting, and storing verifiable the ledger data, and clients would be able to
digital Credentials in blockchain-rooted peer-to- continue with new local-only transactions until a
peer interactions. time when updates can be merged back into the
c) Hyperledger Ursa: a shared cryptographic library national system.
to avoid duplicating other cryptographic work
and increasing system security.
d) Hyperledger Identity Working Group: discus- 5�3 Implementation Status
sion, research, and documentation of methods With the digital wallet infrastructure in place, Kiva
to capture, store, transmit, and use identities in began supporting individual FSP API integrations
blockchain, specifically for projects within Hyper- into the NDIP in early 2020. When complete, this
ledger. integration work will enable citizens to share veri-
fiable credentials from their digital wallet directly
To maintain compatibility across independent into the core banking systems of FSP verifiers. Given
implementations, the Hyperledger community main- the technical capacity constraints across the sector
tains a directory of ratified message types and proto- – particularly in Sierra Leone's remote provinces –
cols that are generally accepted as necessary, should Kiva's in-country teams worked intensively with early
the software in question support the functionality. FSP pilot partners to ensure that the NDIP-based
The current state of interoperability can be found in identity verification integrated seamlessly into exist-
the Aries-RFC directory, and is described in the Aries ing workflows and customer onboarding processes.
Interoperability Profile RFC.
A strong advantage of this type of standardized
identity protocol derives from the interoperability, 6 INTRODUCTION TO ADIA FOR DID IDEN-
efficiency, and network effects that can be achieved TITY SYSTEMS
by working together:
The Accountable Digital Identity Association (ADIA)
a) No vendor lock-in� Because Kiva Protocol is is a technology specification from DID Alliance
open-source software, the implementing entity (DIDA). The Decentralized Identity (DID) Alliance is
(typically a government agency or public-private an open industry association created to drive the
partnership) is not reliant on a single vendor to development of a standardized, interoperable frame-
maintain or modify the system. work for decentralized identity services to ensure the
b) Standards� Technical standards and terminology authenticity of and establish trust in digital identities.
are shared across the open-source community. The group will contribute to the creation of a global
This greatly simplifies integrating Kiva Protocol ecosystem, the formation and operation of a collab-
into existing or new systems for governments, orative network, the diffusion of standardized tech-
FSPs, and other authorized entities. nologies and the development of the decentralized
c) Interoperability and Extensibility� Enabling Kiva identity industry
Protocol to extend beyond e-KYC verification ADIA's purpose is to achieve true interoperabili-
is possible if desired. Adding adjacent services ty among decentralized identity (DID) systems by
such as business entity registration, digital driv- deploying requisite technologies and processes that
er's licenses, digital voter identity, portable health are outside the scope of existing interoperability
data, and verifiable education records are just a efforts such as W3C, DIF, and Hyperledger Aries. In
few examples. Moreover, because Kiva Protocol pursuit of this objective, ADIA's efforts are directed
extends the functionality of existing identity sys- to three main areas:

24 e-KYC use cases in digital financial services