As a credential issuer you can use the retrieval endpoints and Crossmint will autodecrypt the credential for you. As a verifier, however, working with encryption modalities to decrypt credentials requires deep understanding of their APIs, managing cryptographic operations securely, and handling user signature interactions. The Verifiable Credentials SDK encapsulates all this functionality for verifiers, ensuring secure and seamless decryption.Documentation Index
Fetch the complete documentation index at: https://docs.crossmint.com/llms.txt
Use this file to discover all available pages before exploring further.
- Upon a verifier’s request, the SDK prompts the credential subject to sign a message proving they are the credential subject, and approving the credential’s decryption.
- Once the subject approves, Crossmint decrypts the credential for the verifier to verify.
Lit.decrypt(encryptedCredential) function.
If the credentials are encrypted using Crossmint, the SDK provides a CrossmintMetamaskDecrypt().decrypt(encryptedCredential) function that decrypts the credential, assuming the user has a Metamask wallet. For the support of additional wallets during decryption, review our SDK reference.
A Crossmint API key (credentials.decrypt) is needed when:
- Crossmint has encrypted the data (
crossmint-recoverableencryption modality) - Data is encrypted via Lit but the verifier wants to delegate Lit network billing to Crossmint

