Each transaction file is processed by Q2's Direct Payables service, which validates the file and then sends it to the UUX database. Once there, the transaction is processed as if the transaction were initiated from within digital banking, following the standard transaction processing route and approval processes.
It is important to note that transaction files and individual transactions have different workflows and are subject to different notification systems.
For example, when a file is submitted to the SFTP site, that file is validated by the Direct Payables service. The Direct Payables email notification only includes information on whether the file passed or failed validation, not whether any of the transactions failed or processed. Notifications about the transactions are generated from UUX, and therefore the notification settings are set within UUX.
The file is processed according to the following workflow:
-
The Direct Payables service digitally signs the transaction file using a private key.
-
The transaction file is uploaded to the SFTP site hosted by the FI.
-
The Q2 SFTP interface picks up the file.
-
The Q2 SFTP interface authenticates the file using SSH keys and, using the Q2 Open Banking API, sends the file to Q2’s database.
Note
Q2’s digital banking will block duplicate files, but not duplicate transactions. Each file is assigned a unique hash code based on file properties and contents, and if two files have the same generated hash code, then the duplicated file or files will not be processed.
-
The transaction is processed according to the Wire or ACH Pass-Thru setup.
Note
At the time of transaction file submission, the Open Banking policy is evaluated for allowed actions (including approvals), but the Group policy is evaluated to determine aggregate transaction limits.
-
The transaction is available to view in UUX. Transactions that were submitted using Open Banking are marked as EXTERNAL within the Payment Details for the transaction.