Platform basics
Contents
- Introduction
- Legal services
- The concepts
- Evidence manager
- Notification manager
- Chat manager
- Signature manager
Introduction
We currently have one type of legal services: Digital Trust.
Legal Services
Digital Trust
Digital Trust provides a set of services whose objective is to facilitate the development of use cases where guaranteeing maximum legal security is a fundamental requirement of the product.
The functionality provided by Digital Trust is supported by cloud technology and qualified trusted third parties, to provide the best balance between technological flexibility and security.
Digital Trust is made up of four functionalities:
- Evidence manager: It facilitates the registration and custody of testimonies in different digital formats. Its immutability is guaranteed through a qualified trusted third party (TSP).
- Notification manager: Service that allows the sending of certified electronic notifications guaranteeing the identity of the sender and recipient, the integrity of the notification and the moment in which each of the milestones of the notice takes place.
- Chat manager: Secure and reliable communication platform that allows you to generate real-time conversations with certified messages, for several parties, ensuring the authenticity and integrity of the shared information.
- Signature manager: Service that manages the electronic signature of documents. It allows the creation of signature requests containing one or more documents and participants (signatories, validators and observers), and reports the progress of the signature process through webhook notifications.
The Concepts
Here is a list of the concepts that you will see listed throughout this guide.
Not every concept is shared by every manager. Hash, SHA256 and
TSP are cross-cutting, but Case file, Evidence group and
Evidence belong to Evidence Manager only. The other three managers have their own entities, described in their own sections below. In particular, there is no Case file in
Signature, Notification or Chat.
- DLT: “Decentralized Ledger Technology”, referring to blockchain technology.
- TSP: “Trust Service Provider” , that are specifically accredited to deliver the highest levels of compliance with the EU eIDAS electronic signature regulation
- Evidence: An entity that represents proof that a hash (sah256) of a file has been timestamped.
- Evidence group: It is an entity that allows evidence to be grouped in it. A group can have N pieces of "Evidence".
- Case file: It is an entity that allows "Groups of Evidence" to be grouped together. A case file can have N "Groups of evidence".
- Hash: Hashing is the process of scrambling raw information to the extent that it cannot reproduce it back to its original form. It takes a piece of information and passes it through a function that performs mathematical operations on the plaintext. This function is called the hash function, and the output is called the hash value/digest.
- SHA256: SHA 256 is a part of the SHA 2 family of algorithms, where SHA stands for Secure Hash Algorithm. The significance of the 256 in the name stands for the final hash digest value, i.e. irrespective of the size of plaintext/cleartext, the hash value will always be 256 bits.
Evidence manager
The first Legal Service, as we have said, is the Evidence Manager. Through this service you can timestamp any type of digital file (images, videos, files, etc.).
The Evidence follows a hierarchy:
Complete version:
- Evidences can be within an Evidence group, and there can be N Evidences in an Evidence Group.
- And in turn, an Evidence Group can be in a Case file, and a Case file can have N Evidence Groups.
Simplified version:
- Evidence is created without Evidence group or Case file.
- Therefore, the Case file > Evidence group > Evidence docking disappears.
Types of Evidences:
Complete version:
- The type of Evidence is inferred from the Evidence group. Therefore, when creating the Evidence group you will have to indicate the Type of evidence it will have: FILE, PHOTO, VIDEO, WEB_PLUGIN
Simplified version:
- The type of Evidence is assigned when creating the Evidence itself. The types it accepts are any mime-type.
Metadata
All three entities (Case file, Evidence group and Evidence) accept metadata. This value will be optional and any key-value can be inserted.
Hash
At the time of creation of the Evidence, its hash (SHA256) has to be sent. This value is essential and will be the SHA of the file that will later be uploaded.
Whether the platform re-checks that hash against the uploaded file is a per-environment setting, and it is not on everywhere. Where it is off, a file whose content does not match the declared hash is accepted and the Evidence completes. Ask us whether it is enabled for your environment. And either way, verify on your side before uploading: the hash is what the timestamp attests, so a wrong one produces a valid timestamp over the wrong value.
Note that the hash travels in two different encodings and they are not interchangeable: the
hash field of the Evidence is the lowercase hexadecimal digest, while the
x-amz-checksum-sha256 header required when uploading the file is the same digest in
base64.
Testimony
Timestamping is performed by a qualified trusted service provider (TSP). Each tenant has its providers configured; when creating Evidence you can name which of them should testify, and if you do not, the ones configured for your tenant are used.
Completion of an Evidence
An Evidence will be considered complete once all the timestampers that have been configured for said Evidence have been processed correctly and if the Custody type is Internal, when the file is uploaded.
Custody type
The Evidence Manager has two types of file custody: Internal and External. This will be defined in the creation of the Evidence. If the custody is Internal, the creation request will respond with a link to which the file will have to be uploaded. If the custody is Internal, EADFactory will have the file and it can be consulted. If the custody is External, EADFactory will NOT have the file.
Notification manager
Sends certified electronic notifications and keeps proof of what happened to each one.
The entities
- Notification request: the draft. You create it, add attachments and receivers to it, and then activate it. Nothing is sent until activation.
- Receiver: who the notification goes to, and over which channel. A request carries N receivers.
- Notification: what activation produces. From here on it has a life of its own: it can be cancelled, cloned or resent, and it accumulates the states that make up the proof.
- Attachment: a file carried by the request. Uploaded through a pre-signed link, like Evidence files.
- Report: the certified document that attests to the notification.
There are two ways in: the step-by-step one above, and a single-call endpoint that takes the whole notification at once. Both end in the same Notification.
A request has one channel, and every receiver in it must match. Mixing channels in one request is rejected.
Chat manager
Certified conversations between several parties, with proof of what was said and when.
The entities
- Chat: the conversation. Everything else hangs from it.
- Message: what is said in a chat. It can carry one attachment.
- Participant: who takes part. They are added to the chat and can be removed from it.
- Invitation: how a participant is brought into a chat.
- Template: pre-approved message formats, needed on channels that only accept templated content.
A chat can be tied to your own processes through its parent process identifiers. That is the join between a conversation and whatever case it belongs to in your system, including a Case file in Evidence Manager.
Signature manager
Manages the electronic signature of documents, and reports progress through webhook notifications.
The entities
These nest, and the nesting is what the API paths follow: signature request > document > signatory > validator.
- Signature request: the whole process. It holds one or more documents and all the participants.
- Document: a file to be signed within the request.
- Signatory: a person who signs a given document. Signatories belong to a document, not to the request.
- Validator: someone who must approve a signatory before that signatory can sign.
- Observer: someone who follows the process without signing.
- Legal entity signer: a company signing through its representative, as opposed to a natural person.
The lifecycle
A request is born as a draft: while it is a draft you can add and edit everything. You then activate it, and from that point the participants are invited and the process runs. You can send an active request back to draft to edit it again.
Going back to draft is not free. It regenerates the identifiers of every signatory, of their validators, and of the legal entity signers, including ones that had already signed. If you stored those identifiers on your side, they no longer match. Read them again after returning to draft.