Merchant Statement Replay
Verify a record
Each evaluation was sealed as a Retrospective Evaluation Record — a retrospective determination, not an authorization. An approver’s resolution is sealed the same way, as a further record that continues the chain rather than editing what it supersedes. Pick one, or paste a proof id, and the platform’s own verifier will recompute it.
Retrospective evaluation · no integration, no write access to any system3 sealed recordsHead 52aa9f29cfa2267b…
What the verifier checks
- Hash chain — every record from the start of the chain up to this one is recomputed from its own contents and re-linked.
- Signature — the record hash is checked against the Ed25519 server signature and the signing key fingerprint.
- Payload binding — the stored payload is rehashed and compared to the input hash sealed into the signed core, so an edited verdict, an edited savings figure or an edited approver name fails verification.
- Resolution binding — an approval names both the proof id and the proof hash of the record it resolves, so it can only be read against the exact record that was on the chain when it was approved.
The verifier is the platform’s, not this screen’s. It is scoped to this profile’s chain: a proof id from another chain returns “record not found”.