Questions.
Clear answers.

ROCKVALID links one exact PDF version with a recorded person, a defined action and a time-stamped public cryptographic proof. The result is a new ROCKVALID PDF that can later be checked independently.

For a new document you can issue it, sign it or object to it. If the uploaded PDF already contains a valid ROCKVALID history, a further person can sign the current version or object to it.

Yes. Use the latest ROCKVALID PDF. ROCKVALID recognises an existing valid record, preserves the earlier confirmations and adds the new confirmation to a new document version.

No. Upload the PDF. ROCKVALID detects whether it is a new document or an existing ROCKVALID document and offers the actions that are available for that version.

The public interface and Service pages are available in German, English, French, Spanish, Italian and Polish. You can switch language from the page without changing the document proof itself.

No. The current workflow is designed as a one-time process for a specific PDF. ROCKVALID creates the public proof in the background.

No. ROCKVALID itself does not ask you to enter online-banking credentials into a ROCKVALID form. If finAPI or your bank requires authentication in its own interface, follow the information shown there.

The configured flow compares the name used in ROCKVALID with account-holder information returned through the provider process. If the required name check fails, certification is not completed.

No. A payment result alone is not automatically proof of identity. The relevant evidence depends on the checks actually performed and returned by the selected provider flow.

The current demo can combine the name check with a small payment step for the individual certification. The payment confirms the payment process; it does not by itself make every statement in the PDF true.

A cryptographic fingerprint, also called a hash, is a mathematical value derived from a file. Even a small change to the file produces a different fingerprint.

It can show that the uploaded file matches the certified version, that the expected public proof exists, that the PDF has not changed since certification, and which person, action and time were recorded. For a continuing ROCKVALID document, the earlier recorded confirmations can also be shown.

The fingerprint changes and the document no longer matches the recorded proof. Always verify the actual PDF, not a screenshot or copied text.

No. ROCKVALID verifies document integrity and the recorded process. It does not independently investigate every factual statement, every person’s legal authority or the legal effect of the document.

No. ROCKVALID is not currently a qualified trust service provider and does not provide a QES. If the law requires a particular form, that requirement must be assessed separately.

No. The public record contains compact proof data such as cryptographic fingerprints and identifiers. It is not a copy of the PDF.

The fingerprint is not a copy of the document and does not reveal its contents by itself. Public metadata is nevertheless kept as small as possible.

The browser workflow is not intended as a permanent document archive. Files and session data are processed temporarily so upload, provider return, certification, download and verification can be completed.

Keep the newest completed ROCKVALID PDF. If another person later signs or objects to the document, keep the newly downloaded version because it contains the updated confirmation history.