MudraWhat a certificate of completion proves — and what it doesn't
· 5 min read
When the last person signs, most e-signing tools hand you a PDF with an extra page at the end: a certificate of completion. It looks official. It's worth knowing precisely what it is, because it is useful evidence, but it is not magic.
What's on it
In Mudra Sign the certificate page lists each person who signed, with the name and email the sender entered for them, the time they signed, and the IP address the signing came from. It also shows a record fingerprint, described below.
Behind the page, the system also logs the steps in between — when each person opened their link, and whether anyone declined — so the sender can see the whole sequence of events, not just the end.
The record fingerprint
When the final signature lands, Mudra's database computes a SHA-256 fingerprint over the completed record: the original uploaded document, every value that was filled in, and the list of signers with their times and addresses. Change any of those afterwards and the fingerprint no longer matches.
The document's owner can check this at any time: a completed document shows a Record intact badge while the stored record still matches its fingerprint, and a warning if it doesn't. Completed documents are also sealed against edits through the app, and the server, not the signer's browser, records the signer's time and IP address.
What it can show
Together that's a coherent story of how the document was completed, which is what an audit trail is for.
- That a particular link was opened and used at a particular time.
- The IP address that link was used from at that moment.
- That the document, the filled-in values and the signer list haven't changed since the last person signed.
- The order and timing of events: sent, viewed, signed, declined, completed.
What it can't show
The fingerprint, meanwhile, is held by the system that created it. It shows the record hasn't been changed inside that system; it is not an independent proof the way a public-key signature is.
- Who was holding the link. Anyone who has a signer's link can sign as that person; the certificate shows the link was used, not that the named person used it.
- That the IP address belongs to one person. Offices, phones and VPNs share addresses, and an address is a location clue, not an identity.
- That the signer's typed name was their own. Nobody checks identity documents.
- Anything a certified or PKI-based digital signature would prove. Those bind a signature to a verified identity with cryptography that anyone can check independently of the platform.
Using it sensibly
Treat the certificate as supporting evidence alongside the rest of the paper trail: the emails that sent the link, the agreement itself, payments and later correspondence. Keep the signed PDF and its certificate together.
For high-value or high-risk documents, add what the certificate can't: confirm the signer's identity another way before you send the link, send it only to an address you know belongs to them, and use a certified provider if the law or your counterparty requires one.
Frequently asked
Does a certificate of completion make a document legally binding?＋
No. What makes an agreement binding is the law and the parties' intent to be bound. The certificate is evidence about how it was signed, which can help you show that intent if it's ever disputed.
Can anyone else verify the fingerprint?＋
At the moment the check is available to the document's owner from their own account, through the Record intact badge. There is no public verification page.
Is the certificate the same as a digital signature?＋
No. A certificate of completion is an audit record. A digital signature in the PKI sense ties the document to a verified identity using cryptographic keys, and can be checked without trusting the platform that produced it. Mudra Sign provides the first, not the second.
Sign a document in your browser
Upload a PDF, place signature and date fields, and send it to the people who need to sign. Free to start.
Start free