Payment Form configuration options

The embedded Payment Form for Giving Pages and PayLinks is fully integrated with your payment processing configuration in FinDock. Wherever possible, we use default values in the form settings to help you to create and publish pages quickly. These values are adequate in most cases, but the range of settings give you many ways to customize and optimize the payment experience.

Common settings

As with other page elements, you can modify the basic appearance - font, background, padding and so forth - of the Payment Form. In addition, there is one important appearance setting under the Payment Form settings proper: brand color.

The brand color setting determines the color of the radio button, checkboxes and button(s) on the payment form. The default color in the templates has been set to fit the color scheme of the template images.

The payment form background color can also be adjusted, but we strongly advise you to keep this white or a light color to keep the form readable.

Page labels

For each step of the payment process, there are page labels to help guide the donor through the process. These labels include the title of the form page and buttons to allow the donor to proceed or move back through the payment steps.

Amounts and frequency

The amount and frequency settings define the donation options presented to page visitors. This includes basic payment parameters like donation amount as well as key texts like the narratives for preset donation levels, campaign and origin.

If FinDock for Fundraising is installed, you also have the Tributes available.

Frequency settings

Open amount error messages

Personal details

The personal details settings are an important part of the payment form, both in terms of privacy and personalization of future donor follow-up journeys. The European GDPR rules apply here, so you need to inform donors what information is being collected and for what purposes. Use the privacy text editor to create a privacy statement (and/or link to your full statement on your website).

The next step is to click the Personal Details button to set which details will be collected. By default, only the minimum amount of information is collected that is required for payment processing. Use the mapping table (pictured below). For each detail, you can define the field label (displayed in the form), a placeholder value, Salesforce mapping, as well as whether or not the detail is visible and required. Learn more about input fields and how to add your own here

Required field for Person Account

If your org is using person accounts, you need to map personal details fields to Account rather than Contact.

In addition, you need to explicitly map a record type on Account to a Person Account record type using an additional input field. Define thee field as required for the page, but not visible.

Payment details

In this part of the payment form configuration, you need to decide what payment method(s) will be offered and how those methods are configured.

If Gift Aid is installed, you also have the following options.

Payment Details

Click the Payment Details button to open the configuration details (pictured below).

The main aspects to plan and configure are:

• Which payment methods you want to offer
• The order in which the method options should be lists for donors
• The default method for each payment period (one-time and recurring)
• Require initial payment for recurring payments (if applicable and optional for the given PSP and method).

The payment methods available in the configuration popup depend on which processors and methods you have activated in FinDock. Only activated methods can be used in the payment form. Use the left-right and up-down arrows to add methods to the form and change the order.

For each payment method, you can enter a custom label (name shown to the donor) and use the toggles to define the defaults for one-time and recurring options.

In addition, any parameters that are available for the given processor and method are available for configuration. You can see these by clicking the Show Parameters button. For each parameter you can define a label, a default value (if allowed), as well as set visible and required toggles.

For some methods, if the parameters are required by the payment method (e.g. account holder name and account number for Bacs DD), they are already set accordingly and made visible for donors. However, required description parameters (typically used for internal purposes) have visible turned off by default.

Cover Transaction Fees

Here you can present the payer with an optional additional amount to add to the payment. This cover fee can be used to cover operational costs, such as payment processing fees or surcharges for special payment methods.

Thank you page

Here you configure the thank you message that you would like to show visitors who have made a donation.

Error

In addition to the error page that is displayed when something goes wrong with the payment process, you can define here the error messages that appear when a field value is missing or incorrect.

Error page

Here you configure the error message that that is shown visitors who have made a donation, but for some reason (e.g. lost internet connection) the payment could not be processed.

Add additional form fields

Next to the standard fields added by default, you can add your own fields to the form. Three types of fields can be added.

Fields can be added to the following pages of the Payment Form by pressing the + Add button in the Fields section of their respective Payment Form setting pages:

• Amounts & Frequency
• Personal Details
• Payment Method (selection)

You can also re-order the fields by pressing and holding while dragging the hamburger icon in front the field label.

Input fields

Input fields have the following settings or attributes:

Fields can be mapped to Salesforce fields to store the data in your system. You can map fields to fields on objects directly related to FinDock payments: Contact, Account, Installment, Recurring (what object is used depends on your default source connector and Inbound Report. The type of input field - text, phone, email, checkbox, picklist, date - is determined by the Salesforce field it is mapped to.

Special input fields

Date fields: To make it easy to enter date fields on the payment form, there is a specific user interaction for the Birthday field on Contact. This field is shown as a date picker with a separate input step for day, month and year. By changing the placeholder values, the date picker can be translated. However, the order of the fields cannot be changed.

Date fields other than the Birthday field use a calendar selection pop-out to make it easy to select a certain date.

Merge fields

You can use merge fields with input fields and payment method parameters (text fields) to generate unique default values. Merge field definitions must follow the standard Salesforce notation: default-text{!fieldname}

For an input field, you would enter your default-text{!fieldname} in the Default field of the input field definition. For payment method parameters, you can do the same with default values in the payment method configuration.

A good use case is the description parameter of the payment method, like Stripe credit card. There you can add a personalized thank-you message, as pictured below.

In this example, if the payer enters "John" for First Name in the payer details, the description would return the value "Thank you for contributing to our whale conservation effort, John."

When using merge fields, keep in mind:

• If the field to be merged is not populated, an empty value is returned (in the example, it would be just “Thank you for contributing to our whale conservation effort,.”)
• If the merge field does not actually exist (or, for instance, it is mistyped), a non-blocking warning is triggered indicating you are trying to use a merge field which does not exist.

URL query parameters

Custom field parameters

The URL query parameters based on custom fields can be used for:

• Pre-filling fields on the donation form
• Sending additional (hidden) data to Salesforce

You can use any field as a URL parameter from the Contact, Account, Recurring Donation, Installment and Inbound Report objects. The only exception is birthday, which cannot be pre-filled by query.

Custom form fields that you define in the Page Builder are also available for URL queries. When you have defined a custom field, use the field Id as the parameter name. For instance, in the custom field below the URL parameter would be https://your-domain.com/page-name?custom_JXOxz8n1Wnityju=somevalue.

Preset parameters

The following parameters can be added to URLs to override configured values for amount and frequency presets.

The follow parameters are deprecated. Use instead the monthly parameters defined above.

Payment method parameters

Payment method parameters, such as Description, can also be used as URL query parameters. These use the following construction:

Generic payment method parameter:

https://url? + pmp + [payment-method-parameter] + =value

For example: https://url?pmp[description]=mydescription

Specific payment method parameter:

https://url? + pmp + [payment-method] + [payment-method-parameter] + =value

For example: For example: https://url?pmp[ideal][description]=mydescription

All query parameters that you add to the URL are first evaluated by FinDock to check for validity.