Skip to main content

Introduction

New names

Credential Factory was formerly IaaS (Issuer as a Service), and Verification Gateway was formerly VaaS (Verification as a Service). Only the names changed: hostnames, API paths and your integration stay the same.

iDen2 provides two API services that let you issue and verify W3C Verifiable Credentials using open standards:

ServiceWhat it doesProtocol
Credential FactoryIssue credentials to holder walletsOID4VCI (OpenID for Verifiable Credential Issuance)
Verification GatewayRequest and verify credential presentations from holder walletsOpenID4VP (OpenID for Verifiable Presentations)

Both are plain REST APIs. If you can call an HTTP endpoint and render a QR code, you can integrate iDen2 — no cryptography, wallet protocol, or DID plumbing required on your side.

How it fits together​

Verifiable credentials involve three parties:

  1. An issuer creates a credential offer via Credential Factory and shows the holder a QR code. The holder scans it with their wallet and receives the credential.
  2. A verifier creates a verification session via Verification Gateway and shows the holder a QR code. The holder scans it, chooses which fields to disclose, and presents the credential. Verification Gateway verifies the signature, issuer trust, and revocation status, then returns the extracted claims to you.
  3. The Trust Network defines which issuers a verifier trusts — verification fails if the credential's issuer is not a trusted member.
  4. The Credential Registry tracks each credential's lifecycle status — verification fails if the credential has been revoked or suspended.

Credentials are issued in SD-JWT format with selective disclosure: the holder shares only the fields a verifier asks for, not the whole credential.

The integration pattern​

Both services follow the same simple pattern:

  1. Create — POST to create an offer (Credential Factory) or session (Verification Gateway). You get back a URL and a pre-rendered QR code.
  2. Display — Show the QR code to the holder. Their wallet does the rest.
  3. Poll — GET the offer or session every 3–5 seconds until it reaches a terminal state. (Or receive a webhook if configured.)

Environments​

Staging only — for now

All documentation examples use the staging environment:

  • Credential Factory: https://iaas.stg.iden2.app
  • Verification Gateway: https://vaas.stg.iden2.app

Staging is for development and testing only. The production hosts are TBD — contact the iDen2 platform team before going live, and always use HTTPS in production.

Prerequisites​

Before you start, you need:

  • An iDen2 account with an active issuer or verifier configuration
  • Your OAuth client_id and client_secret (contact iDen2 onboarding)
  • A staging environment access confirmation

Next steps​

  1. Authentication — acquire an OAuth access token with your client_id
  2. Your First API Call (Credential Factory) — issue your first credential offer
  3. Your First API Call (Verification Gateway) — create your first verification session
  4. Mobile Wallet & Wallet API — how holder wallets interact with Credential Factory / Verification Gateway
  5. Browse the API Reference for full endpoint documentation