Skip to content

VeriSaaS Architecture

Alt

Architecture Overview

VeriSaaS Cloud exposes Services APIs in order to allow customers to consume Veridas OCR, document validation and biometric services without having to worry about on-premise deployments.

The Customer will be only responsible for Middleware, an on-premise application owned by them that is in charge of managing the communication between the End-User and VeriSaaS Cloud, and where most of the business logic resides.

The onboarding process basically is as follows:

  1. An end-user starts the onboarding process capturing images of its document and biometric information typically using Veridas SDKs (HTML, IOS, Android). Veridas SDKs are not communicating, only performing an optimal capturing.
  2. The captured information will be sent to the customers’ Middleware by the APP/web itself.
  3. The Middleware is in charge of conducting the customers business logic in addition to communicating with VeriSaaS Cloud Services. This communication must be performed using TLS1.2 or TLS1.3 protocol, and the Middleware has to be authenticated by VeriSaaS Cloud by the ApiKey header in every request.
  4. VeriSaaS processes all the images/videos uploaded by middleware.
  5. The middleware or a backoffice platform may now retrieve from VeriSaaS the document OCR data, document and/or biometry scores, image cuts, etc.
  6. Alternatively, Veridas offers an on-premises software solution (boi-das) for downloading, storing/archiving and reviewing all the validation processes.
  7. Finally, the validation is deleted by customer middleware/backoffice/boi-das. If that does not happen, Veridas auto-cleaner process will delete it after a pre-established expiration time (ie: 30mins).