ConversaLabs Help Center
en
Language
pt_BR Portuguese (Brazil) en English es Spanish

Public contract page and validator

Open in
View as Markdown Open in ChatGPT Open in Claude
Conversa Labs

Conversa Labs

Last updated on Jun 27, 2026

Overview

Every contract has a secure public page, accessible through a link, where external signers review the document and sign — with no need to sign up or log in. This page shows the contract content with the issuing company's branding and guides the signer through the signing flow (including OTP and the visual signature, when the level requires it).

After it's signed, there is also a public validator: a verification page that lets anyone check the authenticity of the contract and the final signed PDF. The validator shows verification details in a masked way (without exposing sensitive data), backed by the immutable audit trail (SHA-256, IP, device, consent and timestamp).

Prerequisites

  • A contract sent for signature (for the public signing page) or already signed (for the validator).
  • The matching link, delivered to the signer through native channels or shared for validation.
  • No login is required for the external signer or for whoever validates.

Step by step

  1. Send the contract for signature: the signer receives the public page link.
  2. On the public page, the signer reviews the document and follows the signing flow.
  3. Depending on the level, they confirm an OTP and record the visual signature.
  4. Once the signatures are complete, the platform generates the final signed PDF with the manifest/certificate.
  5. To prove authenticity, open (or share) the public validator page.
  6. The validator confirms whether the document is authentic and shows the verification details in a masked form.

Settings & options

  • Branding: the public page uses the issuing company's logo and colors.
  • Flow by level: simple, advanced (OTP + visual signature) or qualified (A1).
  • Final signed PDF: generated on completion, with the audit trail and manifest/certificate.
  • Masked validator: shows the verification without exposing sensitive data (privacy/LGPD).
  • Time-stamp (TSA): when configured, it appears in the verification to strengthen validity.

Use cases

  • Send the customer a signing link that opens straight on their phone, with no install.
  • Provide a third party (bank, registry, auditor) with a contract validation link.
  • Prove the integrity of the signed PDF at any time, even after closing the deal.

Tips, limits & best practices

  • Share the validator when you need to prove authenticity without sending sensitive data.
  • Advise the signer to open the public page in an up-to-date browser.
  • Keep the final signed PDF — it carries the audit trail and the verification manifest.
  • Remember the validator is masked by default to protect personal data.

Troubleshooting

  • The public page link won't open: check that the link is complete and that the contract is still active (not canceled/expired).
  • The validator says the document was not found: check that the contract was completed and that the validation link is correct.
  • The PDF doesn't match the verification: the file may have been altered — always use the final signed PDF generated by the platform.
  • The signer can't sign: check the required level (e.g., OTP) and the contact details for sending the code.

See also