Questions.
Clear answers.

ROCKVALID OTF combines an exact PDF version, a named person, a defined confirmation process and a time-stamped cryptographic proof. The result is a new ROCKVALID PDF that can later be checked against its public proof.

Upload one PDF, review it, enter the test user’s name and open Choose a test bank. Select one of the payment-provider workflows shown there, start certification and complete the provider’s sandbox process with the displayed test credentials.

Keep the ROCKVALID page open. After all checks required by the selected workflow have succeeded, ROCKVALID creates the proof and prepares the completed PDF for download.

The current demo can show finAPI GiroIdent + Payment, finAPI Payment and TrueLayer Sandbox. Availability, test users and credentials may change. Always use the information displayed directly on the Certify page.

No. The public demo is for the sandbox users and credentials displayed on the Certify page. Never enter real banking credentials into a demo environment.

No. Provider capabilities differ. A payment confirmation alone must not be treated as proof of a name match. Only a workflow that explicitly returns and validates the required identity or account-holder data can provide that part of the OTF evidence.

In the combined finAPI GiroIdent + Payment flow, the name check is a separate step before payment. If the names do not match, certification must stop.

No. The OTF workflow is designed as a one-time process. ROCKVALID handles creation of the public proof after the selected provider process has completed.

Depending on the selected provider flow, it can supply payment status, account-access evidence and identity-related data. It also handles the payment step for the individual certification. The exact checks are shown in the selected workflow; they must not be inferred from payment alone.

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.

A successful check can show that:

• the uploaded file matches the certified document version;
• the expected cryptographic record exists;
• the record was created through an authorised ROCKVALID issuer process;
• the document has not changed since certification; and
• the recorded name, action and time can be associated with that document.

Its fingerprint changes and verification becomes invalid. The check must be performed on the actual completed PDF, not on a screenshot or copied text.

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

No. Some transactions require a written form, notarisation or a qualified electronic signature. ROCKVALID is not currently a qualified trust service provider and does not provide a qualified electronic signature under eIDAS.

The current version is a public test workflow. Do not rely on it as a substitute for legally required form or professional advice, and do not use sensitive or high-impact documents unless ROCKVALID has explicitly released a suitable production service for that purpose.

No. ROCKVALID uses compact proof data such as cryptographic fingerprints, identifiers and technical metadata. The PDF contents are not written to the blockchain.

A cryptographic fingerprint is not a copy of the document and does not reveal its contents by itself. Public proof metadata should nevertheless be limited to what is necessary, because metadata can itself carry information.

The OTF architecture is designed to avoid permanent storage of document contents. Files may be processed temporarily for upload, preview, certification, download and verification. The applicable retention and deletion details must be described in the current data-protection notice.

Download and securely retain the completed ROCKVALID PDF. The originally uploaded file does not contain the final proof record. Verify the downloaded result before sharing it.