Every delta recorded through PacSpace produces a verifiable proof. Every billing period produces a checkpoint. Both are independently verifiable — by either party, at any time, without involving PacSpace.
Either party can verify without involving PacSpace or the counterparty. The proof stands alone. No phone call, no login, no relationship required. The proof contains everything needed to confirm authenticity.
Same proof, same verification algorithm, same result. There is no ambiguity and no interpretation. Run the verification today, next month, or next year — the answer is always the same. The math doesn't change its mind.
Once a delta is verified and permanently recorded, the proof exists independently of PacSpace's infrastructure. Even if PacSpace ceased to exist, the proof on the verification layer remains valid. The verification outlives the verifier.
When a delta is recorded through the Balance API, it produces a proofRoot — a verifiable fingerprint committed to PacSpace's public verification layer. Anyone with the proof root can verify independently:
The provider shares a receiptId with their counterparty — via invoice, API, or dashboard. This is the key to independent verification.
Call GET /api/v1/verify/:receiptId. Returns the content fingerprint, proof value, and timestamp.
The returned contentHash is a fingerprint of the original event data. Recompute it locally from your copy. If the fingerprints match, the delta is authentic and unaltered.
Optionally verify the proof against PacSpace's verification layer directly. No account or relationship required. Full independence from end to end.
// Verify a proof independently const proof = await fetch('https://api.pacspace.io/v1/verify/rcpt_a1b2c3d4e5f6'); // Response { "receiptId": "rcpt_a1b2c3d4e5f6", "contentHash": "0x2d4e7f1a...", "proofHash": "0x8f3a9b2c...", "timestamp": "2026-02-10T14:32:01Z", "status": "verified" }
At period-end, a checkpoint produces a proof root over all verified deltas for the billing window. A single fingerprint covers every event in the period. Include the proof root or shareable URL in invoices, dashboards, or API responses.
Your system includes a proof root — a single verifiable fingerprint covering every delta in the billing period. Share app.pacspace.io/verify/{proofRoot} on an invoice or in a dashboard.
Call GET /api/v1/verify/:proofRoot. Returns the record count, net change, verification reference, and public ledger URL.
The response includes a records array with each delta (amount, reason, time, item fingerprint). Use the publicLedgerUrl to view the proof on the public verification layer.
// Verify a billing period proof root const res = await fetch('https://balance-api.pacspace.io/api/v1/verify/0xf4e3d2c1b0a9...'); const { success, data } = await res.json(); // Shareable verification page // https://app.pacspace.io/verify/0xf4e3d2c1b0a9... // Response (data) { "verified": true, "proofRoot": "0xf4e3d2c1b0a9...", "summary": { "recordCount": 1500, "netChange": -45820.00, "firstRecordAt": "2026-01-01T00:05:00Z", "lastRecordAt": "2026-01-31T23:55:00Z" }, "verification": { "reference": "0.0.12345@1234567890.123456789", "publicLedgerUrl": "https://hashscan.io/mainnet/transaction/...", "note": "This proof exists on a public verification layer that neither party controls." } }
Include app.pacspace.io/verify/{proofRoot} on an invoice, in a dashboard, or through your API. Your counterparty opens the link — no integration required. PacSpace stays invisible — the proof speaks for itself.
Engineering teams can hit the public verification endpoint directly. Automate verification in their own billing pipeline without a PacSpace account.
For maximum independence, verify the proof root directly against the public verification layer. The verification reference and public ledger URL provide full traceability. Zero reliance on any single system.
Four API calls to verified settlement. Independent proof at every step.