Get started

You're a developer with authentic source data (customer records, government registries, HR systems, academic transcripts, payment history) and you want to issue, hold, share, or verify it as verifiable credentials using OpenID4VC. This page is the map. It points you at the workflow you need and the docs that walk you through it.

Recommended starting point: New here? Start with Issue Credential (In-Time). It walks through your first issuance in three steps (get an API key, create a credential definition, then issue and receive) and ends with a working scannable QR code. Once that succeeds, branch out to whichever workflow below matches what you're building.

Want to understand what's happening under the hood before you write code? Read the OpenID4VC credential issuance lifecycle. It walks through every state from offer_sent to accepted and what each one means for your integration.

Prerequisites

• An iGrant.io tenant account (contact [email protected] to request access)
• Your API key (provided with your tenant)
• iGrant.io Data Wallet installed on your phone (available on the App Store and Play Store)

Self-hosting? If you're deploying on-premise instead of using the hosted PaaS, complete the Deployment Guide first. The API calls are the same once your instance is running.

Issue credentials

Create credential definitions and issue verifiable credentials to holders using the OpenID4VCI protocol. Supports in-time issuance, deferred issuance, and dynamic credential requests.

• Issue Credential (In-Time) - issue credentials immediately using Pre-Authorised or Authorisation Code flow
• Issue Credential (Deferred) - issue credentials asynchronously for batch or invitation-based workflows
• Dynamic Credential Request - request additional proof from the holder before issuing

Hold and share credentials

Receive credentials from trusted issuers and store them securely in your organisation's wallet unit. Present held credentials to relying parties when requested, with selective disclosure of only the claims they need.

• Receive and Store Credential - receive credentials from issuers and store them in your wallet
• Receive and Present Credential - respond to presentation requests with selective disclosure

Verify credentials

Define verification requirements, send presentation requests, and validate credential proofs from holders.

• Send and Verify Credential - define presentation requirements, initiate verification, and validate responses

Cross-cutting & next steps

• Webhook Events - receive real-time notifications at key stages of issuance and verification
• Use Case Workflows - worked examples for EBWOID, payments, and passwordless login
• Sandbox Organisations - create test environments to simulate multi-party credential ecosystems
• Deployment Guide - deploy on your own infrastructure via Helm chart
• Developer APIs - full API reference