From the document to the evidence, with defined stages
RPSIGN structures the signature process into stages linked to the document, participants and applicable policy. Authentication mechanisms and the evidence produced vary according to the adopted modality and the controls actually enabled for each workflow.
Six stages that organize the signature process
Document preparation and versioning
The process is structured around a document and the version linked to its envelope. The RPSIGN architecture contemplates workflow-associated fields such as signature, initials and other information defined by the modality, preserving identification of the version used at each stage.
Defining participants
Participants are associated with the envelope according to the role they perform in the process. Identification and contact data should be limited to what is necessary for the purpose of the workflow and handled according to the applicable policy.
Authentication and evidence policy
Each workflow may adopt different identification and authentication requirements. The applicable policy defines which controls and evidence must compose the selected modality, potentially involving electronic channels, additional validations or a digital certificate, according to the document's purpose and the enabled resources.
Signer's expression of intent
At the signing stage, the expression of intent must be associated with the document and signer through the mechanisms provided for the adopted modality. Recordable events and technical data depend on the controls actually used, device permissions, the applicable policy and the characteristics of the workflow.
Document integrity and ledger
Events actually produced may be linked to the organization's ledger through SHA-256 chaining. This mechanism allows inconsistencies incompatible with the recorded chain to be detected. HMAC-SHA-256 authenticated checkpoints strengthen integrity verification without being equivalent to a digital signature or time stamp.
Consolidation of evidence
The architecture contemplates gathering evidence relevant to the workflow into technical completion and audit documents, according to the modality and resources used. These documents have their own evidentiary and informational function within the platform: they are not ICP-Brasil digital certificates, notarization of signatures, notarial authentication or, by themselves, a time stamp issued by a Time-Stamping Authority.
Evidence appropriate to the purpose of each act
No method in isolation automatically turns a signature into an “advanced” signature. Legal classification depends on the technical characteristics actually used and on the evidence associated with the signer and the document. Channels and validations may be combined according to the modality, resource availability and applicable policy.
Email verification
Email may form part of the evidence set for a workflow, including through a one-time code when that mechanism is enabled. Confirmation of a single channel does not, by itself, determine the legal classification of the signature.
SMS or WhatsApp
Mobile channels may add distinct evidence to the authentication process when integrated and enabled for the modality. Combining two or more codes does not, by itself, make an electronic signature advanced.
Identity, document and biometrics
Enhanced-validation modalities may involve an identity document, selfie, liveness detection, facial comparison or geolocation when those resources are enabled and appropriate to the case. Biometric data are sensitive personal data and require a specific assessment of necessity, proportionality, security and retention.
Qualified signature with ICP-Brasil
When the modality requires a qualified electronic signature, the signer must use their own ICP-Brasil digital certificate, subject to the applicable technical and regulatory rules. A qualified signature is distinct from certificate-free authentication methods, and its integration depends on the specific signing and validation components used in the workflow.
Documents commonly used in legal and business practice
| Document type | Typical use | Note |
|---|---|---|
| Legal-fee agreement / services agreement | Formalizing a contractual relationship with a client | The signature modality and evidence set should consider value, risk, parties involved, purpose and any specific requirement. |
| Power of attorney (ad judicia or private) | Granting powers to a lawyer or third party | The Brazilian Code of Civil Procedure allows a power of attorney to be digitally signed in accordance with the law. The appropriate modality should consider the instrument, the powers granted and any legal, judicial or destination-system requirements. |
| Declaration and authorization | Unilateral statement of fact or consent for a specific act | The form and level of evidence should be compatible with the purpose, risk and requirements of the recipient. |
| Agreements and terms in general | Formalizing obligations, arrangements and statements between parties | An electronic expression of intent may be used when the law and the nature of the act allow that form, subject to any applicable specific formalities. |
Acts subject to a special form
An electronic signature does not remove formalities required by law. Legal transactions that depend on a public deed, public registration, specific solemnities or another special form must comply with the requirements specific to the act. RPSIGN should not be interpreted as an automatic substitute for a notary/registry office, public deed, notarization of signatures or registration where those requirements are legally mandatory.
Want to understand the legal and technical basis behind each stage?
We explain integrity, privacy, signature modalities, ICP-Brasil and the limits of each mechanism on the Security, Privacy and Evidence page.