InvoanceInvoance
Log inGet access
Event Ledger

Every important event your business produces — anchored permanently.

The Event Ledger is an append-only, cryptographically signed record of anything that matters to your business. Payments, approvals, deliveries, user actions, system changes — once anchored, a record cannot be edited, deleted, or disputed. One API call. Permanent proof.

Start for freeView API docs

Free up to 1,000 events/month · Paid plans from $149/month · No setup fees

What the Event Ledger does

Send any business event to Invoance with a single API call. We hash it, sign it with Ed25519, timestamp it, and write it to an append-only ledger. The result is a permanent, tamper-evident record that anyone can verify — without trusting you, us, or anyone else.

Append-only

Events can only be added — never updated or deleted. This is enforced at the database level, not by policy. No admin override exists.

Cryptographically signed

Every event is signed with Ed25519 using a key bound to your organization. The signature proves the record came from you and hasn't changed.

Content-hashed

SHA-256 is applied to the event payload before signing. Any alteration — even a single character — produces a completely different hash.

Timestamped at ingestion

The timestamp is recorded the moment Invoance receives the event and is part of the signed payload. It cannot be backdated or adjusted.

Publicly verifiable

Every anchored event gets a public verification URL. Anyone — a customer, partner, auditor, or regulator — can verify the record without an account.

What businesses anchor

Any event your business produces can be anchored. These are real categories of events that companies send to the Event Ledger — from two-person startups to enterprise operations.

Payments and invoices

Payment approved, invoice sent, refund issued, subscription renewed, payout completed

Orders and fulfillment

Order placed, shipment dispatched, delivery confirmed, return initiated, inventory adjusted

User actions

Account created, permission changed, data exported, consent given, terms accepted

System changes

Config updated, deployment pushed, feature flag toggled, API key rotated, schema migrated

Contracts and agreements

Contract signed, amendment filed, SLA milestone hit, renewal triggered, NDA executed

Decisions and approvals

Expense approved, loan decision made, claim adjudicated, review submitted, budget allocated

Why regular logs aren't enough

Your application logs are built for debugging — not for proving something happened. When a customer disputes a charge, a partner questions a delivery, or anyone asks "did this really happen?" — logs don't hold up. They can be edited. They have no proof of origin. They depend on whoever controls the database.

Application logs
Event Ledger
Can be edited?
Yes — anyone with DB access
No — append-only, enforced at DB level
Cryptographic proof
None
Ed25519 signature per event
Third-party verification
Not possible
Public URL, no account needed
Timestamps
Can be changed after the fact
Signed at ingestion, immutable
Proves it happened?
Only to your own team
To anyone, independently
Integration effort
Already exists
One API call alongside existing logs

The Event Ledger doesn't replace your logs. It runs alongside them as a proof layer — anchoring the events that matter most.

Built for every size of business

Whether you're a solo founder shipping your first product or an enterprise managing thousands of daily transactions — if something important happens in your business, it should be provable.

Small businesses

Anchor payments, contracts, and customer agreements. When a dispute arises, you have cryptographic proof — not a screenshot.

Agencies and freelancers

Prove deliverables were submitted on time. Anchor approvals, revisions, and handoffs so scope disputes have a clear record.

SaaS platforms

Record user actions, billing events, and system changes. Give customers verifiable proof that their data was handled correctly.

Manufacturing and logistics

Anchor shipment confirmations, quality inspections, and chain-of-custody handoffs across your supply chain.

Healthcare

Create tamper-evident records of patient consent, treatment decisions, and data access — built for HIPAA and beyond.

Education and credentials

Anchor certifications, grades, and credential issuance. Recipients can independently verify their records forever.

When proof matters

You don't think about proof until someone asks for it. These are the moments where an immutable record changes the outcome.

Customer disputes a charge

A customer claims they never approved a payment or didn't receive a service.

You dig through logs, export CSVs, and hope the timestamps weren't modified.
You send a public verification link. The cryptographic proof speaks for itself.
Partner questions a delivery

A supplier or logistics partner says the handoff never happened.

Your internal records are inadmissible — you control them.
The delivery event was anchored at the time it occurred. Independently verifiable.
Audit or compliance review

A regulator, investor, or auditor asks for proof that records haven't been tampered with.

Weeks of manual evidence gathering. Admissibility questioned.
Cryptographic proof bundle generated instantly. Every record signed and timestamped.
Internal investigation

You need to know exactly what happened, when, and prove nothing was altered.

Logs may have been modified. No chain of custody. No certainty.
Append-only ledger. Every event anchored. Tamper-evident by design.

One API call. Permanent proof.

The Event Ledger runs alongside your existing systems. You don't reroute logs or change workflows. You POST the events you want anchored. Everything else continues unchanged.

1
Send an event

POST any business event to the ledger. Include whatever payload matters — we'll hash and sign it.

POST /v1/events
{
  "event_type": "order.shipped",
  "payload": {
    "order_id": "ord_8f2a",
    "carrier": "fedex",
    "tracking": "7489201837465",
    "shipped_by": "warehouse_east"
  }
}
2
Get permanent proof

Invoance hashes the payload, signs it with Ed25519, and returns the event ID and ingestion timestamp.

{
  "event_id":    "9549c332-a52b-…",
  "ingested_at": "2026-03-12T09:14:22Z"
}
3
Retrieve full record

GET the event to see hashes, signatures, and full cryptographic proof.

GET /v1/events/9549c332-a52b-…

→ payload_hash:  "a3f2b1c9d4…"
→ request_hash:  "c7d4e9a1b2…"
→ event_hash:    "f8a1c3d2e5…"
→ ingested_at:   2026-03-12

Technical guarantees

These aren't marketing claims. They're structural properties of how the Event Ledger works. They hold regardless of who you are, what plan you're on, or how you use the API.

Hash integrity

SHA-256 binds the proof to the exact content submitted. Any change to the payload invalidates the hash.

Signature authenticity

Ed25519 proves the record was signed by your organization's key. It cannot be forged without access to the private key.

Timestamp immutability

Recorded at ingestion. Part of the signed payload. Cannot be backdated, adjusted, or overwritten.

Append-only storage

Events can only be added. The database enforces this structurally — no admin, no API, no override can delete or modify a record.

Public verification

Every event gets a verification URL that works without authentication. The proof resolves against cryptography, not a server assertion.

No vendor lock-in

Verification can be performed offline using the public key and Ed25519 signature. You don't need to trust Invoance.

Start free. Scale when you need to.

Developer
Free
1,000 events/month

Build your integration. Test the API. Anchor real events. No credit card required.

Builder
$149/mo
250,000 events/month

For growing teams with production event volume, document anchoring, and AI attestations.

Growth
$399/mo
750,000 events/month

Multi-user team management, 7-year retention, and audit obligations for mid-market teams.

Compliance
$2,499/mo
5,000,000 events/month

For regulated financial institutions with multi-user teams, dedicated onboarding, and priority support.

Enterprise
Custom
Custom volume and SLA

Unlimited team seats, dedicated onboarding, SSO/SAML, custom retention, BAA, and priority rate limits.

All plans include public verification, Ed25519 signing, and API access. Annual billing saves 20%. See full pricing

Make your business events provable

If something important happens in your business, it should be anchored — permanently, cryptographically, independently verifiably. Start with one event. Scale from there.

Start for freeAPI referenceWhy Invoance

Event Ledger — Tamper-Proof Business Records

Every important event your business produces — anchored permanently. The Event Ledger is an append-only, cryptographically signed record of anything that matters to your business. Payments, approvals, deliveries, user actions, system changes — once anchored, a record cannot be edited, deleted, or disputed. One API call. Permanent proof.

Invoance

Neutral digital proof infrastructure for business. Tamper-evident, independently verifiable records.

Subscribe to our newsletter

Products
Platform
How It Works
Developers
Verify
Resources
Help & Legal
Products
  • Event Ledger
  • Document Anchoring
  • AI Attestation
  • Traces
Platform
  • Why Invoance
  • For Compliance Teams
  • Pricing
  • Security
How It Works
  • Overview
  • Event Ledger
  • Document Anchoring
  • AI Attestation
Developers
  • Overview
  • Endpoints
  • Authentication
  • Concepts
Verify
  • Verify Document
  • Verify AI Attestation
  • Verify Event
  • Verify Trace
Resources
  • All Resources
  • SOC 2 Guide
  • HIPAA Guide
  • ISO 27001 Guide
Help & Legal
  • Support
  • Verification Help
  • FAQ
  • Legal Notice

Invoance provides technical verification and proof infrastructure for digital records. Invoance does not issue legal, financial, or regulatory advice.

Records anchored through Invoance are cryptographically signed and tamper-evident by design. Invoance does not verify the accuracy, legality, or authenticity of document contents — only that a record existed in a specific form at a specific time. Verification links are publicly resolvable and do not require authentication. Invoance does not act as a custodian of funds, a legal authority, or a regulated financial entity. Use of Invoance does not constitute legal compliance. Consult qualified counsel for your specific obligations.

© 2025 – 2026 Invoance. All rights reserved.•