Overview of Payments in Slate

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 by 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.

Be aware that for a complex payment setup (such as 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.


Payments do not function independently. They must be attached to a record, such as a person record, an applicant record, or a dataset record.

Charging payments in Slate using interactions and activities

The standard way to charge payments is to add Payment Due interactions or activities to a person or application record (currently 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 an 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.

For more information, refer to the Knowledge Base article on Charging Payments in Slate Using Interactions and Activities.

Using an external processor to collect payments through Slate

External payment processors or gateways can often be integrated with Slate to collect online payments and update Slate records accordingly.

For more information, refer to the Knowledge Base article on External Payment Processors.

Using Flywire for international payment processing

This specific use case is also a helpful example of using additional payment accounts to route payments to different vendors.

For more information, refer to the Knowledge Base article on Using Flywire for International Payment Processing

Our built-in Slate Payment System

Slate includes a self-service setup payment processing system called Slate Payments. It can be used to collect payments as described above, and also adds the option of collecting payments within a form using a payment widget. The payment widget adds the option of charging payments for a dataset record as well as a person or application record.

For more information, refer to the various Knowledge Base articles on Slate Payments.

Security and Compliance

Slate uses encrypted transmission at all times, follows best-practice security, and is PCI compliant. We do not store or persist any protected information such as credit card numbers. All payment transactions support TLS version 1.2 and will block TLS 1.0.

For additional information and certification of compliance, refer to the Knowledge Base article on Slate Security Profile and Documentation.

Troubleshooting payment issues

This article provides some things to check when payments aren't behaving as expected and how to obtain assistance.

Viewing and querying payment data

Whether using Slate Payments or an external processor, you have the ability to query and export payment data in Slate

Was this article helpful?
8 out of 9 found this helpful