#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 credential configuration declared on 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.
• Authorized Transaction Data Types – OpenID4VP transaction_data types an mDoc's device key may sign (embedded as MSO KeyAuthorizations).
• Selective Disclosure – Which SD-JWT claims a holder can selectively disclose.
• Credential Status – Configuration for credential revocation/suspension.
• Notifications – Webhook settings for issuance events.

#Profile Lifecycle

1. Create – Define a profile with your desired configuration.
2. Use – Create credential offers that reference the profile.
3. Update – Modify the profile configuration (creates a new version).
4. Delete – Permanently remove the profile when no longer needed.

#Supported Credential Formats

Profiles can be created for any credential format your issuer service supports:

#Next Steps

• Create a Profile – Step-by-step guide to creating your first profile.
• Manage Profiles – View, update, and delete profiles.