Form Payment Receipt Merge Fields

Prev Next

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.

You can:

  • Use the Form-Payment-Receipt merge field to insert a prebuilt receipt.

  • Use specific Form-Payment-Receipt fields, such as Form-Payment-Receipt.amount or Form-Payment-Receipt.date, to choose which payment details to include and how they appear.

💡 Recurring vs. one-time payments

Use the merge fields in this article for payment receipt details from a form submission. For recurring payment schedule details, see Form Recurring Pay Merge Fields.

The Form-Payment-Receipt merge field

To add a prebuilt payment receipt to a form communication:

  1. Go to Forms.

  2. Select an existing form that contains a payment widget configured to collect payments using Slate Payments, or create a new one.

  3. Select Edit Communications.

  4. Select an existing form communication, or create a new one.

  5. Select Edit Message.

  6. Select the Form-Payment-Receipt merge field.

  7. 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}}
  8. Edit the surrounding text or formatting, but leave the merge field names unchanged.

    Payment receipt merge field example

  9. Select Save.

✔ Expect pre-flight warnings

Slate flags each Form-Payment-Receipt field as an unknown merge field because the data is not 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.

📖 Further reading: 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.

Merge field

Description

Example output

{{Form-Payment-Receipt.amount}}

Payment amount, formatted as a decimal.

49.51

{{Form-Payment-Receipt.payment_account}}

Payment account name.

Registration Fee

{{Form-Payment-Receipt.transaction_id}}

Unique transaction ID of the form.

ch_a1B2c3

{{Form-Payment-Receipt.is_recurring}}

Recurring payment indicator. Returns 1 if recurring.

1

{{Form-Payment-Receipt.currency}}

Three-letter currency code.

USD

{{Form-Payment-Receipt.fee}}

Processing fee amount, formatted as a decimal.

0.12

{{Form-Payment-Receipt.payment_type}}

Payment method: CC for credit card or ACH for bank account.

ACH

{{Form-Payment-Receipt.last4}}

Last four digits of the card or account number.

0123

{{Form-Payment-Receipt.date}}

Payment date. Format with the Liquid Markup date filter, such as {{Form-Payment-Receipt.date | date:'MMMM dd, yyyy'}}.

2026-06-01

Example: display a 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 %}

Still looking for what you need?