O04 - Wallet Interoperability

Sequence	Objective Detail	Test Procedure
O04	Confirm that the Innovation is interoperable with multiple wallet applications.	Assert that there is no technical limitation (theoretical verification) for other wallets to store the digital credential (i.e. it is decentralized) Assert that others wallet applications are able to store the credentials generated by the Innovation.

Assumptions & Acceptance Criteria

The issuer asserts that there is no technical limitation imposed by the innovation that would prevent other wallets from storing its credential
The issuer acknowledges that other wallets must provide some sort of mechanism to store the issuer's credentials in order to be considered interoperable
The issuer issues valid Verifiable Credentials that conform to the W3C Verifiable Credential Data Model v1.1

info

Native wallet application functionality with Apple Wallet is currently being implemented and are not yet ready for testing`.

Open the Blueprint wallet application on your android device
If there is no credential in the wallet, add one automatically via OIDC login or manually via QR code
Select a credential to view the its expanded detail view
Select the "Add to Gooogle Wallet" button to preview the credential in the Google Wallet application
Select "Add to wallet" to confirm the addition of the credential to the Google Wallet application
Open the Google Wallet application and confirm that the credential is present

info

We are currently investigating the following wallets applications for Interoperability:

The mechanism for adding a Verifiable Credential to the wallet uses a QR code, however the code appears to be a URL to the issuer to request credentials instead of a raw VC payload
There is no mechanism for storing a raw VC payload directly in the wallet
Assertion: there appears to be no technical limitation to integrate with BC wallet for the storage of Blueprint issued credentials, however, additional validation is required to determine if our issuer is compatible

The wallet application offers a scan QR mechanism for adding credentials and does not discriminate on any dimensions
No processing of the QR payload is performed by the wallet application, the scanned QR is simply saved and displayed in the wallet
Assertion: there appears to be no technical limitation to integrate with Lissi for the storage of Blueprint issued credentials, however there is also no additional value provided in this Interoperability

The mechanism for adding a Verifiable Credential to the wallet uses a QR code, however the code appears to be a URL to the issuer to request credentials instead of a VC payload
There is no mechanism for storing a raw VC payload directly in the wallet
Assertion: there appears to be no technical limitation to integrate with Learner Credential Wallet for the storage of Blueprint issued credentials, however, additional validation is required to determine if our issuer is compatible

The mechanism for adding a Verifiable Credential to the wallet uses a QR code, however the code appears to be a URL to the issuer to request credentials instead of a VC payload
There is no mechanism for storing a raw VC payload directly in the wallet
Assertion: there appears to be no technical limitation to integrate with estatus Wallet for the storage of Blueprint issued credentials, however, additional validation is required to determine if our issuer is compatible

The mechanism for adding a Verifiable Credential to the wallet starts with uploading a physical credential
There is no mechanism for storing a raw VC payload directly in the wallet
Assertion: a technical limitation exists on the Trinsic wallet in that there is no mechanism for adding verifiable credentials outside of their first party flow