Skip to content

Introduction

Purpose of the document

The purpose of this document is to describe :

Definitions

  • Dashboard: web interface for managing the subscription process and the life cycle of client files;
  • clientFile: information about the client and their supporting documents;
  • manager: a user with the role of "manager" for the dashboard who can modify the paths;
  • operator: a user with the "operator" role for the dashboard who can validate client files;
  • workflow: configuration of a contractualisation process;
  • product: support for a subscription process;
  • profile: information enabling the list of supporting documents to be submitted and the list of documents to be signed by the end user to be specified for a customer file or for a signatory (for example, requesting a salary slip for a file with the employee profile and a tax notice for the retired profile); the documents to be signed can be linked to a profile; the post-signature supporting documents remain common to both signatories.
  • Consent protocol: conditions that the end-user must accept before signing the contract.

Trust and Sign

Trust and Sign is a SaaS platform that enables the configuration and the configuration and execution of a 100% digital underwriting journey.

A subscription pathway links 3 elements:

  • the SignBook: a web component enabling the end user to follow the various stages of the process;
  • Trust and Sign: SaaS platform operated by Namirial and offering electronic signature, anti-fraud, file validation and legal archiving functionalities;
  • The IT client: the infrastructure hosting the server software component linking Trust and Sign to the information system.

Diagram of a route

path diagram

In the Trust and Sign information system, a client file is materialized by a resource of type clientFile.

The role of the software component hosted in the client IT is therefore to :

  • Create the clientFile in Trust and Sign ;
  • Retrieve the list of clientFiles according to their status. In general, this retrieval will be used to transmit client files into the information system;
  • Retrieve, for a clientFile, its archive containing all the files making up the folder;
  • Accept or reject the clientFile (optional depending on the validation mode). Upon acceptance, the file will be legally archived (only if a signature has been performed)

Since the Winter 19' version of Trust and Sign, the IT client can be notified directly through the web hooks configured in the path (http request from server to server).

The change history of the documentation can be found here.