Skip to main content
Haia Trace passively records the lifecycle of a payment operation and assembles a single verdict — what completed, what’s missing, and which faults were observed — entirely on your machine, with no registration. The one artifact is the Operation Receipt. It is:

Not a log

A log shows events. A Receipt interprets them — comparing the operation’s expected flow against what was actually observed and stating a verdict.

Not a merchant receipt

A merchant issues its own receipt. A Trace Receipt is built from your observations, so it holds up in a dispute with that merchant.

Not a dashboard

Not trends across many operations — the full, evidence-backed account of one.

How it fits together

An adapter records what it observed. A template says which milestones the operation was expected to hit. The assembler folds the two into a Receipt. Events are the source of truth and the Receipt is derived — the same NDJSON always assembles to the same Receipt.

Start here

Quickstart

One command, no install, a Receipt on screen.

What a Receipt is

Stages, evidence, missing, exceptions — the model behind the verdict.

Demo

A real agent pays twice, reads its own verdict, and stops spending.

The packages

@usehaia/trace-cli

The haia-trace command — assembles and renders receipts.

@usehaia/trace-x402

Capture adapter for the x402 payment SDK.

@usehaia/trace-circle

Capture adapter for Circle webhook v2 notifications.

@usehaia/trace-core

Contracts and the deterministic receipt assembler.
Haia Trace is pre-1.0. All four packages are published and versioned together; expect the contracts to still move before 1.0. Pin an exact version if a receipt has to keep assembling identically.