Question 1

What is iDen2?

Accepted Answer

iDen2 is access infrastructure. We help institutions let the right people through at the moment they need a service, using just enough proof instead of collecting and re-checking everything about a person.

Question 2

What do you mean by "access, not identity"?

Accepted Answer

When identity works it disappears, and when it fails access breaks down. Most systems do not fail for lack of data, they fail because someone cannot get to a service in time. We start from the access moment and work backwards to the minimum proof that moment needs.

Question 3

Why do existing identity systems fall short?

Accepted Answer

They assume stable lives, fixed attributes and a single institution holding the record. That leads to over-collecting, over-checking and slowing everything down, until risk management turns into exclusion by process.

Question 4

Is iDen2 a wallet, an IAM platform or a digital ID replacement?

Accepted Answer

No. iDen2 is not a wallet vendor, an IAM platform, a national ID replacement or a trust broker you have to switch to. It is complementary access infrastructure that works alongside the public and private systems already in place.

Question 5

Who is iDen2 for?

Accepted Answer

Institutions that need to admit people to a service: banks, insurers, telcos, healthcare, higher education, government and social programs, employers, travel and hospitality, retail and loyalty, supply chain, energy and NGOs.

Question 6

What are the main parts of the platform?

Accepted Answer

Credential Factory for issuing, Trust Engine for verification, the Trust Network for governance, the wallet and its SDK for the person, and the credential registry underneath. Each part can be adopted on its own.

Question 7

What is the Trust Network layer?

Accepted Answer

It aggregates signals such as issuance quality, verification behavior, revocation patterns and operational consistency, so access can flow without every party defaulting to over-verification.

Question 8

Do we have to replace our current systems?

Accepted Answer

No. The modules sit alongside what you already run, so there is no rip and replace. You can start with a single flow and extend from there.

Question 9

Can we use our own wallet or an existing credential ecosystem?

Accepted Answer

Yes. You can use the iDen2 wallet and SDK, or connect third-party wallet and credential ecosystems and use the Trust Network layer across them.

Question 10

What happens if someone loses their phone or their credentials?

Accepted Answer

Proof is designed to be recoverable and portable. A person can restore access without starting the whole onboarding journey again.

Question 11

What is a digital identity?

Accepted Answer

A digital identity is any electronic representation of a person, organization or device inside a digital system. It is an umbrella term: it covers everything from a low assurance social media profile to a high assurance government issued credential, whatever the underlying technology.

Question 12

What is a mobile identity?

Accepted Answer

A mobile identity is any credential designed to be stored, managed and presented on a phone, using capabilities such as NFC, Bluetooth, QR codes and biometrics. It describes the delivery mechanism and the experience, not the data format. Examples include mobile driver's licenses, employee badges and student IDs held in a wallet.

Question 13

What is a verified identity?

Accepted Answer

A verified identity is a digital identity whose attributes have been checked and cryptographically certified by a trusted authority. It speaks to the level of assurance behind the data, not to the format it is expressed in.

Question 14

What is an ISO 18013-5 mDoc or mDL?

Accepted Answer

ISO 18013-5 is an international standard for holding and presenting official identity documents on a smartphone. Its best known implementation is the mobile driver's license, and mDocs are cryptographically bound to the device they are issued to.

Question 15

What is a W3C Verifiable Credential?

Accepted Answer

A Verifiable Credential is a digital version of any credential, such as a diploma, license or certificate, cryptographically signed so it can be shown to be authentic and untampered. It follows a W3C web standard so different systems can work together, and it may be bound to the device it was issued to.

Question 16

What is SD-JWT VC and selective disclosure?

Accepted Answer

SD-JWT is a privacy focused format that lets a person share only chosen pieces of a credential with each verifier. SD-JWT VC applies that selective disclosure to verifiable credentials, so a presentation can prove a fact without revealing everything behind it.

Question 17

Is a mobile ID the same as a particular format?

Accepted Answer

No. Identity characteristics such as mobile or verified are a separate dimension from representation formats such as mDoc, W3C VC or SD-JWT VC. A mobile driver's license can be implemented in any of those formats, and verification integrity holds across all of them.

Question 18

Which formats does iDen2 support?

Accepted Answer

iDen2 can issue the same verified credential as an mDoc, a W3C Verifiable Credential or an SD-JWT VC, so you can pick the format that fits your regulatory and technical needs. Verification is format agnostic: it validates cryptographic integrity and issuer authority, so new formats can be added without changing the core verification process.

Question 19

Is a mobile version of a national ID a digital ID?

Accepted Answer

Not on its own. A mobile national ID mirrors the physical card on a phone and is mainly for visual checks. A digital ID adds secure authentication, consent based data sharing and electronic signatures, and can be reused across many services. Having a digital copy of your ID is not the same as having a digital ID.

Question 20

How much personal data does a verifier see?

Accepted Answer

Only what the specific decision requires. Credentials are presented with the person's consent, so a verifier can confirm a fact without receiving the underlying documents behind it.

Question 21

Who controls the person's credentials?

Accepted Answer

The person does. Issuers verify facts, the wallet holds them, and relying parties accept them when the holder chooses to present them.

Question 22

We already have an identity system (AD / Okta / Ping).

Accepted Answer

Our Protocol Bridge sits on top of your existing stack. We don't replace Okta, we add the layer it can't: portable credentials, cross institution reuse, AI agent governance, and standards compliance.

Question 23

Decentralized identity is still emerging, we'll wait.

Accepted Answer

The standards are done. What's forming is the market, and organizations that move first will own the distribution advantage for a decade. The question isn't whether this happens. It's whether you lead or follow.

Question 24

How does APoC actually work in practice?

Accepted Answer

Every agent gets a Delegation Credential, like a power of attorney, but cryptographic. It specifies exactly what the agent can do, on whose behalf, and until when. Every action generates a signed receipt. Your legal team can answer any regulatory question in seconds.

Question 25

What's the ROI, prove it before we commit.

Accepted Answer

Give me three numbers: how many identity checks you run per year, your average customer revenue, and your current onboarding abandonment rate. In five minutes I'll show you a conservative model with your exact parameters.

Question 26

Is this GDPR compliant? What data do you hold?

Accepted Answer

With iDen2, you're not holding their data, they are. Your GDPR exposure drops to near zero on identity data because you never collected it. That changes your DPA conversations, breach liability, and audit profile overnight.

Question 27

Can credentials be stolen or spoofed?

Accepted Answer

Holdr credentials are bound to the holder's device key and biometric. A stolen wallet is like a stolen key that only works if you're the person who enrolled it. We're also post quantum, CRYSTALS Dilithium signatures hold through the next decade of threat evolution.

Question 28

What's the implementation timeline?

Accepted Answer

A proof of concept is 2 to 4 weeks. First production credential issuance is 6 to 8 weeks. Your team's job is configuration, not construction, we bring the complexity.

Question 29

We're not deploying AI agents yet, APoC isn't relevant.

Accepted Answer

Most clients start with human identity and activate APoC when they're ready. You don't pay for agent governance until you need it, but when you do, it's already built and tested. Starting governance after agents are running is always harder and more expensive.

Question 30

Your competitor X has more market presence.

Accepted Answer

Point solutions and platforms are different things. [Competitor] does [biometrics/signing/auth] well, but they cannot issue W3C VC 2.0 credentials, govern AI agents, or enable cross border portability. That's not a product gap, it's an architectural difference.

Question 31

What happens if iDen2 shuts down? Are we locked in?

Accepted Answer

Because we build on open W3C, ISO, and IETF standards, your credentials and platform logic are exportable. The credentials your customers hold in their wallets work with any W3C compliant verifier, forever, regardless of issuer. Open standards are the exit strategy from lock in.

Question 32

How does an engagement usually start?

Accepted Answer

With one access moment that hurts today: onboarding, re-verification, a support flow or a partner handoff. We map that flow, agree the minimum proof it needs and put the relevant modules behind it.

Question 33

How do I get the industry briefs and other material?

Accepted Answer

Everything in the resources library and the industry briefs is unlocked with one short form and an emailed sign-in link. There is no second form for each asset.

Question 34

How do I get in touch?

Accepted Answer

Use the contact form and the message reaches our team directly, or reply to any email you receive from us.

Frequently asked questions

About iDen2

Platform and technology

Terminology and standards

Privacy and data

Objections

Working with us

Still have a question?