A Submission Receipt records that a person handed something to an institution — a form, a document, a request, an application — at a specific moment, in a specific form. The receipt is self-attested by its creator; its content is tamper-evident via SHA-256.
A structured record that someone submitted something to a named institution at a recorded moment. It captures the submitter (pseudonymous where appropriate), the receiving institution, the service or process being submitted to, the date, the items handed over, and any reference number the institution returned.
It is the entry-point receipt for most other VRX-1 receipt types: a missing-item receipt, a correction trail, an escalation packet, or a verification-readiness review usually chains back to an original submission.
PlenaProof does not replace authorities. PlenaProof records the accountable path around them. A Submission Receipt is an organised record of a service event, formatted for review. It is not a certificate, not a court filing, not a registered communication, and not an official acknowledgement of receipt by the institution.
Future production releases may add issuer signing keys, external timestamp anchoring (for example, OpenTimestamps or content-addressed deposit), a public revocation registry, and certified-issuer status. These remain roadmap items.
Submission 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.
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 facts in the receipt are true.
Receipts you save to the local Wallet preview are stored only on this browser. They are not synced and not uploaded. Clearing browser data on this device removes them.
A Submission Receipt is the entry point. From here, related receipt types or institutional workflows may apply.
Use a Submission Receipt as the intake record when an applicant submits to a national ID, passport, or civil-registry office. Pairs with missing-item, correction-trail, escalation, and handover receipts.
When a submission later becomes contested, PROVA helps organise evidence and chain it back to a dated Submission Receipt.
A submission that started a clock — appeal deadline, response window, expiry date — can be linked to TEMPORA's deadline calendar.
Saved receipts appear in the Wallet's local lifetime timeline preview. Stored on this device only.
The shared schema definitions, field meanings, and integrity-note pattern that this receipt type inherits.
The general PLENA verification page. For Submission Receipts specifically, the Verify tab above performs the same SHA-256 check with a typed truth-boundary explanation.