Issuing Certificates

Filling Placeholders with Unique Data

In the backend, CertiShop fills in the attributes and placeholders defined in the certificate template with the unique attestations corresponding to the recipient. These attestations contain specific details about the recipient of the certificate, such as their name, course completed, or certificate ID.

• When issuing certificates via the webApp, users directly input the required recipient data, which is automatically mapped to the appropriate placeholders.

• When issuing certificates via the SDK, organizations send an issue request containing the dynamic data for each certificate, which is then processed by our backend.

---

Issuing the Certificate via Walt-ID / OpenID4VC

CertiShop issues certificates by leveraging Walt-ID and the OpenID4VC/jwt/issue flow. Here’s how the process works:

1. Credential Offer Generation: Upon issuance, CertiShop generates a credential offer, which includes a unique claim URL and QR code.

2. Sending the Credential Offer: The recipient receives the claim URL and QR code via email. These links allow the recipient to claim the certificate securely.

---

Storing in Digital Wallets

The issued certificate can be stored in any EU-compliant digital wallet. Once the recipient receives the credential offer via email:

• They can scan the QR code or click the claim URL to retrieve the certificate.

• The certificate can then be securely stored in their digital wallet, ensuring that they maintain control over their verifiable credential, while also providing easy access for verification when needed.