Forms have two widgets relating to payments:

• Payment amount: Lets the registrant (or administrative user completing the form) add items to be calculated toward a total by the Payment widget. Not required to use the Payment widget.

• Payment form: Calculates a total cost and, with Slate Payments, lets registrant (or administrative user completing form) pay with a credit card.

Payment widgets can be used on forms with these scopes:

• Person

• Application

• Dataset

The payment amount widget

You can add a payment amount widget for each item that can contribute to a total cost charged by the payment widget.

Payment amounts are applied to the total payment due unless you filter them out with conditional logic.

The fields you configure in the payment amount widget are available in the Form base for events, including as a join to find all payment amount line items.

To add the payment amount widget to a form:

1. From the main navigation, select Forms.

2. Click New Form, or select an existing form.

3. Configure form settings as needed.

4. From the form palette, select the Payment Amount widget. A popup appears.

Configuring payment amount widget settings

🏔️ Summit 2025 Feature

The Payment Amount widget now includes metadata fields and supports the sum(*) operator in the Formula field, which lets you calculate discounts.

Status

Set to Active or Inactive.

Label

Enter a descriptive, registrant-facing label for the widget. For example, T-shirt (Small).

Alternatively, select Hide Label.

Amount / Formula

Enter an integer to add that amount to the total.

Enter a formula to add the calculated amount to the total.

📖 Further reading: Calculated fields in forms

Here’s an example of a formula that offers a 20% discount to event speakers:

1. Add a Check Boxes widget titled Speaker Discount with a prompt called Discount.

2. Add a Payment Amount widget called  20% Discount, with a Formula value of sum(*) * -0.2. This takes the sum of payment amounts (sum(*)) and multiplies it by negative 0.2, which gives us an amount to discount the total cost by.  

3. Add a filter to the Payment Amount widget for the Speaker Discount form field, and select the filter value IN Discount.

When the administrative form registrant selects Speaker Discount, a 20% discount is applied to the total cost:

Item name

Enter an optional internal item name. For example, T-shirt (sm).

Item code

Enter an optional internal item code. For example, an SKU like TSHIRTSM.

Show amount

Select to display the item’s per-unit cost on the form.

Show quantity

Select to include an item quantity selector.

When this is selected, two options appear:

• Quantity max: Enter a maximum quantity for the selector. Required if Show Quantity is selected.

• Quantity default: Enter an optional quantity to be selected by default.

Conditional logic filters

You can apply this payment amount widget to the total amount due only under certain conditions by filtering for the status of form fields.

The payment form widget

Use the payment form widget on a form to:

• Calculate payment-due amounts and create person-scoped Payment Due interactions on the user’s timeline.

• Collect payments as a part of form submission (Slate Payments only).

To add the payment widget to a form:

1. From the main navigation, select Forms.

2. Click New Form, or select an existing form.

3. Configure form settings as needed.

4. From the form palette, select the Payment Form widget. A popup appears.

Configuring payment form widget settings

Configure the following settings:  

Label

• Enter a descriptive, registrant-facing label for the widget.

• Alternatively, select Hide Label.

Payment Amount

• Sum of Payment Amounts: Request the sum of all the payment amount widgets in the form not filtered by conditional logic.

• Amount/Formula: Enter the amount or formula to be calculated. Enter an integer to charge just that amount.

Payment Account

Select the account to be associated with the payment interaction.

Embed Payment Form

• Enable Embedded Payment Collection on Form: Embed the payment collection on the form. Available for Slate Payments only.

• Calculate Payment Due: Slate calculates the total amount due and displays it to the registrant.

If you are using the payment widget, it will automatically add a Payment Due activity or interaction (depending on scope) when the form is submitted. This can replace the use of a separate rule to add the payment due. If a payment rule is already on an existing form, it should be removed or inactivated.

If the payment collection is embedded on the form, the widget will use the Slate Payment configuration (deposit account, mode, or options) set up in the Application Editor for the selected payment account (as described in Step 3 of the Setting up Slate Payments guide).

Create New Payment Due for Each Submission

Select this option if it is possible that the same user will submit this form multiple times at different points in time (for example, a giving form).

Internal Only

Choose this option if the payment widget should be loaded only for internal form registrations.

Mapping payment form widget fields

Map relevant form fields to their corresponding system fields.

That way, the relevant record can be created or matched when the form is submitted and the resulting payment activity/interaction and payment record can be properly connected.

📝 Note

Payment widgets should be extensively tested on all forms before the form is made live.

Click Save.

Calculate payment-due amount

You can calculate the payment due by leveraging fields on the form. The accompanying screenshot demonstrates a cost for the registrant, plus a cost for guests multiplied by the number of guests; this calculation determines the total amount due. The payment amount calculation works the same as any calculation formula in a form field.

📖 Read more: Calculated fields

If the payment amount is fixed, just add a number. In this example, just the number itself—no dollar sign or other text required.

When using the widget to calculate the payment amount but not to collect the payment, a Payment Due activity or interaction will be created. For application-scoped payments, a link to make the payment will be visible on the applicant status page, assuming the 'Show Payment Due Link' setting is set, or on their custom status portal, assuming the Payments portal widget is added to the view.

For person-scoped payments, a form communication containing the merge field of Form-Payment must be created. This will direct registrants to the payment landing page. The Form-Payment merge field is only used when the payment is not collected directly through Slate Payments.

Troubleshooting the payment form widget

Prohibited scopes

You cannot use the payment form widget on forms built on any of the Page Construction or Page Construction Widgets scopes.

Only one widget

Don’t create more than one payment widget that collects payments per form.

No additional form rules needed

The payment widget will automatically add a Payment Due activity or interaction to the record. Because of this, there should not be any additional rules on the form that add another Payment Due item (for the same payment_account prompt value). If an existing form that previously used rules to add a Payment Due is being updated, remember to inactivate or delete these rules.

Using the payment form widget with Slate Payments

• No Partial Payments: Slate Payments deposit accounts have an option that can allow for partial payments. This option cannot be used with a payment form widget that collects payments.

• No “Save for Later” Option: If the payment widget is using Slate Payments to collect a payment at time of form submission, do not use the “save for later” setting within Edit Properties of the form as this may lead to submission errors.