On June 10, 2025 OpenID for Verifiable Presentations draft 29 was published. It incorporates feedback received during the review period including:

• define mdoc session transcript for redirect-based oid4vp flow
• rename verifier_attestations parameter name to verifier_info
• make the meta parameter mandatory in DCQL query
• explicitly state that various arrays need to be non-empty
• clarify text about how encryption keys are obtained
• clarify how hashing works in transaction_data_hashes
• rework & expand privacy considerations section
• capitalise use of defined terms more consistently
• relax language in some cases that required wallets to always perform signature verification
• fix language implying verifier_attestations was mandatory
• try to make it clearer that direct_post.jwt builds on top of direct_post
• update pre-final specs section
• add IANA considerations for encrypted_response_enc_values_supported
• remove now unused reference to JARM
• move verifier_attestations IANA consideration to correct section
• fix title in 23220-2 ref
• add example of response encryption
• remove reference to CBOR encoding the OpenID4VPDCAPIHandoverInfo thumbprint
• fixed reference for DC API single/multi sign requests and made it clear what the protocol identifier is
• fix type_values example in W3C Verifiable Credential section
• fix an example that used now removed jwt_vp and ldp_vp
• fix description of invalid_request error
• add note that cross-device flow diagram doesn't show all parameters
• additions to & typo fixed in acknowledgements

As agreed during the DCP WG meeting on June 10, 2025, the WG needs to agree that the -29 revision of OID4VP will become the version that is voted upon in the Foundation wide vote, to become a Final Specification, (rather than the -28 that’s currently in public review) and that the WG won’t reset the 60 day public review period.

This will be a consensus decision made at the normal June 24, 2025 DCP WG call, at 20:00 London time. This is a formal 14 day notice that the DCP WG will make that decision at that meeting. As allowed by the Process Document, this notice period will run in parallel with the public review period for OpenID for Verifiable Presentations draft 29 . The Foundation wide vote will not start until after this working group decision.

Purely editorial fixes continue to be made and published in the editors' draft.

About The OpenID Foundation (OIDF)

The OpenID Foundation (OIDF) is a global open standards body committed to helping people assert their identity wherever they choose. Founded in 2007, we are a community of technical experts leading the creation of open identity standards that are secure, interoperable, and privacy preserving. The Foundation’s OpenID Connect standard is now used by billions of people across millions of applications. In the last five years, the Financial Grade API has become the standard of choice for Open Banking and Open Data implementations, allowing people to access and share data across entities. Today, the OpenID Foundation’s standards are the connective tissue to enable people to assert their identity and access their data at scale, the scale of the internet, enabling “networks of networks” to interoperate globally. Individuals, companies, governments and non-profits are encouraged to join or participate. Find out more at openid.net.