Overview
Credential Profiles are the foundation of the Issuer2 Service's profile-based architecture. A profile defines all the default values needed to issue a specific type of credential, making it easy to create consistent credential offers without repeating configuration.
What is a Credential Profile?
A credential profile is a reusable configuration that contains:
- Credential Configuration ID – The type of credential this profile issues (must match a supported credential type in your issuer service)
- Issuer Identity – The DID, key, and/or X.509 certificate chain used to sign credentials
- Credential Data – Default data template for the credential
- Data Mapping – Dynamic data functions for populating credential fields
- ID Token Claims Mapping – Mapping from external IdP claims to credential data (for authorization code flow)
- mDoc Data Mapping – Type conversions for mDoc/mDL credentials
- Credential Status – Configuration for credential revocation/suspension
- Notifications – Webhook settings for issuance events
Profile Lifecycle
- Create – Define a profile with your desired configuration
- Use – Create credential offers that reference the profile
- Update – Modify the profile configuration (creates a new version)
- Deactivate – Soft-delete the profile when no longer needed
Profiles support versioning. When you update a profile, a new version is created. Existing offers continue to use the profile version they were created with.
Supported Credential Formats
Profiles can be created for any credential format supported by your issuer service:
| Format | Description |
|---|---|
vc+sd-jwt | IETF SD-JWT Verifiable Credentials |
jwt_vc_json | W3C Verifiable Credentials (JWT) |
mso_mdoc | ISO 18013-5 Mobile Documents (mDL) |
Next Steps
- Create a Profile – Step-by-step guide to creating your first profile
- Manage Profiles – View, update, and deactivate profiles
Last updated on April 8, 2026