Overview of Payments in Slate
This article provides an overview of how the payment system works with applications in Slate, how to set it up in your instance and different methods of processing payment, and querying on the payment data.
Slate includes the option to charge fees and collect payments online. The payments can be collected through an integration with an outside payment processor, or using our built-in tool (Slate Payments). This process can be customized in a number of different ways. The following articles describe the different parts of the process.
Please be aware that for a complex payment setup (e.g. conditionally sending different values to a payment processor, or a complex fee waiver process) you should begin the payment setup implementation at least six weeks before go-live.
The standard way to charge payments is to add Payment Due interactions or activities to a person or application record. (At present payments can not be charged in this way for any other type of record.) This article discusses that process, including calculating fees, waiving fees, and how the amount due is determined and displayed. This process will be the same for all types of payment processing. Alternately, payment amounts can be calculated and Payment Due activities added using a form payment widget. When charging an application fee, there is a optional setting to require payment before allowing the application submission to appear as complete.
The payment page that is generated can also be shared with others, such as relatives of an applicant, to allow them to make payments on the applicant’s behalf.
Last Updated on