For national wallet ecosystems

Protect ecosystem trust with relying-party conformance tests.

The security of a national wallet ecosystem and the satisfaction of its users depend heavily on its relying parties. This OpenID4VP 1.0 and HAIP 1.0 conformance testing tool, built as an extension of the OpenID Foundation Conformance Suite, lets ecosystem owners verify RP implementations before going live. Relying parties can use it too, as a development support tool and for self-conformance testing.

Why relying-party conformance matters

Ecosystem security
A single non-conformant verifier weakens trust in the whole ecosystem, not just in its own service.
User satisfaction
Faulty RP implementations break presentation flows, and users blame the wallet for errors it did not cause.
Fraud prevention
An RP that detects invalid, revoked, expired or tampered presentations stops fraud attempts before they succeed.

Two modes: RPs develop and self-test, you verify

Readiness Test

Develop

A self-service mode that supports RP development: developers build test plans, run test cases as often as they need and fix issues before the conformance test.

Positive, negative and trust test cases
Re-run any test case as many times as needed
Detailed log and test report

Conformance Test

Verify

A formal conformance test before an RP is admitted to the ecosystem: its requests are submitted one after another while the test cases stay hidden. RPs can also run it as a self-conformance test.

Just paste the request links
Hidden test cases for unbiased results
Live tracker of passed and failed tests

A full verifier test catalogue

80+

test cases

Positive cases check that a verifier meets each requirement of OpenID4VP 1.0 and HAIP 1.0. Negative cases hand it faulty presentations (invalid signatures, revoked or expired credentials, untrusted issuers) and expect a safe rejection. Trust cases cover EUDIW ecosystem mechanisms such as PID Provider certificates and LoTE listing.

Request parameters
DCQL
Request object
Client ID prefixes
Response validation
Encryption
Trust mechanisms

Both EUDI credential formats

SD-JWT VC
mdoc

Traceable results, step by step

Every run is logged along the presentation flow, from the authorization request to the RP's acknowledgement, with error codes and details. A screenshot of the RP-side screen is attached as evidence, and the test report bundles it all as documented evidence for the admission decision.

Test report

VER-114

Authorization request received
Request object retrieved and validated
RP accepted an invalid Key Binding JWT signature
RP-side screenshot attached, awaiting review

Built for authorities and operators responsible for national wallet ecosystems.