Verify the document. Keep the evidence behind the decision.
Document authenticity begins with the exact original and the proof it carries. Receiz seals a document into a proof object that a recipient can independently verify, including with the prepared offline verifier. A familiar logo, pasted signature or convincing screenshot is not a substitute for that check.
Obtain the original
Request the complete sealed file, not a screenshot or an extracted fragment.
Verify the proof
Use the Receiz verifier and inspect its actual result for that file.
Assess the claim
Check who is identified, what is established and whether the evidence supports the decision.
Resolve the evidence question before acting on the document.
An organization receives an inspection report before accepting equipment. The reviewer checks the complete sealed original, inspects the carried identity and history, and compares the report with the required inspection scope. If someone alters the sealed payload, the altered copy cannot pass as the unchanged original when that alteration breaks its proof.
Integrity, identity and meaning answer different questions.
Integrity checks establish whether the protected material satisfies its carried proof. Carried identity establishes the identity claims verified by the applicable primitive. Reviewing the document establishes whether its content answers your business question. Keep these checks explicit: a verified original can still contain a mistake, an incomplete observation or a disputed claim.
Detect alteration without depending on a shared portal.
The receiver verifies the held proof object. A portal may deliver it, but the portal display does not replace the original. Keep the complete file intact. A PDF export, screenshot or copied paragraph may be useful to read, yet must not be presented as the enclosing proof object unless it carries its own valid Receiz proof.
Make document verification part of the handoff.
Provide the complete original with enough context to identify the subject, intended purpose and supported authority. Have the receiver inspect it before acceptance. Keep subsequent authorized additions with the proof object so the next reviewer can distinguish the earlier record from later evidence. Use the existing institutional fraud page to understand identity and issuance relationships.
Carry the original. Check it yourself.
Use a public demonstration proof object to test independent verification. Download the complete sealed example and the offline verifier. Open the verifier locally, select the held file and inspect its result. Once both files are prepared, repeat with the network disconnected. This tests the held original; it does not discover later additions elsewhere.
Questions that matter.
Can Receiz verify any ordinary PDF as authentic?
An ordinary file without applicable proof does not gain proof merely by being uploaded to a verifier. Seal the original through the supported Receiz workflow; verify the resulting proof object. Sealing does not retroactively establish an unsupported issuer claim.
Is a visible signature enough?
A signature image is visible content. Inspect the carried proof for the identity and authority claims actually established; visual resemblance alone does not establish them.
Can verification happen offline?
Yes. Prepare the offline verifier and hold the complete supported proof object locally. Offline verification checks that held object; it does not discover later additions elsewhere.