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.

Prerequisites

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

Install Buckaroo extension

Follow the standard procedure for installing payment processors to add the Buckaroo payment extension and activate payment methods.

Check and assign the required permissions. If you are using custom permission set groups, ensure the Buckaroo permission sets are 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 extension

To configure Buckaroo for FinDock:

Available card brands

In addition to setting up your merchant account(s), the Buckaroo extension includes general settings where you define the card brands that are displayed on payment forms. The list of available card brands shows all supported brands. The most common brands are enabled by default, but please check and ensure the selected brands are included in your Buckaroo contract. Payments made with card brands not included in your contract will fail.

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.

SEPA Direct Debit options with Buckaroo

If you use Buckaroo for SEPA Direct Debit payments, ensure the FinDock Core mandate service is set to automatically create mandates.

For direct debit payments created through the Payment API, including PayLinks and Giving Pages, FinDock creates mandates based on the mandate service settings. Upon creation, the mandates get the status Success and are activated. The mandate reference is then sent to Buckaroo as part of the first installment collection through a payment schedule.

If a SEPA Direct Debit payment is created by a Salesforce user, you only need to create the recurring payment and payment profile.

To manually create Salesforce records for new SEPA Direct Debit payments:

1. Create a payment profile for the payer with record type IBAN.
2. Fill in the required fields for the payer's bank account.
3. Create a new recurring payment and link it to the payment profile.
4. Run a payment schedule to collect the first installment.

If you are creating Salesforce records for a migration that includes existing mandates, be sure to set the migrated mandates to active (and status Success). You can migrate Buckaroo mandate reference different ways.

Mandates that should no longer be used for collection can be deactivated by emptying the Active checkbox on the record. This can be done manually for each Mandate record or automated through Salesforce tooling.

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": "Test",
                "LastName": "Payment",
                "Email": "testpayment@findock.com"
            }
        }
    },
    "OneTime": {
        "Amount": "36"
    },
    "PaymentMethod": {
        "Name": "Ideal",
        "Processor": "Buckaroo",
        "Parameters": {
            "issuer" : "abnamro" 
        }
    },
    "Settings": {
        "SourceConnector": "PaymentHub"
    }
}

Recurring SEPA Direct Debit 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": "Test",
                "LastName": "Payment",
                "Email": "testpayment@findock.com"
            }
        }
    },
     "Recurring": {
          "Amount": "25",
          "Frequency": "Monthly",
          "StartDate": "2020-11-01"
     },
    "PaymentMethod": {
        "Name": "Direct Debit",
        "Processor": "Buckaroo",
        "Parameters" : {
            "IBAN" : "NL13TEST0123456789",
            "holderName" : "T. Payment"
        }
    },
    "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": "Test",
                "LastName": "Payment",
                "Email": "testpayment@findock.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