Buckaroo

Buckaroo is a well-known Dutch Payment Service Provider. The Buckaroo for FinDock extension supports several payment methods.

Please note your contract with Buckaroo needs to include the payment methods you wish to activate and use.

Pre-requisites

• FinDock is installed and configured.
• FinDock WebHub is connected.

Install and activate Buckaroo payment extension

Follow the standard procedure for installing and activating the Buckaroo payment extension.

Check and assign the required permissions for FinDock and Buckaroo features. Ensure all package-specific permission sets are correctly assigned.

Configure Buckaroo notifications

To ensure FinDock can receive messages from Buckaroo, you need to make a few adjustments to certain settings in Buckaroo Plaza.

1. Log into Buckaroo Plaza.
2. Under My Buckaroo / Websites, click the Push settings tab.
3. Configure these settings:
   • Delayed and Push responses: enable for responses, refunds and invoices
   • HTTP Method: POST
   • Hash method: SHA1

Configure Buckaroo payment extension

To configure Buckaroo for FinDock:

1. Launch the FinDock app and click Setup. You will see a red mark on the Remote Site Settings tab indicating that the remote site settings for Buckaroo are disabled.
2. Open the Remote Site Settings tab and, depending on your org, activate the test or production endpoint of Buckaroo:
   • Test: https://testcheckout.buckaroo.nl
   • Production: https://checkout.buckaroo.nl
3. You should see a notification saying “Success: The remote site setting "Buckaroo" has been activated successfully.
4. Go back to the Setup tab.
5. Scroll down and click on the Buckaroo tile.
6. Fill in the settings for your Buckaroo account and click Save.
   • Name: Enter a name for your account. If you have multiple accounts, ensure the name reflects the purpose or usage of the account.
   • Available Card Brands: Select the card brands you want to display on payment forms. The list includes all supported brands, but only select brands included in your Buckaroo contract.
   • Is Default: Toggle on if the account should be used as the default account for a transaction when no account is provided.
   • Endpoint: This is the Buckaroo server address for initiating transactions. There are two options:
     • Test: https://testcheckout.buckaroo.nl/nvp/
     • Production: https://checkout.buckaroo.nl/nvp/
   • Secret Key: Used to sign the Buckaroo transactions requests. You can create a Secret Key in Buckaroo Plaza under Configuration / Secret / Secret Key.
   • Log Requests: When enabled, all requests to Buckaroo are logged before being submitted. Use with care as this might be data-storage intensive.
   • Website Key: The identifier for the website in Buckaroo Plaza under My Buckaroo / Websites / {yourwebsite}. The website key is in the table in the first row. If you have multiple websites, use the filter option in the top right to switch between websites.
   • Mandate Prefix: If you use Buckaroo for direct debits, you need to enter the Mandate Prefix provided to you by Buckaroo. You can find it in your Buckaroo Plaza account under My Buckaroo / General information / Mandate prefix.

If you have more than one account, see multi-merchant accounts, click Add Account and fill in the settings for your second account.

You merchant account may also include Credit Management. If you have this enabled, the settings for credit management need to be filled out according to your Buckaroo contract.

Activate payment methods

After you have configured the Buckaroo extension, you can activate the payment methods.

To activate Buckaroo payment methods:

1. Launch the FinDock app and click Setup.
2. Click the Activate/Deactivate tab.
3. Click the Payments Method button in the ACTION column of the Buckaroo listing.
4. Toggle on the methods you want to activate.
5. If you have other payment extensions that use the same payment methods, check the ‘Show advanced settings’ option and use the toggle to define which method(s) should use Buckaroo as the default processor.
6. Close the payment method dialog when you are done.

For further information on advanced settings, see Activating payment extensions.

Please also note that Buckaroo uses transaction type codes to distinguish different payment transactions. See below for details about the codes supported by FinDock.

Schedule Buckaroo Apex job (optional)

FinDock regularly listens for webhook notifications from Buckaroo. This is normally sufficient for keeping payment data in FinDock up to date with Buckaroo.

However, it is possible that under certain conditions notifications are missed. To ensure you have all the latest data from Buckaroo, you can schedule a special Apex job, called BuckarooPendingInstallmentsSchedule, to handle updates on transactions.

The Apex batch can be scheduled as needed, but we suggest running it daily if you are going to use it. The job queries all Buckaroo installments in the Salesforce org with status ‘Pending’ and makes a callout to Buckaroo to get the latest status in Buckaroo and updates the installments accordingly as needed.

iDEAL QR with Payment Request Generator

You can generate open or closed iDEAL QRs with the Payment Request Generator using the Ideal reference type.

There are several input mapping fields to define for the generator run, such as amounts, description, expiration date, and QR image size. The QR image size depends on how the QR will be distributed. If no size is defined, FinDock uses the default size of 100x100 pixels.

For the generated values, you need to create custom fields - preferably Buckaroo specific - on the target object to store (output mapping) the following values:

• Payment Reference: Text(255)
• Payment URL: Url(255)
• QR URL: Url(255)
• QR Base 64: Long text Area(32768)

In addition, create a custom Description field (Text(35)) as the input field on Campaign, Campaign Member or other, where you can provide the text that is shown to the payer on the iDEAL payment page.

Payment API message examples

To test your Buckaroo configuration, you can use the following examples with the Payment API.

One-time iDEAL with Buckaroo

The following message initiates a one-time iDEAL payment with Buckaroo, passing a issuer to by-pass the Buckaroo bank selection screen.

{
    "SuccessURL": "https://www.example.com/success",
    "FailureURL": "https://www.example.com/error",
    "Payer": {
        "Contact": {
            "SalesforceFields": {
                "FirstName": "Eric",
                "LastName": "Johnson",
                "Email": "eric@johnson.com"
            }
        }
    },
    "OneTime": {
        "Amount": "36"
    },
    "PaymentMethod": {
        "Name": "Ideal",
        "Processor": "Buckaroo",
        "Parameters": {
            "issuer" : "abnamro" 
        }
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}

Recurring SEPA DD with Buckaroo

The following message initiates a recurring SEPA Direct Debit payment with Buckaroo, passing a holderName and IBAN parameter to set up the Mandate.

{
    "SuccessURL": "https://www.example.com/success",
    "FailureURL": "https://www.example.com/error",
    "Payer": {
        "Contact": {
            "SalesforceFields": {
                "FirstName": "Eric",
                "LastName": "Johnson",
                "Email": "eric@johnson.com"
            }
        }
    },
     "Recurring": {
          "Amount": "25",
          "Frequency": "Monthly",
          "StartDate": "2020-11-01"
     },
    "PaymentMethod": {
        "Name": "Direct Debit",
        "Processor": "Buckaroo",
        "Parameters" : {
            "IBAN" : "NL13TEST0123456789",
            "holderName" : "E. Johnson"
        }
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}

Recurring card with Buckaroo

The following message initiates a recurring card payment with Buckaroo. Important to note is that recurring card payments with Buckaroo require an initial payment on setup. This is indicated by the InitialPaymentonRecurring parameter response from the Payment API.

{
    "SuccessURL": "https://www.example.com/success",
    "FailureURL": "https://www.example.com/error",
    "Payer": {
        "Contact": {
            "SalesforceFields": {
                "FirstName": "Eric",
                "LastName": "Johnson",
                "Email": "eric@johnson.com"
            }
        }
    },
    "OneTime": {
        "Amount": 25
    },
    "Recurring": {
        "Amount": "25",
        "Frequency": "Monthly",
        "StartDate": "2024-01-01"
    },
    "PaymentMethod": {
        "Name": "CreditCard",
        "Processor": "Buckaroo"
        }
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}

Buckaroo transaction types

Buckaroo uses transaction type codes to precisely distinguish payment actions such as collection, refunds and reversals across payment methods, card brands, and other factors.

The following is a list of the currently supported transaction type codes. These codes are recognized by FinDock and used as inbound report subtypes (for report type Buckaroo).

If you need to use a specific transaction type code that is not included in the tables below, please contact FinDock Support.

Transaction codes for collection

Transaction codes for refunds

Transaction codes for reversals