Check every release against the standards, automatically.
Conformance automation runs standard test suites against your wallet, credential issuer or verifier every time something changes, not once before an audit. Credimi runs those suites for you, on real devices, and keeps the evidence.
-
You push a change
git push · new wallet APK
-
Credimi runs the suites
OpenID4VCI · OpenID4VP · FCAF
-
The run keeps its evidence
Temporal history · video · logs
-
Your CI passes or blocks the release
run-wallet-apk · run-issuer · run-verifier
-
Repeat on every change, or on a schedule
What is conformance automation?
Conformance automation uses tools to check that a product follows the technical standards, protocols and regulatory specifications it claims to support.
In digital identity, that means testing a wallet, issuer or verifier against OpenID4VCI, OpenID4VP, the EUDI ARF and its conformance framework (FCAF), and running the same checks again whenever the product or the standard changes.
Manual review
- Runs once, before a release or an audit.
- A snapshot that ages with every commit.
- Steps and results live in documents and spreadsheets.
- Hard to repeat the same way twice.
Automated conformance
- Runs on every change, on a schedule, or from CI.
- The same suites, run the same way, every time.
- Every input, output and artifact is kept with the run.
- Failures surface before your users or an assessor find them.
How Credimi automates it
Four steps, set up once. After that, every change runs through them on its own.
- 1 / 4
Choose the checks
Pick suites from the catalog: the OpenID Foundation conformance suite, WE BUILD / EWC, EUDIW verifier tests and EUDI FCAF.
- 2 / 4
Build a pipeline
Chain checks with real flows: StepCI calls to issuers and verifiers, Maestro flows on wallets running on phones, emulators or iOS simulators.
- 3 / 4
Run it on every change
Trigger runs from a pull request with the GitHub Action, from the CI endpoints, or on a schedule.
- 4 / 4
Read the evidence
Each run keeps a timestamped Temporal history, protocol messages, video and logs. Published pipelines feed the public scoreboard.
run-wallet-apkrun-issuerrun-verifierWhat changes for your team
-
Ship without waiting for a review
Check a new feature or integration in the same pipeline that checks everything else, from the first commit.
-
See who you actually interoperate with
Run the same scenario against the wallets, issuers and verifiers published on the Hub, and see which ones complete the flow.
-
Hand over reports, not screenshots
Every run keeps its evidence. FCAF reports hash each evidence item and point into the run history, so an assessor can check every claim.
-
Keep up as the standards move
The catalog covers several versions side by side, such as OpenID4VP 1.0, Draft 23 and Draft 24. New suites plug into the pipelines you already run.
Conformance is not a certificate you earn once. It is a check you run on every release.
Standards you can check against:
Credimi runs the reference suites for you, side by side, and adds what they lack: real wallets on real devices.
See all conformance checks ↗EUDI FCAF: wallet solution, relying party role
617 test cases
in 184 scenarios
- OpenID4VCI 1.0 Issuer and wallet
- OpenID4VP 1.0, Draft 23, Draft 24 Verifier and wallet
- OpenID Foundation conformance suite Integrated
- WE BUILD / EWC conformance Integrated
- EUDIW verifier tests Integrated
- SD-JWT VC and ISO mDoc PID Credential formats
- DCQL and Digital Credentials API Scenarios
- vLEI Organizational identity
Counts reflect the catalog shipped in Credimi on 20/10/2026. New suites plug into the same pipelines, results pages and evidence model.
Run your first conformance check
Whether you build an EUDI wallet, issue credentials or verify them, start with one suite and add it to CI when it passes.
