How Verification Works

PacSpace records usage at the time it happens. Then it creates a proof that both sides can check later.

For customer-facing Shared Records, the product framing is simple:

Written by one side. Visible to both. Owned by neither.

The vendor writes the attestation. PacSpace records it at the time it is made and makes the record independently checkable later. PacSpace does not decide commercial meaning or act as the meter.

The Flow#

1. You Emit A Delta#

Send a POST /balance/delta request with the customer, delta, reason, and any metadata you want to attach.

{
  "customerId": "cust_8xKj2m",
  "delta": -42.50,
  "reason": "usage_charge",
  "referenceId": "inv_20260211_001",
  "metadata": { "plan": "growth" }
}

2. PacSpace Records It#

PacSpace checks the request, records the delta, and attaches it to the customer record.

3. PacSpace Creates A Proof#

PacSpace creates a proof fingerprint for the recorded delta. The proof can be checked without exposing private business data.

4. PacSpace Sends A Webhook#

PacSpace sends a webhook to your registered endpoint with the proof fields.

{
  "event": "delta.verified",
  "data": {
    "receiptId": "rcpt_a1b2c3d4",
    "proof": {
      "proofHash": "0x8f3a...",
      "contentHash": "0x2d4e...",
      "previousProofHash": "0x1c7b...",
      "itemHashes": ["0x2d4e...", "0x9f1a..."]
    }
  }
}

5. A Checkpoint Closes The Period#

At the end of a period, PacSpace creates a checkpoint for the verified deltas in that period and sends a checkpoint.verified webhook.

What A Proof Shows#

A proof shows that PacSpace recorded a specific usage delta at a specific time. It does not reveal private business data unless you choose to share that data.

Key Terms#

What You Can Do With This#

• Check a delta - Compare the content fingerprint with the proof fingerprint.
• Share evidence - Send a proof root instead of private business data.
• Review a period - Check the records used before invoices go out.
• Independent checking - Use proof fingerprints to check a proof.

For invoice and receipt bundles, use verifyUrl as the human link and verificationApiUrl as the machine verification endpoint.