Issue from your own products
Use the API or SDK to add credential issuance to an existing service without rebuilding the user journey around a separate workspace.
Issue verifiable credentials from the systems you already use. Identra helps organizations move from a trusted result to a credential people can receive, keep, and reuse.

Why Credential Issuance
Give teams the controls they need to issue credible, reusable credentials without hiding the trust decisions that make them valuable.
Use the API or SDK to add credential issuance to an existing service without rebuilding the user journey around a separate workspace.
Use CertNet or connect a blockchain, ledger, or registry selected by your organization and its governance requirements.
Prioritize OpenID4VCI through QR and deep links for Identra Wallet and compatible external wallets.
Manage module versions, issuance history, status changes, suspension, revocation, expiry, and audit events.
How it works
Integrate directly through the API and SDK, with Dynamic Flow available as an additional channel when issuance belongs inside a verification journey.
01 · Connect
Choose the approved result or business event that should lead to a credential.
02 · Integrate
Create a clear issuance journey inside the product your customers already use.
03 · Issue
Use Identra-managed signing or connect infrastructure under your control.
04 · Operate
Keep every module and issued credential understandable after launch.
Your trust model
Choose the operating model that fits your security responsibilities without changing the holder experience.
Identra can manage the core issuance operations so your team can focus on the service and the people receiving credentials.
Connect a KMS, HSM, or external signer while Identra coordinates modules, delivery, and lifecycle workflows.
Start with CertNet or connect a blockchain, ledger, or registry chosen by your organization. The right option depends on governance, interoperability, and operating requirements.
Built for your operating model
Engineering teams integrate issuance directly, while Dynamic Flow remains available when a credential should be issued as part of a verification journey.
Use it as an additional channel when issuance follows an approved verification outcome.
Create issuance sessions, connect signing infrastructure, deliver offers, and manage status from your own system.
Shared outcome
A trusted credential ready for the holder’s wallet
Designed for real reuse
Credential Issuance helps organizations turn a completed decision into portable evidence the holder can present again.
Issue degrees, certificates, and verified learning outcomes directly to a learner’s wallet.
Institution-issued · Holder-controlled · Easy to present
Convert an approved KYC result into a credential customers can reuse in a permissioned journey.
Based on verified results · Status-aware · Auditable
Our direction follows W3C VC 2.0, DID Core, SD-JWT VC, JSON-LD/Data Integrity, ISO mdoc, and OpenID4VCI.
These standards describe product direction and interoperability goals; they are not a statement that every profile is production-ready today.
FAQ
Understand where configuration ends, who controls signing, and how credentials reach a wallet.
The API and SDK path is designed for engineering teams. Dynamic Flow is an additional option for teams that want issuance inside a configured verification journey.
Yes. An approved KYC, education, membership, or other trusted result can trigger issuance when it meets the policy defined by your organization.
You can choose Identra-managed custody or connect your own KMS, HSM, or external signer so private keys remain in your environment.
Identra Wallet is the preferred experience, while OpenID4VCI is intended to support compatible external wallets as well. DIDComm remains an additional option.
Credential Issuance
Review the integration overview or talk with Identra about the credential journey your organization wants to launch.