WalliD
  • Overview
  • CertiShop WebApp
    • Getting Started
    • Manage Organization
    • Create a Certificate Template
    • Issue Certificates
    • Receiving Certificates
    • Verifying Certificates
  • CertiShop SDK
    • Intro
    • Authentication
    • Making Requests
  • CertiShop On Prem
    • Intro
    • Webhooks
    • Client-gateway
    • Datalayer
    • Deployment
  • Architecture
    • Overview
    • Certificate Protocols
    • Wallets
    • Databases
    • Verification
  • API Reference
  • Glossary
  • Privacy Policy
Powered by GitBook
On this page
  1. Architecture

Overview

PreviousDeploymentNextCertificate Protocols

Last updated 3 months ago

CertiShop's backend architecture is built to simplify the complexities of creating a Certificate Authority (CA) issuing and verifying digital certificates while ensuring compliance with global standards like. At its core, the CertiShop backend abstracts the intricacies of (DID) protocols, , and Verifiable Credentials (VC), providing organizations with a streamlined, frictionless experience.

The architecture of WalliD CertiShop connects frontend components (webapp and SDK) to a robust backend API that integrates multiple VC protocols, wallet solutions, and databases.

  1. Frontend Components:

    • Webapp: A no-code platform allowing users to:

      • Set up a Certificate Authority (CA).

      • Manage users and API keys.

      • Create certificate templates, schemas, and designs.

      • Issue certificates manually or in bulk.

      • Revoke and manage certificates.

    • SDK: Libraries enabling developers to:

      • Interact with CertiShop APIs programmatically.

      • Create CAs, templates, and certificates.

      • Perform certificate issuance and verification.

  2. API The API serves as the central hub for:

    • Authentication of users.

    • Managing CAs and templates.

    • Issuing and verifying VCs.

    • Supporting multiple VC protocols (OID4VC, mDL, PDA-1).

  3. Databases store certificate's data and are queried by verification proccesses.

    • Cloud Database: Default storage managed by WalliD.

    • On-Premise Database: Optional implementation for clients to store data privately.

  4. Verification

    • Verification occurs via a website (Accessed through a QR displayed on the certificate), hosted by WalliD or configured by the client. Offline verification is supported using electronic signatures embedded in PDFs, ensuring authenticity.

eIDAS
Decentralized Identity
digital wallets