Verifiable Credentials is the standard (from W3C) to represent credentials in the digital world. It can be used to build digital ID cards, academic diplomas, membership passes, and any kind of credential or proof of achievement you may want to attach to a subject.

Credentials created with this standard are (1) globally interoperable, (2) un-fakeable, (3) can be used for digital native use cases, such as credentialing AI agents or as conditions in smart contracts.

But integrating Verifiable Credentials in your app can be tedious. You must implement issuance in a cryptographically correct way. Then figure out a way to store and distribute credentials to your users. Maintain a revocation server. Finally, you need to provide instructions or SDKs to all parties who want to verify them. And re-do all of this if you want your credentials to work on-chain inside smart contracts.

Crossmint allows you to issue, store, distribute, present and verify VCs, all in under 5 lines of code, with an implementation that is 100% standards compliant and interoperable, and works both off and on-chain.

Verifiable Credentials is currently in Beta. It can only be accessed through the Staging console.

Key Characteristics

Global interoperability

Emit credentials that anyone in the world can verify. They work off and on-chain.

Zero Knowledge

Credentials are confidential by default. Users can choose who to share them with.

Easy to use

Issue, present, verify… all in a handful of lines of code.

How Does it Work?

Crossmint’s Verifiable Credentials SDK helps in all 4 components of the lifecycle of a credential:

  1. Issuance: define the schema for your credentials, and then issue credentials to users, identified by emails, phone numbers, crypto wallet addresses, or your custom user id. You can also revoke credentials.

  2. Storage: Crossmint can store all credentials for you in centralized storage, or can end to end encrypt and store them in a decentralized permanent storage network.

  3. Presentation: easily retrieve all the credentials of a user filtering only the ones you are interested in. Works with any wallet that supports the wallet connect interface.

  4. Verification: cryptographically validate that a credential you have been presented is valid. Use it to authorize users against your system.

Typically, issuance and storage are performed by one party, presentation and verification by another.

Get Started

FAQs