The esilverpay system was a proprietary payment system based on previous metals. It was using a proprietary terminal based on a custom build of windows CE on a Telpo TPS-360 terminal and loaded with specific software components written in C++ and C# for the .NET 3.5 compact framework.
The custom windows CE build had restricted security. I was the designer and only developer for the whole project which lasted more than three years. The terminal has a secure ciphered bootloader and a custom GUI as well as keys loaded in a TPM (Trusted Platform Module). The terminal was working online and had Wi-Fi, 4G and Ethernet connectivity. It was connected to a backend, developed with docker and asp.net (C#) for IIS. The connection between the backend and the server was encrypted with TLS 1.2. The terminal, the connections and the server were PCI-DSS compliant.
The principle of esilverpay was based on exchange with precious metal (silver) which was vaulted on a merchant's account.
The merchant could withdraw physical silver or exchange it against fiat value (USD).
Esilverpay had a bank licence and had operated in the USA for two years. It was used for several businesses which are legal but who cannot usually obtain a merchant's account: legal cannabis, lottery tickets, some games, etc. ... This was a niche market where we were competing among a few other fintechs which also were providing proprietary payment systems for these types of businesses. For two years the system operated fully with almost a hundred of terminals deployed and several dozens of millions of $ of transactions processed monthly. The system allowed full control of the terminals, remote management, remote blocking of a terminal as well as full database management, chargebacks tracking, etc ... The system operated a private PKI with each terminal being loaded with its own certificate.
The project was stopped after three years (2016-2019) because of some different strategy from the shareholders of the project who preferred to invest in an ICO for a new type of cryptocurrency.
The custom windows CE build had restricted security. I was the designer and only developer for the whole project which lasted more than three years. The terminal has a secure ciphered bootloader and a custom GUI as well as keys loaded in a TPM (Trusted Platform Module). The terminal was working online and had Wi-Fi, 4G and Ethernet connectivity. It was connected to a backend, developed with docker and asp.net (C#) for IIS. The connection between the backend and the server was encrypted with TLS 1.2. The terminal, the connections and the server were PCI-DSS compliant.
The principle of esilverpay was based on exchange with precious metal (silver) which was vaulted on a merchant's account.
The merchant could withdraw physical silver or exchange it against fiat value (USD).
Esilverpay had a bank licence and had operated in the USA for two years. It was used for several businesses which are legal but who cannot usually obtain a merchant's account: legal cannabis, lottery tickets, some games, etc. ... This was a niche market where we were competing among a few other fintechs which also were providing proprietary payment systems for these types of businesses. For two years the system operated fully with almost a hundred of terminals deployed and several dozens of millions of $ of transactions processed monthly. The system allowed full control of the terminals, remote management, remote blocking of a terminal as well as full database management, chargebacks tracking, etc ... The system operated a private PKI with each terminal being loaded with its own certificate.
The project was stopped after three years (2016-2019) because of some different strategy from the shareholders of the project who preferred to invest in an ICO for a new type of cryptocurrency.
