Public verification URL
Each certificate can be checked at proofmark.space/verify/<id>. No account needed to verify.
Feature · Proof certificates
A certificate for every finished handover
When a client signs off, Proofmark can issue a certificate recording the approval timestamp, the deliverables and their SHA-256 hashes, the payment state, and the full proof timeline — with a public URL where anyone can verify it is genuine.
When a dispute starts, screenshots look like screenshots
Months after delivery, a payment dispute or scope argument comes down to evidence. Screenshots of chats are easy to doubt and easy to fake. What holds up is a coherent record: this exact file (hash), approved by this client (timestamp), payment confirmed (state), downloaded on this date (log) — assembled at the time it happened, not reconstructed later.
Who this is for
- Freelancers who want a clean record when projects close
- Agencies that archive delivery evidence per client
- Contractors dealing with procurement or compliance teams
- Anyone who wants to end projects with an artifact, not a shrug
How it works
- 1
Finish the handover
Client approves, payment is confirmed, final files unlock — the normal Proofmark flow.
- 2
Certificate is generated
It includes the certificate ID, project, client sign-off timestamp, deliverable hashes, payment and unlock state, and the proof timeline.
- 3
Share or archive it
Download the certificate, attach it to your records, or share the public verification link with anyone who needs to check it.
- 4
Anyone can verify
The /verify page shows a safe version of the record — valid or not, at a glance, without exposing emails, IPs, or files.
Safe by design
The public verification view never exposes client emails, IP addresses, signature images, or the files themselves.
Full evidence export
Need everything? The proof packet bundles the agreement, sign-off record, hashes, and download log into one document.
Honest scope
A certificate is a timestamped record, not a legal guarantee — and it says so on its face. Credibility comes from precision, not overclaiming.
Frequently asked questions
What information does a certificate contain?
Certificate ID, project title, client name, issuing freelancer or studio, approval timestamp, deliverable names with SHA-256 hashes, payment status, unlock time, and a proof timeline of recorded events.
Can someone forge a Proofmark certificate?
A forged document would fail online verification: the /verify URL shows only what Proofmark actually recorded for that certificate ID. If the page doesn't match the paper, the paper is wrong.
Does a certificate prevent chargebacks or disputes?
No tool can promise that. What a certificate gives you is a clear, timestamped record of approval, delivery, and payment status to present if a dispute happens. It is not a substitute for legal advice.
Who can see a certificate?
The certificate download requires the approval's secure token. The public verification page shows a reduced, safe subset to anyone with the link.
Send your first handover link in minutes
Free plan includes one full handover — approval link, payment-gated files, and a proof certificate.
Create your free account