Page Comparison

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 for. Otherwise the engine is disabled for that 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.ACCOUNT_PAYMENT_TYPES

String

payment_type_id value of the
account_payment entries used to choose 
what type of account payments are 
picked up by the request
generator engine for creating the 
payment export file.
Ex: 200

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
will start with

YES

INTEGRATION.BUCKAROO.BPE3.EXPORT_FILE_EXTENSION

String

Extension used for export file.
For ex: .CSV

YES

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

Value to be put into the 'startrecurrent' field of the Direct Debit request file.

Possible values are: TRUE , FALSE

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.

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.

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.

Used only when Buckaroo Notification service is used.

The type of notification to send. Can be one of the following:

• PreNotification: A pre-notification that is sent some time before performing a scheduled action.
• PaymentComplete: A notification that is sent when a transaction has been completed with success.
  

See Buckaroo Notification service description document for more information

Used only when Buckaroo Notification service is used.

The method used to send the notification. Can be one of the following:

• Email: The notification is sent by email. 

Please note: The communication method determines which fields are mandatory. See Buckaroo Notification service description document for more information