Decrypt File
Overview
Decrypts a file that has previously been encrypted by wither: - A workflow Encryption Node - The Agent
There’s no complicated key management or certificate handling to worry about. Paygate will take care of that in the background.
Usage
In the following sample a payroll file has been encrypted by the Agent prior to being upload to paygate. The file is moved into working folder and then decrypted. The file can now be used like any other and is fed into a mapping and other BACS submission
The following diagram shows the end-to-end encryption that can be achieved using a combination of Paygate Agent and a workflows using the encryption/decrytion nodes. Paygate Agent is used to ‘watch’ a local folder and encrypts any files entering the folder.
Paygate Agent send the encrypted files to Paygate and the files remain encrypted oin the Paygate environment until a workflow runs. A decryption node decrypts the files and processes the file. The file is safely deleted from the Paygate environment.
Configuration
Supply the node with the filename of the file to be decrypted together with the path to the folder containing the file.
The node expects the encrypted file to have a .pge file extension
Note: This is not a general purpose decryption node and is designed only when paygate originally encrypted the file.
Tokens
Special tokens can be used in path and filename fields to allow them to be dynamically named. For example: MyReport-21-09-2025
| Token | Meaning | Example |
|---|---|---|
| {dd} | Current Day number | 12 |
| {MM} | Current Month Number | 03 |
| {yy} | Current Year (2d) | 25 |
| {yyyy} | Current year (4d) | 2025 |
| {hh} | Current Hour (24hr) | 07 |
| {mm} | Current Minute | 45 |
| {ss} | Current Second | 22 |
| {SSS} | Current Millisecond | 123 |
Error Path
The error path is follow for the following reasons: - An error occurred durinf file decryption that resulted in the file failing to be decrypted correctly. - The file does not exist.