OpenID4VC High Assurance Interoperability Profile 1.0

Note

OpenID Foundation specification, final version 1.0, defining an OpenID profile for verifiable credentials with the SD-JWT VC and ISO mdoc formats, for a high level of assurance.

Summary

Purpose

The OpenID Foundation’s OpenID4VC High Assurance Interoperability Profile 1.0 (OpenID4VC-HAIP), published as a final version on 24 December 2025 OpenID4VC HAIP 1.0, is a profile of OpenID4VCI and OpenID4VP, combined with the SD-JWT VC and ISO mdoc formats OpenID4VC HAIP 1.0, [Abstract](#abstract):

Who it applies to

The profile imposes nothing by itself. Wallet providers ensure that wallet solutions support the presentation of attributes in accordance with Annex II to Implementing Regulation 2024/2982 Art. 5(1). That annex makes applicable, with adaptations, specification ETSI TS 119 472-2 V1.2.1, whose clause 6 defines a presentation profile based on OpenID4VC-HAIP Annex II ETSI TS 119 472-2 V1.2.1, § 6.1 Introduction. The requirements of the annex concern in particular relying parties and wallets Annex II.

For issuance, Annex I to the same regulation makes specification ETSI TS 119 472-3 V1.1.1 applicable, with adaptations Annex I. It provides that the wallet implements the OpenID4VCI protocol as profiled by the requirements of clause 4 of OpenID4VC-HAIP, unless otherwise specified ETSI TS 119 472-3 V1.1.1, § 4.1 General requirements.

Sections referred to, adaptations

Annex II precisely delimits the sections of the profile Annex II:

• Mandatory requirements. All mandatory requirements of sections 5, 5.3, 7 and 8 apply. “Section 5” only covers the requirements placed directly under its heading, without sections 5.1 to 5.3 Annex II.
• The annex prevails. If the annex modifies a requirement of the profile, the modified requirement applies; it can thus make an optional requirement mandatory Annex II.
• Format profiles in section 6. Depending on the format of the requested attestation, relying parties and wallets comply with the “ISO mdocs” profile or the “IETF SD-JWT VCs” profile Annex II OpenID4VC HAIP 1.0, [6.](#section-6) [OpenID4VC Credential Format Profiles](#name-openid4vc-credential-format).
• Other adaptations of the ETSI profile. The annex also voids several requirements of clauses 6.3.2.1, 6.3.2.2, 6.3.3 and 6.4.1 of the ETSI specification. It rewrites the requirement on the verifier_info parameter, which must contain the registration certificate, and adds a requirement on the certificate used with the x509_hash prefix Annex II.

Key points of the profile

• Section 5 (presentation). The verifier and the wallet support at least one of the two formats. For signed requests, the verifier uses the x509_hash client identifier prefix of OpenID4VP, which the wallet must accept. Responses are encrypted OpenID4VC HAIP 1.0, [5.](#section-5) [OpenID for Verifiable Presentations](#name-openid-for-verifiable-prese).
• Section 7 (signatures). Issuers, verifiers and wallets support at least ECDSA with P-256 and SHA-256 (ES256) to validate the signed objects listed in the section OpenID4VC HAIP 1.0, [7.](#section-7) [Requirements for Digital Signatures](#name-requirements-for-digital-si).
• Section 8 (hashes). All entities support SHA-256 for SD-JWT VC and mdoc digests OpenID4VC HAIP 1.0, [8.](#section-8) [Hash Algorithms](#name-hash-algorithms).
• Mediating API. By default, the wallet reveals to the API operating under section 5.2 of the profile which types of attestations it holds, but never their attributes or their values. If it supports this API, it offers a global setting to disable this disclosure Annex II.

Links

• Profiled specifications: OpenID4VCI OpenID4VCI 1.0 and OpenID4VP OpenID4VP 1.0.
• Intermediate standards: ETSI TS 119 472-2 ETSI TS 119 472-2 V1.2.1 and ETSI TS 119 472-3 ETSI TS 119 472-3 V1.1.1.
• Both annexes to Implementing Regulation 2024/2982 were added by Implementing Regulation 2026/1731 Art. 4.
• Learning path: step 3, the European wallet.

Written by Asphalia.