Trust & reputationPlanned
Dispute Log
A public record of payments that went wrong and how each was resolved. Planned alongside escrow.
On this page+
What an entry holds
| Field | Content |
|---|---|
| Receipt | The signature of the disputed payment |
| Claim | No response, wrong output, timeout or overcharge |
| Evidence | Hash of the request and response the buyer kept |
| Seller reply | Free text plus an optional evidence hash |
| Outcome | Refund, partial refund or rejected |
| Resolution | Signature of the refund transaction, if any |
Why public
Sellers shouldn’t be able to bury complaints, and buyers shouldn’t be able to file anonymous ones. Every entry hangs off a real payment signature, so only the wallet that paid can open it, and every future buyer can read it.
What exists today
Under exact, money has already moved when a dispute starts. Refunds are voluntary transfers from the seller. Once escrow ships, a dispute inside the challenge window can hold the funds until it is resolved.
Two things already help. With withX402 a handler error prevents settlement, so the most common failure (the seller crashed) never charges anyone. And failed settle attempts through Axonpay’s facilitator are recorded in the receipts ledger with their error, where they count against the seller’s score.