Open Verifier

Supported inputs

Bring the artifact you want to verify

OpenVerifier reads supported files locally in your browser. No sample artifact, vendor account, or server upload is required.

Input classes

Authorization receiptsSupported VC JSON, VC-JWT, compact JWT, local W3C package, and raw technical JSON receipt profiles.
Exact-action continuity bundleOPENVERIFIER-EXACT-ACTION-BINDING-v1: full SYNC VC JSON, one canonical reviewed-action packet, and a signed Gate compatibility projection containing the exact SYNC receipt bytes.
Exact-action batchOPENVERIFIER-EXACT-ACTION-BATCH-v1: multiple exact-action bindings evaluated under one separately supplied relying-party context, with supplied-batch duplicate refusal.
OpenVerifier compatibility projectionVersioned consequence-control projection with action, signer-policy, evidence-binding, lifecycle and retry-safety checks. Alone it does not establish the human ↔ machine continuity join.
Qualification bundleSigned machine-qualification bundle evaluated against supplied relying-party trust pins and request context.

Exact-action continuity workflow

  1. Obtain the relying-party context independently from the bundle and load it first under Exact-action continuity — relying-party context.
  2. Use a full SYNC VC JSON receipt created with the designated sealed reviewed-action packet. Older receipts are not retroactively upgraded.
  3. Choose the exact-action bundle or batch. OpenVerifier recomputes the human-side action identity, verifies the exact receipt-byte reference, and compares the protected action/scope with the signed machine-side admission evidence.
  4. Read MATCH only as continuity of the supplied action evidence. Execution, provider outcome and physical effect remain separate.

The current narrow profile supports the pinned payment.release.1 action type. It does not silently follow future registry changes or accept arbitrary action types.

Local-only handling

Files are read by the browser and are not uploaded by OpenVerifier. The relying-party context stays in browser memory for the review session. No signer is accepted merely because its key appears inside the presented receipt or bundle.

Return to the verifier