BACS Automation

Purpose When building an automated BACS submission workflow, this node is responsible for checking and the transactions in the submission and validating them against BACS or Faster Payment scheme rules and other paygate security configuration Background Workflow Configuration Service The Pressubmission Validation nodecan be used to validate both BACS and Fatser Payment submissions. Due to differences in the scheme rules you must tell the node what type of submission it will be validating. »

Data Items The CSV rejects file format is CSV (Comma Separated values). The first row contains column headers. These headers are described in the table below. Column Name Title Description Format Example submissionId Submission Id A unique reference that paygate gives to the submission UUID/V4 ff918652-bf64-4b6b-a905-5795c32234c2 fileNumber File Number In a single file submission will be 1, otherwise the number of the file within the submission: 1,2,3…n Integer 1 recordNumber Record Number The record number within a particular file. »

Data Items The Simple JSON formatted rejects files is a standard JSON (JavaScript Object Notation) formatted file. Data items are descibed below. Name Title Description Format Example submissionId Submission Id A unique reference that paygate gives to the submission UUID/V4 ff918652-bf64-4b6b-a905-5795c32234c2 fileNumber File Number In a single file submission will be 1, otherwise the number of the file within the submission: 1,2,3…n Integer 1 recordNumber Record Number The record number within a particular file. »

Purpose When building an automated BACS submission workflow, this node is responsible for co-ordinating the digital signing of the submission. Background Before the BACS network will accept a new submission it must be signed using a digistal certificate issued to you by your bank. Signing the submission protects the submission from tampering because any changes to the submission after signing cause the signature to become invalid. Signing also helps to prove, to the BACS service, the the submission came form the correct, authorised source. »

Purpose When building an automated BACS submission workflow, the approval node is responsible for co-ordinating the approval of the submission. Background Submission is a step built into how paygate handles payment submissions. It was orginally designed as a manual step to allow a supervisor/manager to check the contents of the submission and provide final, audited approval prior to submission to the payment system. Since a workflow is providing automation to a manual process, the approval step is still required when building a submission workflow. »

Purpose When building an automated BACS submission workflow, this node is responsible for co-ordinating the secure submission of the transactions to BACS or Faster Payments. Background Once a submission has been digitally sign and approved it can be sent to BACS or Faster Payments for processing. The Submission node connects to the output of an approval node and is responsible foe a number of jobs: - Connects to BACS or Faster Payments and negotiates the authenticate procedure. »

Purpose Automates the downloading of BACS and Faster Payments reports. You can use the BACS Report Download node to create a workflow that autmatically connects to the BACS report service and downloads new reports in various different formats. Workflows can be extended to email downloaded reports to or securly download them to your own environment using the Agent. In the following simple example a trigger is created to automatically run the workflow once a days. »

Purpose Transforms a BACS report into a useable CSV format Workflow Configuration Report Service »