Concepts

This page explains the words that appear in the panel, on the signing page and in the API. It is worth reading before sending your first envelope.

Envelope#

The envelope is the unit of work in Ravisign: a document, the people who need to sign it and the sending rules (order, deadline, reminders, signature level). Each envelope has a code in the format 157b650a-75e0-4eaa-a32c-b92b5a432ee4, printed on the manifest and used in the public validator.

Every envelope created counts toward the plan's monthly envelope limit, including those that are canceled later.

Document#

The document is the PDF that will be signed. It comes from one of three sources:

• A PDF you upload, up to 20 MB and without a password.
• A text template with variables: the template text receives the envelope data (name, CPF or CNPJ, address, plan, price, term) and becomes a PDF only once, right after creation.
• A fixed PDF template: a ready-made PDF, used as is.

As soon as the document is ready, Ravisign records the SHA-256 hash of the original, a fingerprint of the file. Any change, however small, alters this value. The original is never generated again.

Signers and roles#

A signer is each person included in the envelope. An envelope accepts from 1 to 50 people, with at least one who signs. Each one has a role:

For each person, Ravisign uses the name, email address, phone number (optional) and CPF or CNPJ (optional, checked by its check digits and recorded on the manifest).

Signing order#

• Parallel (default): everyone receives the invitation at the same time and signs in any order.
• Sequential: people sign in groups, in the defined order. Each group receives the invitation when the previous one finishes. People with the same order number form a group and sign together.

Identity confirmation#

At the advanced level, before signing, each signer confirms their identity with a 6-digit one-time code:

Each code allows 5 attempts, and a signer can request at most 4 codes per hour.

Coming soon code by WhatsApp through the official API and by SMS.

Deadline and reminders#

• Deadline: the last date to sign, from 1 to 365 days. The account default is 30 days. If the deadline passes without all signatures, the envelope becomes expired.
• Automatic reminders: every so many hours (default 48, up to 720; zero turns them off), Ravisign reminds by email those who have not signed yet and whose turn has come. You can also send reminders manually from the panel or through the API; anyone who received a reminder in the last hour is skipped.

Envelope statuses#

Completed, declined, expired and canceled are final statuses: the envelope no longer changes.

Signer statuses#

Final copy and manifest#

When everyone has signed, Ravisign combines the original and the signature manifest into a single PDF, digitally signs that file with the platform certificate and applies the timestamp. This is the final copy, also called the signed copy. Details in Final copy and manifest.

Audit trail#

Each event in the envelope (creation, sending, link opening, code sent and validated, signature, refusal, reminder, completion) becomes an entry in a hash-chained trail: each event seals the previous one, and any change breaks the sequence. See Audit trail.