# Verifiable Credentials **πŸ“œ Verifiable Credentials – Trust That Travels With You** Verifiable Credentials (VCs) are digitally signed statements issued by trusted entities that allow individuals and organizations to **prove claims about their identity, skills, or qualifications** without revealing unnecessary personal information. VCs provide a **tamper-proof, cryptographically secure** method of verifying information across different platforms and jurisdictions.

Fairway Professional Credentials

#### **How Verifiable Credentials Work** 1. **Issuance** – A trusted entity (Issuer) digitally signs and issues a credential to a user’s digital wallet. 2. **Storage** – The user (Holder) securely stores the credential in their self-sovereign identity (SSI) wallet. 3. **Verification** – A verifier (Employer, Bank, Government) requests proof of specific information, and the user shares only the required details. #### **Key Features of VCs:** * **Privacy-Preserving** – Users can share minimal data through **Selective Disclosure**. * **Interoperable** – Adheres to **W3C Verifiable Credentials Standard**, ensuring compatibility across platforms. * **Tamper-Proof** – Cryptographic signatures prevent credential forgery or alteration. * **Cross-Border Trust** – Supported by frameworks like **EUDI, eIDAS 2.0, and EBSI**. πŸ”— **Sources:** * W3C Verifiable Credentials Data Model: * European Blockchain Services Infrastructure (EBSI): --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fairway.global/learn/introduction-to-digital-identity-and-verifiable-credentials/verifiable-credentials.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.