...
Date: | Author: | Version: | Changes: | Completed | Available in version (tag) | Ext. | Int. | Is in Core |
|---|---|---|---|---|---|---|---|---|
|
| 1.0 | Doc. created | Yes |
|
|
| |
| 1.1 | Added Pay per email parameter entry | Yes | ||||||
| 1.2 | Added new parameter tree entries to support the configuration of additional service Notification | Yes | ||||||
| 1.3 | Fix to avoid creating empty files if all of the payments in a invoice batch are rejected | Yes | 1.4.2 |
Terms and Definitions:
Terms/definitions: | Meaning: |
|---|---|
TBD | To be defined |
N/A | Not applicable |
...
- First run the Buckaroo Request Generator engine. If all of the payments for a run are rejected and no payments need to be sent to Buckaroo, the corresponding BUCKAROO_REQUEST_HEADER_BPE3 and/or BUCKAROO_NOTIFICTN_HEADER_BPE3 record(s) will be set to STATUS = 3 (STATUS_EMPTY).
- Then run the File Processor Generator engine instance. The file processor engine will create a file only if the request engine processed the data successfully, and the DB tables contain some records ready to be processedsuccessfully, and the BUCKAROO_REQUEST_HEADER_BPE3 and/or BUCKAROO_NOTIFICTN_HEADER_BPE3 tables contain some records in STATUS = 1 (READY_TO_PROCESS) . Please note that it is possible to configure the layout of request file (i.e. which of the fields should be present and at which position in the request record) by using the File processor generator configuration.
For example: It is possible skip adding the PayperEmail fields to the request record in the file even if they are present in the BUCKAROO_REQUEST_RECORD_BPE3 table.
...
Name: | ACCOUNT_PAYMENT_REQUEST |
|---|---|
Description: | Each record represents a direct debit payment request. The InvoiceHandlerEngine will create an account payment request record for each invoice that is successfully closed. The Buckaroo Request Generator engine will then read the payment requests in this table that are ready for capture and inserts the required payment data into buckaroo tables mentioned below. |
|
|
Name: | BUCKAROO_REQUEST_HEADER_BPE3 |
Description: | Each record represents a header which holds reference to the record data needed to generate a payment request file. Each header entry can have one or more corresponding request records in BUCKAROO_REQUEST_RECORD_BPE3 table. So for each record (not in ERROR with STATUS = 1 (i.e. in READY_TO_PROCESS status) in this table, a payment file will be generated and sent to the Buckaroo containing the information like name of the file, status, file generation date, number of records in the file etc. |
|
|
Name: | BUCKAROO_REQUEST_RECORD_BPE3 |
Description: | Each record represents a a payment record in the payment request file. Each record in this table contains actual payment information like amount, VAT, user info like name, bank account info, address etc. |
Name: | BUCKAROO_NOTIFICTN_HEADER_BPE3 |
Description: | Each record represents a header which holds reference to the record data needed to generate a seaparte pre-notification file. Each header entry can have one or more corresponding notification records in BUCKAROO_REQUEST_RECORD_BPE3 table. So for each record (not in ERROR w ith STATUS = 1 (i.e. in READY_TO_PROCESS status) in this table, a pre-notification file (containing the information like customer name, email, type of notification used, communication method used and the date of sending the notification) in the file etc.) will be generated and sent to the Buckaroo. Please note that this table will be used only if separate notification files need to be created. |
...