By publishing qualifying services and workflows in an Ocean Protocol powered Marketplace, we can hook up a Vue.js data wallet by means of a simple QR-code-service as glue for data transfer of DIDs and webtokens in order to preserve privacy and use service endpoints according to Ocean OEP 8 metadata to disclose and verify information and issue verifiable credentials as well. Every piece of data in the wallet or an asset in the marketplace is modeled after a credential, published as a DDO (data asset) in the marketplace. We first publish a base credential DDO like some university degree format description using schema.org in the Ocean marketplace, issued by a public organization, as a template from which we instantiate –issue– timestamped credential objects to a client. This event will be published as a DDO of a Verifiable Credential according to the W3C standard, using OEP 8 service endpoints as a means to interact with this asset, like authenticate, read the accompanying data and verify. If service endpoints link to public documents, like in the case of the base credential DDO, we use IPFS to download files, lifting the burden of managing storage facilities. When service endpoints link to private or verifiable data, like in the case of a verifiable credential DDO, we use authentication services and separate DLT to get to the data.