SVX Documentation
HomepageAPISDK
Current
Current
  • Docs
  • Concepts
    • Digital Identity and Why It's Important
    • Digital Wallets
    • Ecosystems
    • Information Security
    • Personal Data & Attributes
    • Privacy- and Security-by-design
    • Secure Data Storage
    • Selective Disclosure / ZKP
    • Tokens and Tokenisation
    • Verifiable Credentials
    • Terminology
  • Platform
    • Secure Value Exchange
    • Authorisation, Tenant & Organisation Manager (ATOM)
    • Credential Service
    • Decentralised Identifiers (DIDs)
    • Keys
    • Tenants, Organisations, and End-Users
    • Vault
      • Enterprise Vault
    • Portal
    • Supported Standards
  • Guides
    • Onboarding to SVX
    • API Guides
      • Credentials
        • Credential Schemas
        • Credential Types
        • Issue Credentials
        • Presentation Definitions
        • Presentations
      • DIDs
        • DID Resolver
        • DID Registrar
        • DID Methods
          • did:key
          • did:web
          • did:ebsi
          • did:indy
        • DID Controller Keypair
      • OpenID Connect
        • For Verifiable Presentation
      • Users
        • Inviting End-Users
        • Authenticating End-Users
      • Vault
        • Items and Slots
        • Connections and Sharing
        • Classification Hierarchies
        • Attachments
        • On-sharing & Client Tasks
        • Account Delegation
      • Machine-2-Machine Communication
    • Portal Tutorials
      • Tenant Administrators
        • Onboard to a Tenancy
        • Dashboard and Navigation
        • Manage Tenancy
        • Manage Tenant Administrators
        • Manage Organisations
        • Manage Organisation Administrators
        • Credential Schemas
        • Applications
        • End Users
      • Organisation Administrators
        • Manage Organisation
        • Onboarding and Organisation Setup
        • Dashboard and Navigation
        • Manage Organisation Administrators
        • Credential Templates
        • View Credentials
        • Verification Templates
        • Verification Requests
        • Connections
        • Applications
    • Wallet Tutorials
      • Wallet Set Up
      • Provider Registration
      • Organisation Configuration
      • Credentials
      • Requests
      • Security
      • Wallet Recovery
  • Tools
    • Meeco SDK & CLI
    • Cryppo SDK & CLI
  • Releases
    • 2.1.1
    • 2.1.0
    • 2.0.0
    • 1.4.3
    • 1.4.2
    • 1.4.1
    • 1.4.0
    • 1.3.8
    • 1.3.7
    • 1.3.6
    • 1.3.5
    • 1.3.4
    • 1.3.3
    • 1.3.2
    • 1.3.0
    • 1.2.5
    • 1.2.4
    • 1.2.3
    • 1.2.2
    • 1.2.1
    • 1.2.0
    • 1.1.0
    • 1.0.0
    • Legacy API-of-Me
  • Policies
    • Privacy
    • Developer Policy
Powered by GitBook
On this page
  • Prerequisites
  • Who can undertake this operation?
  • Generate Verifiable Presentation
  • Verify Verifiable Presentation

Was this helpful?

Edit on GitHub
  1. Guides
  2. API Guides
  3. Credentials

Presentations

Last updated 1 year ago

Was this helpful?

A presentation, short for , is a data model that allows a Holder of to present their VCs to a Verifier. The Verifier can then attest the authorship of the credentials included in the presentation.

The data format used for a presentation is . Other formats are not supported at this time.

Prerequisites

Who can undertake this operation?

Presentations are generated by the Holder and are verified by an Organisation (Verifier), or another user.

Generate Verifiable Presentation

Generate a verifiable presentation, ready for signing.

Endpoint

POST /presentation/generate

Request

  • DID

  • List of VCs

Response

The presentation object that includes an unsigned JWT. The client calling this endpoint (e.g. Holder wallet) is responsible for adding the signature.

Verify Verifiable Presentation

Verify a given verifiable presentation. The steps performed during verification are:

  1. Validate the presentation structure

  2. Resolve the presentation DID

  3. Verify the presentation signature

  4. For each credential in the presentation:

    • Validate the credential structure

    • Resolve the Issuer DID

    • Verify the credential signature

Endpoint

POST /presentation/verify

Request

  • Verifiable Presentation – supported format is vp-jwt

Response

The result of the verification, either true or false. In the event the response is false, all errors are provided, with an explanation.

Verifiable Presentation
Verifiable Credentials (VCs)
vp-jwt
DID
Credentials