[ Haia Trace ]

Money moved. Did the operation complete?

One deterministic Operation Receipt shows what completed, what stayed open, and why.

No signup. Compare one FULL and one PARTIAL Receipt.

Operation 01FULL
  • challengeconfirmed
  • paymentconfirmed
  • settlementconfirmed

operation completed

Operation 02PARTIAL
  • challengeconfirmed
  • paymentconfirmed
  • settlementnot confirmed

operation not complete

Same events. Same template. Same Receipt.

Local-firstPassiveDeterministicBuilt on Arc
[ The Evidence Gap ]

Paid is not the same as done.

The agent paid. The chain settled. The result never arrived. No system marked the operation incomplete.

Walletfunds sent
Protocolpayment accepted
Chaintransaction confirmed
Applicationrequest observed
? Outcome delivered
Operation ReceiptPARTIAL
  • paymentconfirmed
  • settlementconfirmed
  • outcomenot confirmed

Before a person notices, software can continue spending against an outcome that was never confirmed.

A wallet confirms that funds left. A protocol confirms that payment was accepted. A chain confirms settlement. An application log confirms that a request happened. None of them, alone, confirms that the complete operation finished.

Money movement confirms one stage. It does not prove that the operation completed.

[ The Product ]

One verdict for the whole operation.

An Operation Receipt compares the flow that should have happened with the evidence your application actually observed.

Not a log. Not a seller's receipt. Not another transaction explorer.

Confirmed

See which required stages completed and the observations that support them.

Not confirmed

See exactly which required stage stayed open and what that absence means.

Exceptions

See the explicit faults observed during the operation.

Evidence

Inspect the application, protocol, webhook, and chain observations behind the verdict.

Trace never turns missing evidence into a guessed success or failure. It names what remains unresolved.

[ Who Trace Is For ]

Stop reconstructing every incomplete operation from scratch.

Trace gives every team responsible for programmable-money operations one shared account of what completed, what stayed open, and why.

Payment operations

Reconstruct the flow across application logs, wallets, providers, webhooks, and chain records.

Identify the unresolved stage without reconstructing the operation across five different systems.

Engineering and platform

Trace lifecycle gaps across fragmented hooks and logs before discovering where the operation broke.

Go directly to the missing lifecycle stage and the underlying evidence.

Customer support

Escalate "paid but not delivered" cases and assemble screenshots from multiple systems.

Answer "paid but not delivered" cases before escalating them.

Risk and compliance

Piece together whether funds moved before required conditions were satisfied.

See whether funds moved before the required conditions were confirmed.

[ How It Works ]

From events to a verifiable verdict.

  1. [ 01 ]

    Capture

    A passive recorder and evidence adapters observe the money lifecycle from inside your application.

    x402 hooks · webhooks · chain witnesses

  2. [ 02 ]

    Assemble

    Trace groups the evidence by operation and compares it with a template defining the required flow.

    events + template → Receipt

  3. [ 03 ]

    Verify

    The Receipt returns the completed stages, unresolved stages, and observed exceptions. The same inputs reproduce the same result.

    deterministic · machine-readable · local

Application
Captured evidence
Operation template
Operation Receipt
const writer = createRunEventWriter();
trace(agent, { writer });

Trace observes the flow. It does not move funds or decide whether payment should proceed.

[ Built and Demonstrated on Arc ]

Arc settles value. Trace restores operation-level evidence.

Circle Gateway batches many payment authorizations into one Arc settlement transaction. The transaction proves that the batch moved. It does not show whether every application-level operation delivered its expected outcome.

Trace preserves one Receipt per operation, connects settlement to the application flow it belongs to, and verifies reported settlement against Arc.

x402 · Circle Gateway · Arc

One batch. Many distinct operations.

Trace observes the payment lifecycle from buyer and seller applications. Even when Gateway settles many payments together, every operation keeps its own status, gaps, and evidence.

Agentic API PaymentPARTIAL
  • challengeconfirmed
  • paymentconfirmed
  • settlementnot confirmed

The payment was submitted, but settlement was not observed.

Circle Webhooks · Wallets · Arc Escrow

Funds moved. The obligation stayed open.

Trace compares the release of escrowed funds with the delivery and criteria evidence required to authorize that release.

Escrow ReleasePARTIAL
  • depositconfirmed
  • criterianot confirmed
  • dispositionconfirmed

Funds were released while the required obligation evidence remained unconfirmed.

What Trace adds to the Circle stack
Per-operation evidenceClaim-vs-chain verificationMachine-readable completenessRebuildable Receipts

Arc is where Trace proves its full value across agentic payments, batched settlement, and conditional release. Trace turns those flows into operation-level evidence that applications and agents can act on. Adapters and templates extend the same Receipt model to additional protocols, providers, and chains.

[ Built to Extend ]

Trust the verdict. Change the rail.

Safe in the money path

  • Passive capture
  • Fail-open recording and kill switch
  • Allowlist-based sensitive-data redaction
  • Zero runtime dependencies in core and x402
  • Local-first Receipt assembly

One Receipt, more operations

  • Adapters connect new evidence sources
  • Templates define new operation flows
  • The deterministic core stays unchanged
  • Providers, chains, and witnesses share one model
  • One Receipt across API payments, batches, and escrow
Paid APIsBatched paymentsEscrowClaim vs chainAgent self-audit

Trace gives teams a local verdict for each operation. Haia Control Plane carries the same operation model across runs, services, and time — exposing recurring failures, systemic gaps, and operational trends.

[ Try Trace ]

Run one flow. See what actually completed.

Open the live demo and compare one completed operation with one unresolved operation. See the exact evidence that separates them.

See It Run

Local-first. No account required.