RECEIZ
What is a receiz?
A verifiable record: the file is the source of truth. One record. One proof. Independent verification.
The file verifies itself. Verify links (/v) are optional public convenience for that same file.
Flow: Record → Seal → Share → Verify.
- 1.(noun) A verifiable record of anything. Proof, in the file.Example: “Send me the receiz.”
- 2.(verb) To create a verifiable record that can be checked later and cannot be changed.Example: “Payment requires a receiz.”
Beginner quick start
Start here for instant clarity. Open the expert section only when you need implementation depth.
Core definition
What Receiz is in one pass: file + match = verified.
How to use
Everyday flows: record moments, seal files/folders, share, verify, download.
Verification model
Plain-language checks: what passes, what fails, and why screenshots fail.
Timestamp and pulse
Pulse is the record id used for verification. Timestamp is human reference.
Accounts and storage
Record, Seal, and Verify do not require accounts. Accounts add authorship, custody, and collaboration surfaces.
Login with Receiz ID
Passkey-first account access with magic-link fallback under one identity.
Upgrade and authorship
Upgrade is for authorship + custody controls. Verification stays public.
WireProof (Pro) and API
WireProof turns outbound payments into sealed proof files. Pro is the operations tier: includes Premium, then adds API/webhooks, structured claims, and optional FaceID signing.
Institutions
How this supports audit, retention, and cross-party workflows.
Technical specification (expert)
For builders: verification guarantees and threat boundaries, without implementation leakage.