EFTlab's Code Signing Certificate

As many of you already know about the deprecation of SHA-1. The use of the signing algorithm has been deprecated in favor of the newer and more secure SHA-2 algorithm.

EFTlab still signs the executables with SHA-1 certificate and this causes warnings in the process of installation. We are aware of this and currently are in the middle of the certificate renewal process. 

SHA-1 and SHA-2 are cryptographic 'Hash' algorithms. They are used as one of the algorithms in the digital signatures that make certificates work.

Code signing is the process of digitally signing executables and scripts to confirm the software author and guarantee that the code has not been altered or corrupted since it was signed by use of a cryptographic hash.

See the compatibility matrix for SHA-2 algorithms with operating systems SHA-256 Compatibility >>

Code signing can provide several valuable features. The most common use of code signing is to provide security when deploying; in some programming languages, it can also be used to help prevent namespace conflicts. Almost every code signing implementation will provide some sort of digital signature mechanism to verify the identity of the author or build system, and a checksum to verify that the object has not been modified. It can also be used to provide versioning information about an object or to store other meta data about an object.


BP-Tools is a set of freeware applications for EFT testing, benchmarking and transaction service development.

See more...


Download Flyer...


The Babylon Payments Simulator (BP-Sim) is a family of highly efficient regression and stress testing tools, designed for deployment in development and pre-production environments. BP-Sim allows users to perform an extensive range of tests across the chain of payment services.

See more...

Download Flyer...


The Babylon Payments Processing Suite(BP-Processing) is a suite of EFTlab's products for realtime payment transaction processing and authorisation.

See more...