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

Figure 11: User e-KYC using ADIA to lookup DAP-managed Verifiable Credentials

routed to the Digital Address Provider that provides payments via 3rd party market makers (which can
the user's Credential wallet. The user will receive a provide liquidity among token types) enables a truly
notification via their smart device asking for their agnostic inter-ledger ecosystem where the whole is
consent to provide the identity attributes required by greater than the sum of the member parts.
the Service Provider. When the user grants consent By not relying on device-based credentials, cer-
and verifies themselves locally on their device using tain other challenges (e.g., multiple device support)
FIDO authentication, the successful verification will are also alleviated. Wallets may be designed to con-
trigger the DAP process to route the Issued VCs back trol cloud-based credential metadata which is cre-
to the Service Provider. ated from actual issuer data and controlled by the
user via interactions with strong authentication (e.g.,
6.3.2 Remote e-KYC (online sign-up for website FIDO).
or app)
The system works the same but instead of the user 6.4.1 ADIA interoperability with FIDO
presenting identity data in person for a Service ADIA uses FIDO authentication at the application
Provider to input into their terminal, the user self-in- layer to ensure that the task of accessing verifiable
puts identity data to be verified along with their Digi- credentials is protected through secure authentica-
tal Address. tion. Any FIDO protocol can be used to secure the
The level of assurance of the identity of the user is access to the ADIA application wallet. Interoperabil-
the same remotely as it is in person since the assur- ity is ensured at the authentication layer by ensuring
ance of the original Digital Address is secured with a the usage of FIDO certified products.
FIDO registration at the time of Issue.
6.4.2 QR code security
6�4 ADIA wallet interoperability QR code passwordless authentication methods are
As mentioned above, there are numerous ledger- vulnerable to man in the middle attacks. In OASIS
based DID-focused identity platform initiatives there is a working that is focused on securing the
underway. What separates the ADIA project of DID usage of QR code in passwordless authentication
Alliance is a focus on true ledger interoperability. By methods.
leveraging existing communications protocols (like
the Hyperledger Aries project and DIDCOM by the 6�5 Standardization
DIF for identity flows along with a smart contract The standardization work of the DID Alliance is not
layer for business flows) ADIA will extend those focused on developing new protocols, but rather
protocols to truly operate among disparate ledger standardizing the interoperability of existing proto-
systems, rather than different instances of the same cols. Additionally, it will focus on publishing common
ledger technology. This coupling of cross-ledger schema for identity and credentials used within
communication with a way to settle cross-ledger

e-KYC use cases in digital financial services 27