Your client says the file never arrived. An API can settle that now.
The argument is always the same. You sent the work on Tuesday. The client says the folder was empty, or the version was wrong, or nothing showed up at all. There's no referee. Just two inboxes and a payment sitting in the middle. ProofReceipt fixes the receipt side of that. When you deliver, the app hashes the file with SHA-256 and gives you a receipt that ties that exact file to that moment.…
When you deliver a file, ProofReceipt generates a receipt that securely links that exact file to the moment of delivery. This is done by hashing the file using SHA-256, which means that even a single character change in the file will result in a completely different hash. This feature ensures the integrity of the file, regardless of who is arguing about it.
ProofReceipt offers a verify endpoint that allows other software to check if a received file matches the original receipt. This endpoint is accessible at https://proofreceipt-verify.netlify.app. It takes a receipt and an invoice amount, and returns either MATCH or MISMATCH, indicating whether the check passed or failed. If the file or invoice amount has been altered, the endpoint will identify the specific change.
The payment process is straightforward and straightforward. An unpaid request will receive a 402 HTTP response, which includes the price attached to the verification. The cost is 0.5% of the invoice amount on the receipt, with a minimum charge of one cent. For example, a $25 invoice would cost 12.5 cents to verify, while a $2 invoice would cost the minimum of one cent.
At the moment, the service is running in test mode on Base Sepolia, pending the mainnet key setup. During this phase, all interactions involve test money, meaning the outcomes are real, but the transactions are not processed on the main blockchain. As soon as the mainnet keys are in place, the service will transition to live payments.
This verification system is particularly useful for marketplaces and escrow tools that want to include a delivery confirmation within their processes, rather than redirecting users to a separate website. Additionally, AI agents that deliver work on behalf of humans can also benefit from this solution. These agents face the same challenge as freelancers, but have no way to present a dispute resolution in a thread.
By using a hash receipt combined with a machine-readable verification call, they can create a verifiable paper trail.
To try this service, you can visit https://proofreceipt.netlify.app to create a receipt manually. Remember that it is free to use, and currently in pre-revenue mode. The developer encourages users to test the tamper case themselves by altering a character in a text file and observing the resulting verdict. This hands-on approach served as the deciding factor for the developer, confirming the effectiveness of the tamper detection feature.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
