Verify a receipt

What this page checks

Paste a receipt into the box above, choose its format, and this page asks the hosted verifier to check it. The format list covers asqav-native (the default), the asqav signature id, acta, aerf, agent-receipts, authproof, pipelock-evidence-v2, W3C VC 2.0, and SCITT as base64 COSE_Sign1. For the asqav format you can also paste a bare signature id. No account or API key is needed; the check runs over HTTPS against the public verify endpoint. To see a result without a receipt of your own, choose Use sample.

The verifier checks the receipt's signature against the signer's public key, confirms the key is an authorized issuer key, and validates the receipt's structure for its format. It reports the algorithm used and where the key came from, so you can see exactly what each check rested on.

Reading the result

A result is one of three verdicts. Receipt verified means the signature is valid and the structure checks passed. Not verified means something failed: the signature does not match, the key is not authorized, or the structure is broken, and the page names the failure class. Checks incomplete means some checks could not run, and the page says which. Two warnings deserve attention. Unsigned members are named explicitly: the signature does not cover them, so the result says nothing about them. When plain-text copies inside the receipt disagree with the signed data, the page flags the contradiction and tells you to read agent, action and time from the signed data only. For keyed digests the page says so outright, since a third party cannot independently recompute them.

What verification does not prove

A verified signature proves the receipt's bytes are unaltered and attributes them to a key. It does not prove the action was permitted, the agent trustworthy, or the underlying claim true: those are policy and provenance questions no signature can answer. This page also needs a network connection, because it calls the hosted verifier. For audits in disconnected environments, the SDK verifies receipts fully offline from a local key snapshot; see verify without Asqav and the offline verification guide.