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

• Trust sourcing a) URL scheme identifier (did)
b) Identifier (proposed) for the DID method (ADIA)
ADIA relies on trusted sources to bootstrap the digi- c) DID method-specific identifier (this would be
tal identity of individuals. ADIA work is based on proprietary to ADIA and would involve the DID
ITU-T Recommendation X.1254, whereby an identity Alliance's patent-pending "Identity Disambigua-
vetting assurance level during the process of validat- tion" process).
ing an individual before a digital address is assigned
to them. Identity resolutions process are incorporat- 6.1.2 Digital Address Issuance
ed to ensure the uniqueness of the individual with There are two types of Issuers in the ADIA ecosystem:
domains. Verifiable Credentials Issuers and Digital Address
Issuers. As the latter, an Issuer is capable of identi-
• Cross-ledger transaction support ty verification to meet regulatory KYC requirements.
Verifiable Credential Issuers leverage the KYC capa-
ADIA works with the assumption that identity infor- bility of Digital Addresses to append other identity
mation for the individual is stored in a cloud environ- claims as Verifiable Credentials.
ment with the binding to a specific digital wallet and The Digital Address is a special ADIA identifier
a specific ledger. ADIA uses cloud based techniques that is issued to an individual by a certified Digital
to ensure that any application can integrate with the Address Issuer after in-person KYC has been done.
available claims for a given individual with interoper- Candidates for such certification could be enti-
ability ensured by using standard based cloud proto- ties such as banks who have established in-person
cols. accounts, certain government agencies, insurers, etc.
By using a specialized biometric sensor, the Issuer
• Inclusiveness will combine a biometric characteristic from the indi-
vidual user, combine it with certain other identity-re-
ADIA is an open platform, there is no royalties or lated traits (such as first name, last name, date of
rules that prevent any participant from belonging birth, city of birth, etc.) and after applying a hashing
and contributing to the system algorithm, derive a Digital Address in cooperation
The DID Alliance seeks to fulfil the promise of with a participating Digital Address Provider (DAP).
DID systems by helping to solve some of the most Digital Address Providers are solution providers who
important practical problems attached to their oper- are currently providing DID-related identity services.
ation and adoption by enabling a business interoper- The Digital Address may be delivered to a FIDO-se-
ability layer as well as a technological one. cured Credential Wallet on the user's smartphone (or
other embodiments) as well as could be presented
6�1 How ADIA works? as a card secured by a user-defined PIN. In both cas-
When the ADIA system is implemented, it will enable es, the Digital Address is strongly bound to the indi-
easy e-KYC for online and offline service providers vidual user by the combination of identity attributes
by leveraging the universe of connected DID identity and biometric measurement taken from that user.
platforms that will interoperate and allow user iden- The Digital Address Issuer has access to a limited
tification via a Digital Address. number of APIs (Create Digital Address, Publish to
Digital Address, and Update Digital Address – which
6.1.1 Digital Address Format can be used for credential revocation when neces-
The plan is for a ADIA Digital Address to comply with sary.)
the W3C standard format for DIDs.
For ADIA, the proposed format is: 6.1.3 ADIA layered model
The ADIA layered model focus on separating the
did: adia: 1234567ABCDEFGHI identity-based services at the business layer from
the network security and data layer (See Figure 10).
This address would comply with the W3C stan- The objective here is to have a trusted identity layer
dard and would be resolvable using the Universal that enable business logic while protected by a data
Resolver project that is proposed by DIF. security layer.
It is comprised of the standard components of a
DID:

e-KYC use cases in digital financial services 25