402402Signal

Verify

Check a retained record in your browser.

Paste the complete paid response you kept and the log key you pinned from trusted configuration. The check runs locally with WebCrypto and sends nothing anywhere.

The same verification ships in the Node guard (verifyReceipt) and the Python package (signal402.verify_route_receipt). Use those for anything automated; this page is for a person with one record and a question.

Take it from your own configuration, the same value your buyer pins. A key copied from this site at verification time is not independent; the transparency page publishes the current descriptor for comparison, not as a substitute.

The reveal contains private request and decision evidence. It stays on this page; do not paste it into public tools.

What a green result establishes

The reveal recomputes the public commitment, the public leaf hashes to the receipt's leaf, the inclusion path reaches the checkpoint root, and the checkpoint carries an Ed25519 signature from the key you supplied whose name matches the log origin. Together they establish that this exact record was in the signed log when the checkpoint was issued and that its bound request, observed terms and submitted rules are the ones shown.

It does not establish delivery, settlement, output quality, human approval of the submitted rules, or the later Falcon anchor on Algorand MainNet; compare the checkpoint with the published anchors for that. Comparing the record with the seller's live challenge before signing is the guard's job, not this page's.