x402receiptsReceipt verification

Receipt 85037451…a2a284

Checking in your browser…
The receipt
When24/09/2026, 09:44:16 UTC
Whatnews.wire.dev/v1/headlines
Amount0.003 USDC
Paid by0x0d3m0a…a9b1d3
Paid to0x5e6f00…0ee5e5
Deliveredyes (HTTP 200)
Fingerprint0bf644dba1…9c3f237c
Receipt id 85037451-80a5-47d2-a8c1-ff252ca2a284
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  0bf644dba1c6d568cb95bb4debd5454a31563778c060228432a682269c3f237c
  2. left  3c84cdddc547c031be23c9daad371845ade67c2c42f12b7cbfc88564a7a2517b
  3. left  43f711a9a72ae0e0d86920f0847ddc54575f8d0891ee2401739b7a7c8c3de076
  4. right 222f01c7e2bd2ff4531f173c56dd7b25b48cc93f90433f6d242cfea53b1f6e43
  5. right 052815df18223e83431358727d72288d1b2032b7cda72f4c96565868f797680e
  6. right 30512387f1df7c135c5a5c5f4430f3f7ae113aa7d7c6fc72c7264b011cb4f176
  7. left  b369bef878dd99705d7953be7383411f586b9d9ebebcab7aa72b6fa29ed7cd96
  8. root  f2af185d28bed14f77ef6ee7901f82fec9fc88a1a6ae4ceb1904e74fc6124d46