Verifiable Credentials for Reusable Digital Identity
Issue, present, and verify W3C Verifiable Credentials in one platform. Decentralized Identifiers (DIDs), a schema registry, revocation registry, and selective disclosure built in.
Trusted by identity engineers, compliance teams, and Web3 builders across DeFi, fintech, healthcare, and enterprise.
Feature Overview
The Complete Self-Sovereign Identity Stack
Every SSI primitive in one platform from identity anchoring to cryptographic proof presentation.
Decentralized Identifiers (DID)
On-chain identity anchors self-sovereign, controller-governed, and globally resolvable.
DID Registry
Blockchain-anchored public registry create, update, deactivate, and resolve DIDs in real time.
Credential Schema Registry
On-chain schema definitions reusable across any issuer JSON-LD and Schema.org compatible.
Verifiable Credential Issuance
Issue W3C VCs to individuals, groups, or anonymous bearers with single-use variants.
Credential Revocation Registry
Revoke any credential at any time status anchored on-chain, no issuer API call required.
Verifiable Presentation
Holders compose cryptographic proofs and selectively disclose only what the verifier needs.
Multi-Signature & Cryptosuites
EdDSA, ES256K, and Secp256k1-R verified across EVM, Cosmos, and the Hypersign Network.
Developer Playground
Issue credentials, resolve DIDs, and test presentations in real time before writing a single line of production code.
Identity no one controls but you.
Decentralized Identifiers (DID)
A DID is anchored to a blockchain, not to a company's database. The controller's private key is the only authority no platform can revoke it without consent.
Hypersign implements W3C DID Core 1.0 with support for multiple verification methods, DID Threshold (M-of-N governance), DIDComm messaging, and CAIP-10 blockchain account linking across EVM and Cosmos chains.
Define the shape of every credential type.
Credential Schema Registry
Every schema is anchored on-chain with an immutable ID. Published once, referenced by any issuer so credentials across platforms conform to the same agreed structure without central coordination.
Schemas are expressed in JSON-LD with Schema.org vocabulary support. Multiple versions coexist credentials reference the exact version they were issued against.
Sign once. Trust everywhere.
Verifiable Credential Issuance
Issue W3C VCs to a single subject, a batch of holders, or an anonymous bearer all in one API call. Credentials are cryptographically signed against the issuer's DID, so any verifier can confirm authenticity without calling back to you.
Single-use credentials invalidate themselves after one successful presentation. Revocation status is anchored on-chain instant and globally queryable.
Share only what the verifier needs.
Verifiable Presentation
The holder signs a presentation with their own DID key binding the credentials to their identity. The verifier checks both the holder's signature and each credential's issuer signature, then queries revocation status on-chain.
With BBS+ selective disclosure, a holder can prove they are over 18 without revealing their birthdate or prove nationality without sharing the document number.
Every proof is verifiable at the protocol level.
Cryptographic Signature Schemes
Hypersign supports EdDSA (Ed25519), ES256K (Secp256k1), and Secp256k1 Recovery covering the full spectrum from standard W3C credentials to EVM-native wallet signatures. BBS+ provides selective disclosure without a separate ZK circuit.
Sign from any wallet. No new keys.
Verifiable Credentials Wallet Signing
Hypersign extends DID authentication to the signing conventions Web3 users already have. MetaMask signs with eth_personalSign. Keplr signs with cosmos-ADR036. Neither needs a new wallet or a new account.
This covers Ethereum, Polygon, BNB Chain, Arbitrum, Cosmos Hub, Osmosis, and every IBC-connected chain.
Integration
Three Integration Paths
From no-code to full API control. All backed by the same SSI infrastructure.
REST API
Enterprise platforms · KYC pipelines · Web3 backends
Full access to DID operations, schema registry, credential issuance, revocation, and presentation verification via a typed REST API.
- Create, update, resolve, and deactivate DIDs
- Publish schemas to the Schema Registry
- Issue, revoke, and verify credentials
- Webhook events on every lifecycle change
SDK
Product teams · JavaScript / mobile / backend
The Hypersign SSI SDK exposes the full credential lifecycle natively. Key management, DID resolution, and crypto operations are abstracted your code handles business logic.
- JavaScript (browser + Node.js)
- Built-in key management and DID resolution
- EVM and Cosmos wallet signing built in
- Real-time webhook event handling
Developer Playground
No-code testing · Integration demos · Developer onboarding
A full no-code environment inside the Hypersign Dashboard issue credentials, resolve DIDs, test presentations, and inspect raw JSON-LD before writing a single line of production code.
- Issue and verify credentials visually
- Resolve DID documents in real time
- Test EVM and Cosmos wallet signing flows
- Inspect raw JSON-LD and VP proof objects
DID creation (p99): under 2s · DID resolution (p99): under 100ms · Credential issuance (p99): under 300ms · Presentation verification (p99): under 200ms
Use Cases
Who Uses Verifiable Credentials
DeFi & Web3
Issue reusable KYC credentials verified users carry across every partner platform. MetaMask and Keplr wallets sign natively no new accounts.
Fintech & Banking
Issue cryptographically signed KYC approvals. Enable one-click onboarding across partner products no repeat verification cost.
Government & eIDAS 2.0
Issue government-grade credentials aligned with the EU Digital Identity Wallet. Citizens carry credentials accepted across all EU member states.
Healthcare
Selective disclosure lets patients share only their diagnosis code not their full medical history with any verifying provider.
Enterprise HR
Credentials revoked on-chain the moment an employee leaves. No directory sync, no manual revocation step.
Education & Credentialing
Issue verifiable degree certificates any employer can verify cryptographically without contacting the issuing institution.
More Than a Credential API
Generic JWT auth vs. Hypersign Verifiable Credentials
Generic credential storage issues JWTs. Hypersign issues W3C VCs backed by on-chain DID infrastructure and a globally queryable revocation registry.
Why Hypersign
The complete SSI stack not just an issuance API.
Most credential APIs stop at issuance. Hypersign covers the full lifecycle identity anchoring, schema definition, credential issuance, revocation, presentation, and cryptographic verification with production-grade blockchain infrastructure behind every operation.
- W3C DID Core 1.0 and VC 1.1 / 2.0 compliant
- On-chain DID Registry globally resolvable without Hypersign
- On-chain Schema Registry shared definitions across issuers
- On-chain Revocation Registry instant, queryable globally
- EdDSA, ES256K, Secp256k1-R covering every major ecosystem
- EVM wallet signing MetaMask, WalletConnect, Ledger natively
- Cosmos wallet signing Keplr, Leap, Cosmostation natively
- DID Threshold M-of-N multi-party governance
- Bearer and single-use credential variants
- BBS+ selective disclosure
- DIDComm encrypted peer-to-peer credential exchange
- CAIP-10 blockchain account linking
- eIDAS 2.0, EUDI Wallet, and EBSI aligned
- Developer Playground for no-code testing
FAQ
Everything about Verifiable Credentials
Issue credentials once.
Trust them everywhere.
Deploy the complete SSI stack DID registry, schema registry, credential issuance, revocation, and presentation in days. Talk to our team about the right setup for your use case.
Verifiable Credential API · DID Infrastructure API · SSI Platform · W3C VC Issuance Service
From the Blog
Verifiable Credentials and Zero-Knowledge Proofs, Explained
Verifiable credentials, zero-knowledge proofs, and selective disclosure get used almost interchangeably in identity marketing, but they're three different things solving three different parts of the same problem. Here's what each one actually is, how BBS+ and SD-JWT do selective disclosure differently, and why eIDAS 2.0 just made this the mandatory baseline for every EU Digital Identity Wallet.
OpenID Foundation Wants to Standardize US mDLs as Verifiable Credentials: What It Means for KYC Teams
Two new OpenID Foundation papers tackle a real gap: the US has no centralized trust framework for mobile driver's licenses, and financial institutions have no standard way to read one. Here's what the initiative actually proposes, and where a credential-based KYC architecture already lines up with it.