x402receiptsReceipt verification

Receipt f42df94f…05e7fb

Checking in your browser…
The receipt
When24/09/2026, 09:15:52 UTC
Whatnews.wire.dev/v1/headlines
Amount0.003 USDC
Paid by0x0d3m0a…a9b1d3
Paid to0x5e6f00…0ee5e5
Deliveredyes (HTTP 200)
Fingerprintf768741ee8…18b55775
Receipt id f42df94f-1197-4f18-8a23-409abd05e7fb
On the ledgerHedera testnet
Batchbd9d9f01…fa5c · 59 receipts
Rootf2af185d28…c6124d46
Topic0.0.10714216 · message #4
Consensus time25/09/2026, 19:10:13 UTC
Open the transaction on HashScan ↗Open the group (59 receipts)All messages on this topic ↗
The ledger holds only the root — a fingerprint of the whole batch. What was bought stays private; that it existed, unchanged, at this time is public.
For auditors: the path from this receipt to the ledger root
Path from this receipt to the root

sha256 of the receipt's canonical JSON gives its fingerprint. Each step pairs it with a sibling (left or right) and hashes again; an odd node pairs with itself. The last result must equal the root above. This group was anchored before the log moved to RFC 9162, so it keeps the earlier rule.

  1. leaf  f768741ee85defa4792f61c09b87210f6b25daa06ebd84d11c173c5a18b55775
  2. right 834fbbee93dde1e87f048b9f4f4b593254cfb50c4f31681a63e722ad216d8fb8
  3. right e3758a5974f9602484bdb61ebf2a27f2005ccab1a2490f04dac612d4be046a9d
  4. left  e24fb20abc5b5eee5151fff918556a125ac31a4bda7c5a1ee1a435900bbea449
  5. right 9ba1cc4ffa5abbb31c9fb72b07ea8e92d69ab2436cf44f2655f08d9de515f1b9
  6. right 2e94dfc63666c1600f61e9ff5e363f193a3473279c23689c66ca58c3bfd805ce
  7. right bea8c40cd66088a79e7c0a7f2f7813d73a5289c6c2d3373c4c8e7d5e268588b7
  8. root  f2af185d28bed14f77ef6ee7901f82fec9fc88a1a6ae4ceb1904e74fc6124d46