Authbound issuance lets your backend turn trusted business data into wallet credentials. You define a credential template once, then create wallet offers when a user needs to receive that credential.
Flow
Create a credential definition
Define the credential type, display title, format, and claim paths.
Map your record into claims
Convert your application data into the nested claim object expected by the definition.
Create an offer
Call openId4Vc.issuance.createOffer and return the offerUri to your UI.
Show the wallet handoff
Encode offer.offerQrUri as a QR code or open offer.offerUri on mobile.
Install
pnpm add @authbound/server
Initialize
import { AuthboundClient } from "@authbound/server";
export const authbound = new AuthboundClient({
apiKey: process.env.AUTHBOUND_SECRET_KEY!,
});
Credential definition vs offer
| Resource | Purpose |
|---|
| Credential definition | Project-scoped template for wallet metadata and claim paths. |
| Issuance offer | One wallet handoff for one issuance flow. |
| Claims | The user-specific data you want to issue. |
Wallet-visible definition fields are title, aliases, rendering, and claim display names. Definition metadata is authenticated management metadata and is not exposed to wallets. Do not put secrets or personal data in any wallet-visible field or in management metadata.
Runnable examples (SDK repository)
The public SDK repo includes copy-paste servers you can run locally against test keys:
| Example | Use it for |
|---|
issuer-agent-basic | Smallest issuance server: one definition and one offer. |
issuer-agent-pension | Owned definition publication, InTime issuance, and verification status polling. |
next-example | Next.js App Router verification with createAuthboundHandlers. |
Next
Start with Issue credentials, use the Node.js guide for a runnable server, then review credential definitions and credential offers.