x402receiptsReceipt verification

Receipt 9a5e8c7a…31a600

Checking in your browser…
The receipt
When24/09/2026, 09:34:43 UTC
Whatnews.wire.dev/v1/headlines
Amount0.003 USDC
Paid by0x0d3m0a…a9b1d3
Paid to0x5e6f00…0ee5e5
Deliveredyes (HTTP 200)
Fingerprint8d8ea5dac5…d21bbe75
Receipt id 9a5e8c7a-1cbd-4800-b04d-08367931a600
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  8d8ea5dac57543e1e09dfa1e684f26b343edcb3cc17e3c5ced5bb647d21bbe75
  2. left  4fab7659db28582d4ebb3bbcecc73f3c73ec27e7d962609247d388f3de0bdb01
  3. right 4f247c58c27c090adaee02f77c7734bbc61e1a01cb950f32a74b476932d9b06b
  4. right ff27c2cab91992191adc3f88e6e1c6b3121b68f8c7f9ded2b125f4664d03aece
  5. left  fab51bf009162889fb6e0eab591b562b927593eae4bea618877705732c616554
  6. left  09455c3fa7e9477fadac48ef4ede76dd8069e2e96a922e3fea7837884c926fdb
  7. right bea8c40cd66088a79e7c0a7f2f7813d73a5289c6c2d3373c4c8e7d5e268588b7
  8. root  f2af185d28bed14f77ef6ee7901f82fec9fc88a1a6ae4ceb1904e74fc6124d46