Record credit deltas as usage happens. Create immutable receipts that both parties can verify. When numbers drift, the neutral record brings them back together.
Request accessIn usage-based models, you and your customer track the same activity independently. Even when both systems are correct, they measure different things—and the numbers diverge.
The problem isn't bad systems. It's the absence of a shared truth at the boundary.
Your system records when processed. Theirs records when sent. Both are "right."
What counts as a "call"? Retries? Failures? Definitions drift over time.
No third party captured the event. No way to resolve without one side conceding.
/balance/delta
Record credit deltas at transaction time. Each event is signed, timestamped, and assigned a unique receipt ID. You can't change it afterward—that's what makes it neutral.
/balance/derive
Any party can independently derive the current balance by replaying verified deltas. You, your customer, or an auditor—everyone arrives at the same number.
/balance/compare
When numbers diverge, both sides compare against the neutral record. Small variances settle automatically. Large variances resolve on evidence, not arguments.
A verified delta is an immutable, neutral, atomic record of a balance change. When you record a credit delta through the Balance API, PacSpace commits it to tamper-proof infrastructure with a cryptographic fingerprint that any party can independently verify.
Your data stays private—only a cryptographic fingerprint is stored in the permanent record. Your counterparty can verify a delta by comparing the metadata you share against the neutral record. No intermediary required.
Once recorded, a delta cannot be altered or deleted by any party.
Neither party controls the record. The neutral record is the source of truth.
Only cryptographic fingerprints are stored externally. Your data stays in your database.
Any party can independently prove a delta exists and is unmodified.
// Your API call POST /v1/balance/delta { "customerId": "cust_12345", "delta": -1000, "reason": "Monthly usage charge" } // What you get back { "receiptId": "rcpt_a1b2c3...", "status": "verified", "fingerprint": "a1b2c3d4e5f6..." } // Period-end checkpoint { "fromIndex": 0, "toIndex": 1499, "proofToken": "ef01ab..." } // ^ attach to invoices for instant verification
We batch events into immutable receipts at sub-cent per verified delta. Your data stays private, but the proof is permanent—and independently verifiable by any party.
Stop pulling engineers into billing disputes. Stop giving away credits to end arguments. Stop losing deals because finance can't verify the numbers.
Record deltas as usage happens. We handle the rest—batching, recording, and verification. Your billing system stays the same.
// Record a credit delta const response = await pacspace.balance.delta({ customerId: "cust_12345", delta: -1000, reason: "api_usage", referenceId: "req_abc123" }); // Store the receiptId for later verification const { receiptId } = response; // Later: derive the balance from verified deltas const balance = await pacspace.balance.derive("cust_12345");
When a delta is permanently verified, we deliver a webhook to your endpoint with the complete receipt. HMAC-signed for security.
{
"type": "delta.verified",
"receiptId": "rcpt_cmh1abc123...",
"fingerprint": "a1b2c3d4e5f6...",
"verification": {
"verified": true,
"discrepancies": []
},
"verifiedAt": "2026-02-10T14:32:01Z",
"status": "success"
}
Every webhook includes an HMAC-SHA256 signature in the Pacspace-Signature header. Verify the payload before processing.
Pacspace-Signature
t=1730295134,v1=abc123...
Pacspace-Event
delta.verified
Idempotency-Key
rcpt_abc123:tenant_...
API keys, webhooks, usage monitoring—all from a clean, intuitive dashboard.
Join usage-based platforms building on neutral ground.