MyID
Enterprises, financial firms, and private services build their own identity verification, on-premise or as SaaS.
Blockchain keeps trust intact while cutting identity-verification steps, and users manage their own data. Backed by proven deployments and security, from on-premise builds to public-sector SaaS.
One DID platform in two tracks, by who adopts it.
The private sector uses MyID; public institutions use MyID 2.0 on shared K-BTF infrastructure.
Enterprises, financial firms, and private services build their own identity verification, on-premise or as SaaS.
The first CSAP-certified blockchain SaaS, running on K-BTF shared infrastructure from the Ministry of Science and ICT and KISA. No separate build required.
MyID is a blockchain-based DID platform. Credentials (VCs) live in the user's wallet, only what is required is submitted, and issuance, verification, and integration run on W3C standards. The four components below plug into your service.
All three parties register their DID on MyID,
with integrity verified on-chain
An admin console for creating DIDs and VCs and setting verification criteria without code. Issuance history and the authentication flow are managed in one dashboard.
An identity wallet where users manage their own DID and VCs. The Wallet SDK adds wallet features to your app, and externally issued VCs can be stored too.
Everything identity verification needs as APIs: DID management, VC issuance and validation, and VP verification. One API across multiple blockchains, with external VC linking.
The public and private blockchain environments MyID needs, delivered as a service. Built on loopchain core2 for stable DID operation.
Changing data stays under your control in a Personal Data Store (PDS). Large files such as documents and images are stored without loss in a Blockchain File System (BFS) replicated across nodes.
Proves a fact, such as "is an adult" or "holds a qualification", without revealing the underlying data. Supports range and membership proofs.
Submits only the requested fields, not the whole credential. Nothing unnecessary is disclosed.
Hides which institution issued the credential during verification, so issuance history is not exposed.