Credential formats

LutraID issues and verifies exactly two formats. Which one a credential uses is decided by the document type, not by the API call.

Format identifier	Also called	Keyed by
dc+sd-jwt	SD-JWT VC (HAIP 1.0)	vct configured on the document type
mso_mdoc	ISO 18013-5/7 mdoc	doctype + primary namespace on the document type

vc+sd-jwt is accepted on input as a legacy alias and normalised to dc+sd-jwt; it is never emitted. There is no jwt_vc_json and no ldp_vc.

You select a format indirectly, by choosing a documentTypeId that the operator already configured for one of these formats — this API never takes a raw format identifier as input.

Keys and holder binding

Key types	EC only — P-256 (default), P-384, P-521
Holder binding	JWK and COSE_Key, plus x5c — no DID methods
Wallet proofs	proofs.jwt only

Credential requests and responses may be encrypted; an encrypted response comes back as application/jwt.

Validity

Declared but not implemented

Issuer metadata reserves deferred_credential_endpoint, notification_endpoint and batch_credential_issuance, and the credential request schema reserves credential_identifier. None of them are wired up — do not build against them.