Skip to main content

About Unum ID

Unum ID is the sharified identity™ network. Our tech allows companies to securely access and share verified identity data, with full user consent. Our core products are:

  • Beyond Passwordless™: Instant multi-factor auth, using your mobile app. No passwords or other shared secrets.
  • Verify with X™: A marketplace for verified identity data, enabling instant onboarding and more. Data recipients pay data providers for access.

Docs Overview#

These docs provide detailed, technical information about how to deploy and use Unum ID tech. We recommend starting starting with the Introduction sections, but feel free to dive into the Components sections for code level details.

Below is an annotated table of contents, which offers a sneak peek of each section.

Introduction#

  • Terminology: a few specialized terms that are helpful to know.
  • Architecture: overview of Unum ID components and how they interact with each other and our Identity Engine cloud.
  • Deployment Overview: conceptual overview of deploying all Unum ID components.
  • Privacy and Security: the unparalled benefits of our Encrypted Domain approach.

Components#

  • Server SDK: lets you act as an
    An issuer is a role a company can play to issue credentials to subjects (users). An issuer also change credential statuses, for example to revoke credentials.
    + More...
    Example: ACME Bank issues a KYC verification credential to Richard (an ACME user). It later revokes that credential and issues a new one to Richard to update his information.
    Components: An issuer issues credentials and changes credential statuses using the Server SDK.
    issuer and/or
    A verifier is a role a company can play to verify presentations shared by subjects (users). A verifier can also make requests for presentations and send them to subjects.
    + More...
    Example: Hooli FinTech sends Richard a request for (a presentation of) a KYC verification credential from ACME Bank. When Richard shares the presentation, Hooli verifies it.
    Components: A verifier requests and verifies presentations using the Server SDK.
    verifier.
  • Mobile SDK: stores
    A credential is a collection of data about a person. It's issued by a company (i.e. created and sent to a user) and stored in the company's app, on that user's device.
    + More...
    Example: ACME Bank issues a KYC verification credential to Richard (an ACME user). This includes Richard's contact information and account numbers, as well as a level of confidence in the accuracy of the data.
    Components: A company issues credentials using the Server SDK, and an app stores credentials using the Mobile SDK.
    credentials for your users and lets them share
    A presentation is a set of one or more credentials. It's shared with (or presented to) a company by a user.
    + More...
    Example: Richard shares a presentation of a KYC verification credential (which ACME Bank issued to him) with Hooli FinTech.
    Components: A user's app shares (or presents) presentations using the Mobile SDK, and a company verifies presentations using the Server SDK.
    presentations.
    • Overview: high level information about the SDK.
    • Android: for native Kotlin and Java apps.
    • iOS: for native Swift and Objective-C apps.
  • Web SDK: lets you display and send
    A request (or presentation request) is a request for a presentation. It's sent by a company to a user, who chooses whether to share a presentation in response.
    + More...
    Example: Hooli FinTech sends Richard a request for (a presentation of) a KYC verification credential from ACME Bank.
    Components: A company creates requests using the Server SDK and routes them to users using the Web SDK. A user's app responds to requests using the Mobile SDK.
    requests to users.

Demos#

Coming soon!