RECEIZ

What is a receiz?

A verifiable record: the file is the source of truth. One record. One proof. Independent verification.

Receiz is a deterministic verification-and-settlement platform: original bytes are authoritative for verification, replayable ledger math is authoritative for settlement, and every trust claim is mapped to code and evidence artifacts.

The file verifies itself. Verify links (/v) are optional public convenience for that same file.

Settlement authority is append-only ledger replay over persisted integer value fields and deterministic rate math.

Flow: Record → Seal → Share → Verify.

FILE + MATCH → VERIFIEDIdentitySettlement Standard
Dictionary
R
receiz
/rəˈsēz/
syll. re·ceiz
nounverbplural receizpast receizedpresent part. receizing
Definition
A verifiable record where proof lives in itself.
  1. 1.
    (noun) A verifiable record of anything. Proof in the file.
    Example: “Send me the receiz.”
  2. 2.
    (verb) To create a verifiable record that can be checked later and cannot be changed.
    Example: “Payment requires a receiz.”
Usage note
receiz functions as both singular and plural (like series).
Canon
Proof in the file. The file verifies itself.
Verification
Public. Deterministic. Offline-first.
Settlement
Replayable append-only ledger math.
Storage
Sealed files.
Proof + custody
Included with authenticated Receiz identity.
RECEIZ / GUIDE

Beginner quick start

Start here for instant clarity. Open the expert section only when you need implementation depth.

Flow: Record → Seal → Share → Verify.
Authority: original file bytes for verification; replayable ledger math for settlement.
Convenience: verify links (/v) for optional sharing and cross-checks.
RECEIZ / GUIDE

Core definition

What Receiz is in one pass: file + match = verified.

A receiz is a verifiable record. It has one authority and one public shortcut: • The file: source of truth (this is what verifies) • The verify link (/v): optional public shortcut to that same file Receiz supports moment records and sealed files/folders. The file carries embedded verification data. Verification is public and deterministic: change bytes, and it fails.
RECEIZ / GUIDE

How to use

Everyday flows: record moments, seal files/folders, share, verify, download.

RECEIZ / GUIDE

Verification model

Plain-language checks: what passes, what fails, and why screenshots fail.

RECEIZ / GUIDE

Front door and discovery

How public identity expands in Receiz.

RECEIZ / GUIDE

Accounts and storage

Record, Seal, and Verify do not require accounts. Authenticated Receiz identity includes authorship, signing, receiving, ownership, custody, and business entity tools. Custom domains begin at Business.

RECEIZ / GUIDE

Plans and upgrade

Free includes the proof, custody, identity, and ownership primitives. Premium is intelligence that stays with you, knows your work, and evolves with it. Business keeps the buyer journey on your domain. Automation keeps opportunities moving without waiting on you.

Track custody →Free carries the proof core. Premium adds intelligence that stays with you. Business keeps the journey on your domain. Automation keeps opportunities moving.
RECEIZ / GUIDE

WireProof and API

WireProof turns outbound payments into sealed proof files. Automation keeps outreach, leads, introductions, APIs, webhooks, and workflows moving.

Prove payouts →Sign in for the WireProof console, API/webhooks, structured claims, and archive/export.
RECEIZ / GUIDE

Login with Receiz ID

Passkey-first account access with magic-link fallback under one identity.

RECEIZ / GUIDE

Institutions

How this supports audit, retention, and cross-party workflows.

RECEIZ / GUIDE

Timestamp and pulse

Pulse is the record id used for verification. Timestamp is human reference.

RECEIZ / GUIDE

Technical specification (expert)

For builders: verification guarantees and threat boundaries, without implementation leakage.

Expert depth for builders and auditors. If you only need usage guidance, stay in Beginner quick start.
Next step

Choose the path.

Start from the file, open a live surface, or move the relationship onto your domain.

Start with the record