For banks
Check a package. By its verification code.
Every signed Stedlan package carries a verification code. Enter it to see whether Stedlan issued the package, when, and whether it is still valid, then compare the PDF you hold with the file as issued.
This page shows nothing about the person the package belongs to, and asks for nothing about them.
How to compare the file
Compute the SHA-256 of the PDF you were given
Use the file exactly as you received it, and put its name in place of file.pdf.
On macOS and Linux
shasum -a 256 file.pdfOn Windows
certutil -hashfile file.pdf SHA256Compare it with the value shown here
Enter the code above. The package must be valid, and the value for the language of your PDF must equal the one you computed, character for character. Capital and small letters do not matter.
If the two differ, it is not the issued file
A different value means the file is not the one Stedlan issued for this code, whatever its pages say. Ask the applicant for the file as downloaded from Stedlan.
The data copy (JSON) and the ZIP are compared in the same way: compute the SHA-256 of the file as you received it and compare it with the value shown for that form.
The “Content fingerprint” printed at the foot of the PDF’s pages is a different value, and is not the one to compare. A preview copy with a watermark never matches.
What this check means
It confirms that the package is the one Stedlan issued, and shows its status. It says nothing else about the file, and it is not a recommendation. The bank makes its own credit decision.
Stedlan records that a code was checked.