Fortress RECEIPT
Photo proof for expenses, returns and deliveries. The customer's app seals the photo at the moment of capture; the check shows whether it was edited or submitted before. Example flow — both sides run in this page.
1 · Customer app
Starting the camera…
The seal is applied only here, to a live camera frame. There is no way to seal an uploaded picture (Fortress Rule 10).
2 · Merchant check
Check a file you received (checking never seals it):
3 · Timing on this device
Takes one live photo, then seals that frame 50 times and checks the sealed file 50 times. Median and slowest run.
4 · Measured with controls (one run, 12 real photos)
Bench messstation/bench-receipt.mjs, same flow code, 2026-11-04, AMD Ryzen AI Max+ 395 (ASUS ROG Flow Z13), not a phone. Timing in Chrome: proofcam/tests/receipt-page-e2e.cjs. Evidence: Documentation/SSOT/evidence/RECEIPT_J322.md.
| Case | Result |
|---|
What this check does not do
The film: why, and every button explained live
First the why as a drawing, then a real recording of this page: every button is pressed and the result shown. At the end: what the product does not do. Voice: neural text-to-speech. Deutsche Fassung (mp4)