...
Date: | Author: | Version: | Changes: | Completed | Available in version (tag) | Ext. | Int. | Is in Core |
---|---|---|---|---|---|---|---|---|
|
| 1.0 | Doc. created | Yes |
|
|
| |
10 May 2014 | Karuna Thulluri | 1.1 | Added Pay per email parameter entry | Yes | ||||
15 May 2014 | Karuna Thulluri | 1.2 | Added new parameter tree entries to support the configuration of additional service Notification | Yes | ||||
27 May 2014 | Karuna Thulluri | 1.3 | Fix to avoid creating empty files if all of the payments in a invoice batch are rejected | Yes | 1.4.2 |
...
PATH | Type | description | Mandatory | Default value used if the parameter is not present |
---|---|---|---|---|
ENGINE.BUCKAROO_REQUEST_GENERATOR_BPE3.ENABLED | String | To enable/disable the engine for the given brand. If set to y/true: the engine will be enabled for the brand to which this parameter is configured. Otherwise the engine is disabled for that brand. Note: If this parameter is not set or changed to something other than 'Y' (case insensitive), then the engine will not run if the general project is set up to be brand enabled (i.e., if there exists the following parameter BRAND.ENABLED and its value is not 'N'), even if there only exists a single brand. If BRAND.ENABLED parameter does not exist or is set to 'N' (case sensitive), then the engine will run in non-branded mode as per standard behaviour of EngineBranded. | YES, if the engine should be enabled for a given brand. | |
INTEGRATION.BUCKAROO.BPE3.WEBSITE_KEY | String | Fixed string from Buckaroo portal. Used if WEBSITE_KEY_B2C /WEBSITE_KEY_B2B parameters are not defined. This is the case if same websitekey is used regardless of the type of the customer. | YES, if none of the two parameters: WEBSITE_KEY_B2C, WEBSITE_KEY_B2B are defined |
|
INTEGRATION.BUCKAROO.BPE3.WEBSITE_KEY_B2C | String | Fixed websitekey from Buckaroo portal for private customers. If this parameter does not exist, then the website key configured in WEBSITE_KEY parameter is used. | NO | <Value configured in the parameter WEBSITE_KEY> |
INTEGRATION.BUCKAROO.BPE3.WEBSITE_KEY_B2B | String | Fixed websitekey from Buckaroo portal for business customers. If this parameter does not exist, then the website key configured in WEBSITE_KEY parameter is used. | NO | <Value configured in the parameter WEBSITE_KEY> |
INTEGRATION.BUCKAROO.BPE3.ACCOUNT_PAYMENT_TYPES | String | payment_type_id value of the | YES |
|
INTEGRATION.BUCKAROO.BPE3.DESCRIPTION_PREFIX | String | Prefix for the description field | YES |
|
INTEGRATION.BUCKAROO.BPE3.VAT_VALUE | String | VAT value : 21 for BPE3 | YES |
|
INTEGRATION.BUCKAROO.BPE3.CURRENCY | String | Currency Code: EUR | YES |
|
INTEGRATION.BUCKAROO.BPE3.DUE_DATE_OFFSET | String | Payment due date offset | YES |
|
INTEGRATION.BUCKAROO.BPE3.EXPORT_FILE_PREFIX | String | Prefix with which export file name | YES |
|
INTEGRATION.BUCKAROO.BPE3.EXPORT_FILE_EXTENSION | String | Extension used for export file. | YES |
|
INTEGRATION.BUCKAROO.BPE3.PRE_NOTIFICATION_FILE_PREFIX | String | Prefix with which pre-notification file name will start with, if a separate pre-notification file needs to be generated | YES, if separate Pre-notification file need to be generated | |
INTEGRATION.BUCKAROO.BPE3.PRE_NOTIFICATION_FILE_EXTENSION | Extension used for pre-notification file, if a separate pre-notification file needs to be generated For ex: .CSV | YES, if separate Pre-notification file need to be generated | ||
INTEGRATION.BUCKAROO.BPE3.CULTURE_CODE | String | ISO culture code: nl-NL | YES |
|
INTEGRATION.BUCKAROO.BPE3.PAYMENT_METHODS_ALLOWED | String | Allowed payment methods | NO | machtiging |
INTEGRATION.BUCKAROO.BPE3.PAYMENT_METHOD_INVALID_BANK_ACC | String | Allowed payment method if the bank account number is null or zero | NO | ideal |
INTEGRATION.BUCKAROO.BPE3.DUMMY_BANK_ACC_NUMBER | String | Dummy bank account number used in case the customer bank account number is either null or zero or in anyway invalid. | NO | <Empty String> |
INTEGRATION.BUCKAROO.BPE3.COUNTRY | String | Country code value | NO | NL |
INTEGRATION.BUCKAROO.BPE3.SEPA_MANDATE_DATE | Date | The default mandate date to be used if the Bank account valid_from date is null or valid_from date is before 2013-12-11. | YES | 2013-12-11 |
INTEGRATION.BUCKAROO.BPE3.SEPA_COLLECT_DATE | Number | The collect date offset : number of days from the invoice close date that is used as the Collect date for this invoice. | YES | 7 |
INTEGRATION.BUCKAROO.BPE3.USE_PAY_PER_EMAIL | String | Indicates whether the PayPerEmail service is used: If value = 'true', then Payperemail service is enabled i.e. PayPerEmail fields will be filled with proper data when the bank account info is invalid. | YES | true |
INTEGRATION.BUCKAROO.BPE3.START_RECURRENT | String | Value to be put into the 'startrecurrent' field of the Direct Debit request file. Possible values are: TRUE , FALSE | NO | TRUE |
INTEGRATION.BUCKAROO.BPE3.USE_ADDITIONAL_SRV_CREDIT_MGMT | String | Used to indicate whether the Credit management service is used. If set to true/yes, credit management related fields will be populated with proper data while request generator engine is inserting the Buckaroo request data into Buckaroo_Request_Record_Bpe3 table. | NO | true |
INTEGRATION.BUCKAROO.BPE3.USE_ADDITIONAL_SRV_NOTIFICATION | String | Used to indicate whether the Buckaroo Notification service is used. Thus it instructs the request generator engine whether or not to populate the Notification service related fields of Buckaroo_Request_Record_Bpe3 table. | NO | false |
INTEGRATION.BUCKAROO.BPE3.CREATE_SEPARATE_NOTIFICATION_FILE | String | Used to indicate whether the Pre-Notification fields should be sent to Buckaroo in a separate file. If set to true/yes, then the request generator engine will insert an entry into BUCKAROO_NOTIFICTN_HEADER_BPE3 table so that the FileProcessor engine will create a separate file with notification data. Only header fields added to this new table. The notification data fields will still be in Buckaroo_Request_Record_Bpe3 table. The file processor configuration must be setup properly to generate the separate Pre-Notification file using the BUCKAROO_NOTIFICTN_HEADER_BPE3 record and notification data from corresponding records in Buckaroo_Request_Record_Bpe3 table. | NO | false |
INTEGRATION.BUCKAROO.BPE3.USE_FIXED_SEPA_DD_COLLECT_DATE | String | Used to indicate whether a fixed day of the month should be used as the collect date. If set to true/yes, then value of SEPA_FIXED_COLLECT_DATE_DAY_OF_MONTH will be used as fixed collect date of that month. | NO | false |
INTEGRATION.BUCKAROO.BPE3.SEPA_FIXED_COLLECT_DATE_DAY_OF_MONTH | String | The day of month to be used as the collect date for all the Direct debit requests in the Buckaroo request file. For ex: If the USE_FIXED_SEPA_DD_COLLECT_DATE is set to 'true' and this parameter has the value '20' and the file was generated for May 2014, then the collect_date for all the Direct debit request records in that file is: 2014-05-20 Please be aware that the value of SEPA_FIXED_COLLECT_DATE_DAY_OF_MONTH must be later than the day of file generation. Also if pre-notification is used, the collect date must be at least <NOTIFICATION_SEND_DATE_OFFSET> days after the file generation date to be able to send pre-notification emails to the customers. | NO | 26 |
INTEGRATION.BUCKAROO.BPE3.NOTIFICATION_SEND_DATE_OFFSET | Number | Used only when Buckaroo Notification service is used. The number of days prior to the collect_date for calculating the pre-notification send-date at which the notification should be sent. If the collect date is 2014-05-20 and the value of NOTIFICATION_SEND_DATE_OFFSET is 14, then the pre-notification send date is 14 days prior to collect date, i.e notification send-date = 2014-05-06. | NO | 14 |
INTEGRATION.BUCKAROO.BPE3.SET_EMPTY_PRENOTIFCTN_SEND_DATE | String | Used only when Buckaroo Notification service is used. Indicates whether the srv_notification_senddatetime field should be set to empty value. In that case Buckaroo will decide when to send pre-notification emails. | NO | false |
INTEGRATION.BUCKAROO.BPE3.NOTIFICATION_TYPE | String | Used only when Buckaroo Notification service is used. The type of notification to send. Can be one of the following:
See Buckaroo Notification service description document for more information | NO | PreNotification |
INTEGRATION.BUCKAROO.BPE3.PRE_NOTIFICATION_COMMUNICATION_METHOD | String | Used only when Buckaroo Notification service is used. The method used to send the notification. Can be one of the following:
Please note: The communication method determines which fields are mandatory. See Buckaroo Notification service description document for more information | NO |
...