Validate a signed document
A signature is worth more if someone other than AssinaJá can confirm it. You do not need an account, or our cooperation, to check a signed PDF.
Two ways to check
Section titled “Two ways to check”Locally — open the PDF in Adobe Reader DC and use its signature panel.
Online — upload it to the European Commission’s DSS Demo Validator.
The second is the more useful one when a third party is sceptical: it is run by the European Commission, not by us, and it checks against the official EU Trust List.
The Completion Report
Section titled “The Completion Report”When a document finishes, you also get a Completion Report as a PDF. It is always issued in English, deliberately — so it can be read by a court or counterparty in any jurisdiction.
It contains the evidence gathered for each signature:
| Evidence | |
|---|---|
| Signer identity | nome, email, telemóvel |
| Device | IP address and User-Agent at the moment of signing |
| Timestamps | envio, visualização, aceitação, assinatura |
| Signature type | and its eIDAS mapping — SES / AES / QES |
| For SMS OTP | phone, send time, validation time, last 4 digits of the code |
| For QES (CMD/CMDSCAP) | AMA transaction id, and the qualified certificate’s Subject, Issuer, Serial, ValidFrom, ValidTo |
| Terms acceptance | with a SHA-256 hash of the terms text that was accepted |
Internally these are held in an append-only audit log chained with SHA-256 hashes, so a record cannot be altered after the fact without breaking the chain.
Keeping a document verifiable long-term
Section titled “Keeping a document verifiable long-term”There is a time limit worth understanding. For documents on the B-T profile, validation after the signing certificates’ issuing authorities expire depends on the OCSP/CRL responses that were available at the moment of signing. In practice: archive the signed PDF and its Completion Report now, rather than assuming you can reconstruct proof years later.