Issue digital IDs from the ID documents your users already carry.

Issue, store and manage all digital IDs from a single platform

Supports all ID formats
Store digital ID in phone
Offline verification of digital ID

Book a demo

Built on global standards for digital IDs

Standards and bodies IwC is built on: ISO 18013-5, AAMVA, OpenID, IETF, W3C, and the EU Digital Identity Wallet

How a digital ID gets issued

Private keys never leave the HSM

Apply

The person submits their documents and passes a liveness check.

Approve

Your reviewer checks the application against the records you already hold.

Create

We sign the credential with your issuer key, inside your HSM.

Hold

The digital ID lands in the holder's wallet over OpenID4VCI.

Present

The holder shows it to a spec-compliant reader, online or offline.

After issuance, you stay in control of every credential you have signed.

RenewalExtend or reissue before expiry

SuspensionSwitch the ID off temporarily

ReinstatementSwitch it back on

RevocationKill it permanently

Everything you need to power verified digital identity.

A phone showing a mobile driving licence issued by a department of transport, with the holder photo, given names, date of birth, licence number, and vehicle classes.

Everything you need to run a digital ID program

Before you issue

Identity Verification (IDV)

Applicants submit their ID and a selfie from any mobile device. Six algorithmic checks are performed on the data submitted & reach your issuing organization as a single decision-ready case (Approve / Reject).

~ Takes 1-2 minutes per verification
Supports ID documents from 200+ countries

Explore Identity Verification (IDV)

The IDV process flow. A digital ID application from an app or browser uploads ID documents and a selfie for biometrics. The application is sent to a review centre, which runs six checks - OCR, biometric match, liveness match, document authentication, a system-of-record check, and a fraud check - then approves or rejects it. Approval creates verified identity data from the document and biometric information the user supplied, which can then be used to issue a digital ID. — The IDV process, from application to verified identity data

For holders

Digital ID Wallet SDK

Holders enrol, hold, and present digital IDs from a mobile wallet. Ship it as a white-label app in your own brand, or drop the SDK into an app you already publish - you do not have to start a new app project.

Digital ID is stored inside secure storage element on your mobile
Available in both iOS and Android
IDV is integrated into the enrolment workflow

Explore Wallet SDK

Three wallet screens: a digital ID under review, the same credential verified with a Present in Person action, and a Scan to Verify QR code waiting for a reader. — Digital ID wallet & sharing the credential using QR code

For issuing authorities

Issue a Verified Digital ID

We sign verified data with your issuer key and deliver the digital ID straight to the holder's wallet. Your system of record stays where it is - IwC reads from it rather than replacing it.

IwC will sign the issuer's signature on the credential
HSM-backed credential signing on the digital ID
Digital ID delivered over OpenID4VCI protocol

Explore Issuance with Credence (IwC)

A phone presenting a digital ID at the centre, with government use cases above - Department of Revenue, Social Services, Labor & Workforce, Department of Motor Vehicles, State Treasurer, Licensing & Regulation, Health & Human Services - and commercial use cases below: Financial Services, Travel, Hospitality, Age-Restricted Products, Large Events, Contactless Pickup, and Healthcare. — Various use cases of digital IDs

The digital identity infrastructure behind national-scale programmes

Why choose Credence ID?

Four things that stay true whichever programme you run, and whoever you run it with next.

One verified identity, generated once, fanning out into three credential formats - ISO mDL/mdoc, SD-JWT VC and W3C VC 2.0 - which all converge again into a single wallet, SDK or app.

From one verified identity record, issue multiple credential formats

After generating a verified ID once, you can issue credentials of multiple formats into the same wallet SDK / app configured.

A key generated inside your HSM. The signature travels out to the application, which receives it; a second path for the private key is dashed and crossed out, marked "private key never leaves".

Keys that never leave your HSM

Issuer keys are generated inside your HSM and stay there. Signing happens in hardware, which means the private key never reaches the application.

A credential whose claims - name, date of birth, over 18 - are each hashed separately. Asked "Age over 18?", only the "Over 18" claim is released and the answer is yes; no date of birth is handed over.

Selective disclosure

Each claim is hashed on its own, so a holder answers the question asked and nothing more. Is Age over 18? Yes - without handing over a date of birth.

Published specs producing a credential in your format rather than ours, read by any compliant wallet and any compliant reader. Walk away tomorrow and everything already issued keeps working.

No vendor lock-in, by design

These are published specs, not our specs. Any compliant wallet or reader works with the credentials you issue, and if you walk away tomorrow, everything you've already issued keeps working as it is.

Published standards, not our own format

Every credential we issue follows a published spec, so you are never tied to our stack. Here is what we support today.

Credential formats

ISO mDL/mdoc
SD-JWT VC

Protocols

OpenID4VCI
OpenID4VP

Cryptography

ECDSA P-256/384/521
Per-claim SHA-256 hashing
PKCS#11 to the HSM

New to digital identity?

The four stages of every credential, and the standards behind them. In plain language.

Read Digital ID 101

Enrolment

The applicant proves who they are

Issuance

The authority signs the credential

Storage

The credential lives on the holder's phone

Presentation

A reader checks the signature

A unified identity experience, without rebuilding your stack

IwC reads from the system of record you already run and signs with keys that never leave your HSM. The credentials it issues follow published specs, so they keep working in wallets and readers we do not control.

Book a demo