A Refusal Receipt records that an institution or a person declined a request, application, signature, payment, consent, submission, or AI output — with the reason documented, the missing or required items named, and a correction or appeal path stated. Institutional and personal modes. The receipt is self-attested by its creator; its content is tamper-evident via SHA-256.
A structured record that someone refused something at a recorded moment, with the reason named and a correction or appeal path stated. Two locked modes:
Refusal receipts are a strategic moat in an AGI era: a person or institution that can refuse with a documented reason and a correction path protects everyone — the refuser, the refused party, and any later reviewer.
PlenaProof does not provide legal advice. PlenaProof does not adjudicate whether a refusal is lawful or proportionate. PlenaProof helps a refuser document the refusal so it can be reviewed. A Refusal Receipt is an organised record of a refusal event, formatted so a counterparty, a regulator, a court, a board, an employer, a university, a donor, a partner, or a public agency can read it. It is not a court order, not a regulator's determination, not a binding decision, and not an official rejection by any external authority.
Future production releases may add issuer signing keys, external timestamp anchoring, a public revocation registry, and certified-issuer status. These remain roadmap items.
Refusal Receipt v1 inherits the established VRX-1 schema conventions. All keys are alphabetised before hashing; the hash field is computed over the canonical JSON with the hash field itself removed. The published schema file is vrx1-refusal-receipt.schema.json.
All processing happens in your browser. Nothing is sent to a server. The receipt JSON, hash, and verification URL are produced locally and can be exported, printed, or saved to the local Wallet preview.
Paste a receipt JSON or upload a .json file. The page recomputes the SHA-256 over the canonical JSON (with the hash field removed) and compares it to the hash stored inside the receipt. A match means the receipt content has not been modified since the hash was computed; it does not mean the refusal was lawful or reasonable, or that any external authority must accept the receipt.
Receipts you save to the local Wallet preview are stored only on this browser, across all VRX-1 receipt-type pages. They are not synced and not uploaded. Clearing browser data on this device removes them.
A Refusal Receipt sits at the centre of the Rights, Risk & Protection suite and connects to related receipt types and platform workflows.
The institutional suite this receipt anchors. Helps institutions make complaints, appeals, evidence packets, refusal decisions, and escalation paths more reviewable and defensible. Output: Appeal & Evidence Readiness Pack.
The sibling AGI-era moat receipt. A Refusal Receipt typically pairs with a Human Review Receipt that documents the review behind the refusal. Use the optional linked_human_review_receipt_id field to bind them.
Carries the evidence-and-dispute axis of the Rights, Risk & Protection suite. When a refusal is questioned, PROVA helps organise the challenge-ready evidence packet around the refusal record.
The fairness-and-appeal axis of the Rights, Risk & Protection suite. Pairs with Refusal Receipts when the refusal turns on fairness, bias, or appeal-rights grounds.
The rights-and-readability axis. Helps make the refusal reason, missing items, and appeal path readable to the counterparty in their language and reading level.
When a refusal starts an appeal-window clock, TEMPORA's deadline calendar tracks the window so the counterparty does not miss it.
Preserves refusal records across staff turnover, leadership change, and time, so a refusal made today can still be reviewed five or twenty years from now.
For refusals that need a sealed packet for cross-border review or formal escalation, SIGILLA prepares the sealing-ready bundle.
Saved receipts appear in the Wallet's local lifetime timeline preview. Stored on this device only.
The entry-point receipt. Many Refusal Receipts trace back to an earlier submission; the optional linked_submission_receipt_id field carries the cross-reference.
The shared schema conventions, field meanings, and integrity-note pattern that this receipt type inherits.
A companion overview page that carries the six refusal-category taxonomy, the appeal path, the refusal-fields list, and the quarterly refusal log. This page is the canonical VRX-1 reference implementation for the type.