Receipt Vault

What Receipt Vault stores

Receipt Vault is the productized customer surface for retained operational evidence of every signed verdict GeoClear emits. For each call, the Vault retains the operational receipt, the canonical payload it commits to, supporting references, and (for transactional notarizations) cross-references to settlement pairings and the compliance-snapshot reference active at sign-time.

The Vault is an append-only evidence log. A receipt that was emitted at time T can be queried, packaged into a bundle, or independently verified using published verification material at any time after T — nothing in the Vault rewrites history.

What the customer should retain

The Vault holds the canonical record on GeoClear's side. For long-retention audit, the customer should ALSO retain the artifacts on their side — that is what makes verification independent of GeoClear's continued operation.

• For every high-stakes verdict (mortgage origination, insurance claim, agentic-commerce settlement, drone-dispatch audit): the full Evidence Bundle ZIP. ~20-100 KB per verdict; trivial to embed in the loan/policy/audit file alongside the rest of the record.
• The retained verification material that ships inside each bundle. It's already in the ZIP — just don't lose the bundle.
• Quarterly: a customer-side snapshot of the published verification material as additional belt-and-suspenders protection.

Retention recommendation: store bundles in your existing audit/document management system the same way you store the rest of the loan/policy/contract record. They're regular files; no special infrastructure required.

Bundle file structure

Every Evidence Bundle is a self-contained ZIP. It includes the operational receipt, the canonical payload the receipt commits to, the retained verification material needed to verify offline, and a self-contained in-browser verifier. For verdicts bound to a transaction (notarized payment context), additional artifacts capture the transaction reference, the consent/context that produced the call, and the compliance-snapshot reference at sign-time.

Detailed bundle internals (exact file layout, verifier implementation, retention guidance) are available to qualified evaluators in the Security & Verification Whitepaper under NDA.

How to verify offline

The bundle is self-contained — no internet, no GeoClear server, no external dependency required for verification.

1. Unzip the bundle.
2. Open the offline verifier inside the bundle in any modern browser (Chrome, Firefox, Safari, Edge). Works from a USB stick. Works with Wi-Fi off.
3. Drag the rest of the bundle files into the verifier.
4. The verifier re-canonicalizes the payload, validates the receipt signature against the retained verification material, and confirms the result entirely on your machine.
5. All checks green ⇒ the receipt is verified. The Verified Anchor badge confirms which trust source resolved the verification material.

For server-side verification, use the npm package: npm install @geoclear/verify-receipt. Three-line API: pass the receipt header + response body, get back { valid, payload }.

How to archive verification material for 10-year audit

The point of customer-held evidence is that verification still works after GeoClear's application server is no longer in the picture, for any reason. Three layers protect that:

1. The bundle in your file — the operational receipt, canonical payload, retained verification material, and offline verifier. This is the local truth.
2. Published verification material, distributed through redundant channels for independent durability.
3. Your customer-side periodic snapshot, archived next to the bundle as belt-and-suspenders for the case where channels become unavailable.

The underlying cryptographic primitives are standard and forward-compatible: any future verifier that understands the published recipe can re-validate any bundle, decades from now, as long as the bundle and its retained verification material are intact. Detailed key-distribution and rotation models are available in the Security & Verification Whitepaper under NDA.

API + dashboard surfaces

• /vault/payments, payments dashboard for transactional receipts (Pro+ tiers); filter by tx_hash prefix, merchant_id, date, verdict status.
• GET /v2/vault/payments, list API, paginated.
• GET /v2/vault/payments/:receipt_id, full per-receipt detail (verdict + settlement-pairing + compliance snapshot reference).
• GET /v2/vault/payments/:receipt_id/bundle.zip, per-receipt evidence bundle download.
• /security/offline-verifier, verify any bundle ZIP locally in your browser.

Honest disclosure of what receipts prove and don't prove: on the Security page. Cornerstone explainer: What Is an Evidence Bundle? · Customer-held verification · Security & Verification Whitepaper (NDA).