ProofReceipt Launches Verify Endpoint to Settle File Disputes

The argument follows the same familiar script every time. You deliver the project files on Tuesday, but the client insists the folder was empty, the version was completely wrong, or nothing appeared at all. There is no neutral referee in sight, leaving only two crowded inboxes and a payment stuck right in the middle of the dispute.

ProofReceipt was created to fix the receipt side of that exact workflow. When a handoff happens, the application hashes the file using SHA-256, generating a receipt that binds that precise file to that exact moment in time. Alter even a single character within the document, and the resulting hash completely changes. Mathematics remains entirely indifferent to whose argument is louder.

Stock photo for illustration only, not from the actual event

The creator recently rolled out a new piece built on top of that core application: a dedicated verify endpoint that other software systems can programmatically call. Hosted at https://proofreceipt-verify.netlify.app, it performs one singular task by taking a receipt and an invoice amount, then returning either MATCH or MISMATCH along with the specific check that failed.

The payment integration represents the most intriguing technical choice, leveraging x402 to eliminate the need for user accounts, API key dashboards, or recurring monthly plans. Unpaid requests automatically receive a standard HTTP 402 response featuring an attached price tag: 0.5% of the invoice amount listed on the receipt, subject to a one-cent floor. A $25 invoice costs 12.5 cents to verify, while a $2 invoice hits the minimum floor. Pay the fee, resend the request, and receive the definitive verdict.

"One character changed, one cent changed — it catches both, because I tested exactly those two cases until they failed loudly."

Nenzy Brown

The endpoint currently operates in test mode on Base Sepolia while the developer sorts out final mainnet credentials. There is no sugarcoating the setup: test mode utilizes test currency, but the endpoint itself is fully functional, the 402 payment challenge functions as intended, and the verdicts returned are entirely genuine. Settled mainnet payments remain on the horizon.