When a form uses the form payment widget to collect payments, you can include payment details — such as the amount, transaction ID, and date — in form communications sent upon submission. These details are available as form payment receipt merge fields.
Your options include:
Use the
Form-Payment-Receiptmerge field to insert a pre-made receipt with a single click.Use specific Form-Payment-Receipt fields — such as
Form-Payment-Receipt.amountorForm-Payment-Receipt.date— to choose which payment details to include and how they appear.
💡 Recurring vs. one-time payments
The merge fields in this article apply to one-time payments only. For recurring payment information (Advancement only), see Form Recurring Pay Merge Fields.
The Form-Payment-Receipt merge field
To add a pre-made payment receipt to a form communication:
Go to Forms.
Select an existing form that contains a payment widget configured to collect payments using Slate Payments, or create a new one.
Select Edit Communications.
Select an existing form communication, or create a new one.
Select Edit Message.
Select the merge field
Form-Payment-Receipt.Slate inserts the following text with merge fields at your cursor:
Thank you for your payment of ${{Form-Payment-Receipt.amount}} on {{Form-Payment-Receipt.date | date:'MMMM dd, yyyy'}}. Payment Account: {{Form-Payment-Receipt.payment_account}} Transaction ID: {{Form-Payment-Receipt.transaction_id}}Edit the surrounding text or format as desired, but leave the merge field names unchanged.
Select Save.
✔ Expect pre-flight warnings.
Slate flags each
Form-Payment-Receiptfield as an unknown merge field because the data isn't part of the recipient list query. You can safely ignore these warnings.
🤔 Not seeing merge field data in test communications?
Merge fields are not populated with values in test messages. To see populated values, test with test records instead.
See also: Testing Form Communications
Form-Payment-Receipt field reference
The Form-Payment-Receipt object includes the following merge fields. These merge fields can be inserted anywhere in your message body. They can also be used with Liquid Markup, for example to display a special message for recurring payments.
Merge Field | Description | Example Output |
|---|---|---|
| Payment amount, formatted as a decimal | 49.51 |
| Payment account name | Application Fee |
| Unique transaction ID of the form | ch_a1B2c3 |
| Recurring payment indicator; returns if recurring | 1 |
| Three-letter currency code | USD |
| Processing fee amount, formatted as a decimal | 0.12 |
| Payment method: | ACH |
| Last four digits of the card or account number | 0123 |
| Payment date; format with the Liquid Markup date filter, e.g. | 2026-06-01 |
Example: Display special message for recurring payments
To display a different message for recurring payments, use the following Liquid Markup:
{% if Form-Payment-Receipt.is_recurring == 1 %}
Thanks for your recurring payment!
{% else %}
Thanks for your payment!
{% endif %}