Verify the receipt, not the vendor.
Check whether a contract assurance receipt is cryptographically intact, bound to one manifest, signed for the correct purpose, and active in the current global status list.
- 1Signature purpose
Attestation, selective presentation, and lifecycle status use separate public keys.
- 2Manifest binding
The signed layers must commit to the same content-addressed assurance record and opaque slot.
- 3Current lifecycle
The verifier refreshes the signed status list without looking up a person, company, or contract.
Receipt verifier
Paste a receipt bundle or choose a JSON file. Contract files are not accepted.
Verification result
No receipt checked
- Lifecycle
- Pending
- Receipt type
- Pending
- Verified claims
- Pending
- Open proof gaps
- Pending
Signed evidence
- Issued
- Pending
- Expires
- Pending
- Manifest SHA-256
Pending
Verification keys
- Presentation
Pending- Attestation
Pending- Status list age
- Pending
Declared proof gaps
A precise trust boundary
A successful result proves integrity, provenance, declared policy execution, and current lifecycle for the disclosed claims. It does not prove that a contract is legally correct, commercially wise, or semantically complete.
- Private reasoning
- Remains sealed in each party’s tenant.
- Public object
- Contains signed commitments and selective disclosures.
- Verification path
- Open keys, published vectors, and an SDK-first protocol.