> For the complete documentation index, see [llms.txt](https://docs.wallid.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wallid.io/architecture/overview.md).

# Overview

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[ eIDAS](/glossary.md#eidas-electronic-identification-authentication-and-trust-services). At its core, the CertiShop backend abstracts the intricacies of [**Decentralized Identity** ](/glossary.md#did-protocol-decentralized-identifier-protocol)**(DID) protocols,** [**digital wallets**](/glossary.md#id-wallets), 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. 

<figure><img src="/files/3Q3blOX7Kzw7BXgmVLue" alt=""><figcaption></figcaption></figure>

1. **Frontend Components:**<br>
   * **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.<br>
   * **SDK**: Libraries enabling developers to:
     * Interact with CertiShop APIs programmatically.
     * Create CAs, templates, and certificates.
     * Perform certificate issuance and verification.<br>
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).<br>
3. **Databases** store certificate's data and are queried by verification proccesses.&#x20;
   * **Cloud Database**: Default storage managed by WalliD.
   * **On-Premise Database**: Optional implementation for clients to store data privately.<br>
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.