EFT PGP Encryption App

EFT Processing doesn't encrypt the bank file out of the box.

If the bank provides an encryption program to use (for example PGP Encryption), you can use Extender and the PGP Encryption app to call the encryption program for each EFT File created, and then the encrypted file can be sent to the bank.

Functionality overview

The PGP Encryption app for EFT Processing provides options to sign (with your private key) and / or encrypt (with the bank’s public key) the EFT file generated in Orchid’s EFT Processing.

Requirement! The PGP Encryption app requires Orchid’s EFT Processing and Extender (Runtime or Developer Edition).

To encrypt the file

The generated EFT file needs to be encrypted using PGP encryption and the Bank’s public key. The Bank’s public key needs to be available on the Sage 300 server.

To sign the file

The app can sign the file generated by EFT Processing or the encrypted file.

The file can optionally be signed with the user’s private key.

In such cases, the user needs to send their public key to the bank.

Generating key files

You can use various online applications to generate the key.

https://www.pgpkeygen.com/, Kleopatra, Putty or command lines and PowerShell

You just fill in the parameters, choose the key type (RSA) and its size, and then fill in a few more details, and it will generate the private and public key for you.

PGP encryption and SFTP

If you need to SFTP the encrypted and/or signed file, you configure this in EFT Processing, using standard EFT configuration in EFT Banks.

For details, see Setup SFTP Output Destination

Contact Orchid for further details on the PGP encryption app.