In the SaaS version, the user manually encodes his data as and when he needs it.
Other situations are possible:
- the user already has a well-structured database that he wishes to transfer to 1stKYC.
In this case, it is possible to consider a semi-automatic import of the data into the application.
The working mode is that the user usually provides us with a file in .csv (or .xls) format that we inject into 1stKYC.
The working methods are defined on a case-by-case basis. - the user uses a “business software” where the data specific to his activity is stored and managed.
If this business software does not manage the anti-money laundering aspect, it is possible, via one of the APIs we have developed, to synchronise the business software with 1stKYC so that our application supports the main business software.
This is generally done on a case-by-case basis, depending on the business software and the wishes of the users.
