Credentials Factory
Creates verifiable digital IDs from any identity source, with a full audit trail.
Platform Phenix®
A network where credentials are issued once and trusted everywhere
Underneath the outcome sit five services. You rarely need all of them on day one.
The big picture
The ecosystem at a glance
Trusted issuers
- Telecom
- Verifies identity
- Manages SIM and device
- Communication channel
- Bank
- Verifies identity
- Income and address
- Ongoing monitoring
- Government
- Issues official IDs
- Verifies citizens
- Employer
- Verifies employment status
They verify facts about you.
User wallet
AI agents- Verified identityby Telecom
- KYC credentialby Bank
- Age credentialby Government
- Employment credentialby Employer
Owned by you. Portable. Private.
Relying parties
- E-commerce
- Insurance
- Fintech
- Travel
- Healthcare
- Education
- Enterprise apps
- Mobility
They accept credentials with your consent.
System view
A modular trust operating system
Trust Engine
Checks that credentials are real, current and policy compliant, in real time.
Custody Control
Consent, delegation and revocation in one place. Hosts policy governed agents.
CAPoC Engine
Proves an AI agent is authorized. Every action signed by a real person.
Protocol Bridge
Connects to existing identity platforms and all major credential formats.
Continuous Agentic Proof of Control
Authority an AI agent can prove, moment by moment
When an AI agent acts on someone's behalf, buying, transacting, filing, calling another agent, the party on the receiving end has no way to tell whether a real person stands behind it. A token proves someone once said yes. It says nothing about whether that person is still in control, or whether the agent is still the agent they approved. Continuous Agentic Proof of Control closes that gap: every time an agent acts, it presents live proof on three questions at once.
Delegation
Who authorized this agent, and for what?
The agent carries a signed chain back to the human or company that delegated to it, with the scope, the limits and the time bounds that principal actually approved, including one level of sub-delegation.
Control freshness
Is the principal still in control right now?
Authority is kept alive by a regular signal from the principal's wallet rather than assumed until a token expires. If the signal stops, or the principal withdraws it, the agent's authority stops being usable within one interval.
Agent integrity
Is this still the agent that was approved?
Each presentation attests that the agent has not been altered since it was authorized, so a swapped tool, a changed model or an injected instruction shows up as a failed check instead of passing unnoticed.
Verifiable without calling us
A relying party evaluates the whole presentation on its own, with no call back to iDen2, so checks work offline and in air-gapped environments.
Withdrawal takes effect in seconds
Stopping an agent is not a support ticket or a token revocation queue: the principal withdraws control, and authority lapses within one interval plus the freshness window they configured.
Protocola bridge
Connecting iDen2 to the systems already in place
[[NEEDS COPY: Protocola bridge: one paragraph on what it connects, why it exists and who it is for]]
What it connects
[[NEEDS COPY: Protocola bridge, what it connects: two or three sentences]]
How it is deployed
[[NEEDS COPY: Protocola bridge, how it is deployed: two or three sentences]]
What it gives you
[[NEEDS COPY: Protocola bridge, what it gives you: two or three sentences]]
Services
What each part does
Credential Factory
Issue credentials people can carry and reuse, with signing keys that never leave your control.
The Credential Factory runs credential issuance for the trust network on open standards (OID4VCI), producing SD-JWT and W3C verifiable credentials. Each issuing organization gets its own identifier and its own signing key, and those keys stay sealed in a hardware-backed vault: signing happens inside the vault, so the private key never leaves it. Every credential is registered with the Credential Registry at the moment it is issued, so status is known from day one.
- Standards-based credential offers and issuance
- SD-JWT and W3C verifiable credential formats
- One issuer, one key, one identifier, cleanly separated
- Multiple credential types per issuing organization
- Status registered with the Credential Registry at issue time
Trust Engine
Check a credential is genuine and still valid, without calling whoever issued it.
Trust Engine is the checkpoint. It opens a verification session, asks the holder's wallet for exactly the proof required for that interaction (OpenID4VP), and validates what comes back against the rules you configured, the right issuer, the right credential type, the right claims. It confirms the credential has not been revoked by reading a published status list, so the issuer is never contacted and never learns who checked.
- Verification sessions and wallet presentation flows
- Configurable rules for what proof each interaction requires
- Trust-network-aware checks on who is allowed to issue
- Live session status for the service waiting on the result
- Revocation checked against published status lists
Credential Registry
Revoke or suspend a credential, and let anyone check status without revealing who they checked.
The Credential Registry is where a credential's life is managed after it is issued: still valid, suspended, or revoked. It publishes status as a compressed public list (W3C Bitstring Status List), so a verifier answers the question locally instead of asking about one named person, nobody learns who was checked or when. Every change is recorded with a full history for audit.
- Register, update and query credential status
- Public status lists for revocation and suspension
- Full status history and audit trail
- Governed by the Trust Network at registration
- Built for high-volume checks with caching
Trust Network
Decide who is allowed to issue and verify what, across every organization in the network.
The Trust Network is the single source of truth every other service reads before it acts: which organizations are members, what each is permitted to issue or verify, and which credential types exist. Change a policy in one place and issuance, verification and the registry all follow it, no bilateral agreements, no drift between participants. Configuration updates take effect without downtime.
- Network and membership configuration in one place
- Policies governing who may issue and who may verify
- Updates applied live, with no service interruption
- Efficient distribution to every connected service
- Consumed by the Factory, the Trust Engine and the Registry
Custody Controls (Wallet)
Give people one place to hold their own identity and the identity of the agents acting for them.
Custody Controls is the holder's side of the network: a native iOS and Android app that carries two kinds of credentials that never lived together before. Human identity credentials are issued by parties the world already trusts, government ID and eIDAS attributes, KYC from a bank, professional licenses and employment, health coverage, age and loyalty status, held in the wallet and selectively disclosable so iDen2 never sees the attributes. Agents' identity credentials are issued under the person's own authority: a DID for every agent that acts for them, delegation with scope, limits and time bounds, the exact configuration they approved, and live proof that their control is still alive. The binding between the two is cryptographic and continuous, so an agent's credential stays valid only while the person's control does. Before any exchange, the wallet checks the other party against the Trust Network, so a holder is never asked for proof by an unrecognized verifier and never accepts a credential from an unrecognized issuer.
- Human identity credentials from issuers the world already trusts
- Selective disclosure, so attributes stay with the holder
- A DID for every AI agent, issued under the holder's authority
- Delegation with scope, limits and time bounds the holder approved
- Agent credentials cryptographically bound to the person's live control
- Both sides of every exchange checked against the Trust Network
- Native iOS and Android, with government-document identity verification
Wallet SDK
Put the same wallet capability inside your own mobile app.
The SDK gives your existing mobile app everything the iDen2 wallet does, receiving credentials, holding them, presenting them, without asking your customers to install a second app. It ships for Flutter and drops into iOS and Android host apps, and it carries the same Trust Network checks, so every credential interaction inside your product is validated against network policy.
- Same credential acceptance and presentation as the wallet
- Flutter integration for iOS and Android host apps
- Trust Network validation of issuers and verifiers built in
- Your brand, your app, your customer journey