Anchor, attest, and verify immutable business events programmatically. Invoance operates as a neutral cryptographic layer alongside your existing systems — no workflow changes required.
Submit any business event via a single POST. Invoance hashes the payload, signs it with Ed25519, and writes an immutable ledger entry.
Attach structured metadata to anchored events — AI model versions, decision context, request identifiers — for complete audit traceability.
Deterministically verify any anchored event by recomputing its hash and validating the Ed25519 signature against Invoance's public key.
Retrieve paginated ledger entries by tenant, event type, or time range. All results include full cryptographic proof metadata.
Invoance sits outside your primary systems as a parallel proof layer. Your workflows continue unchanged. Every event you choose to anchor becomes independently verifiable — permanently.
Your system
→ POST /v1/events
payload: { type, data, metadata }
─────────────────────────────────────
hash: SHA-256(canonical_payload)
signature: Ed25519(hash, tenant_key)
ledger: append-only write
─────────────────────────────────────
→ { event_id, hash, signature, timestamp }
→ https://invoance.com/verify/<event_id> ← public, unauthenticatedcurl -X POST https://api.invoance.com/v1/events \
-H "Authorization: Bearer <your_api_key>" \
-H "Content-Type: application/json"{
"type": "invoice.approved",
"data": {
"invoice_id": "inv_9f3a",
"amount": 14200,
"approved_by": "user_7b1c"
},
"metadata": {
"source": "billing-service",
"version": "2.1.0"
}
}{
"event_id": "evt_4c8d2f",
"hash": "9f3a...c21e",
"signature": "ed25519:7b1c...a4f9",
"timestamp": "2026-02-25T14:22:01Z",
"verify_url": "https://invoance.com/verify/evt_4c8d2f"
}