Skip to content
MapleGatherMapleGather Help

Configure receipt templates

This guide shows you how to customize the email receipts that MapleGather sends to members after a payment, refund, event registration, or donation.

Who can do this: Admins with the receipt_templates:write permission.

Before you start

Section titled “Before you start”
  • Receipts fire automatically after any successful payment. You don’t need to configure templates to start receiving receipts — the defaults work out of the box.
  • There are four template slots: a global default and per-type overrides for payment receipts, refund receipts, donation receipts, and event receipts. The per-type template takes priority.
  • What the payment receipt email uses today: your Payment receipt template’s Email subject and body, with these four merge tags filled in: {Organization.name}, {Member.firstName}, {Member.name} and {Payment.amount}.
    • The body is used as plain text. It appears at the top of the email, in place of the standard greeting and thank-you line, and MapleGather’s receipt details follow it: what was paid for, any tax, the total, the payment date and method, the payment reference and your organization’s name. Those details are always included. Any formatting in the body (bold, links, lists) does not carry over; paragraphs and line breaks do.
    • Only those four tags work in a payment receipt. If the subject uses any other tag, the standard subject (“Your payment receipt from” followed by your organization’s name) is sent instead. If the body uses any other tag, or is empty, the standard greeting and thank-you line are sent instead. A raw tag never reaches a member.
    • Receipts for event payments are payment receipts too. Without a template, the email uses the standard subject and wording.

Steps

Section titled “Steps”
  1. In the admin sidebar, select Billing & payments, then select Receipt templates.
  2. Select the tab for the template type you want to configure: Payment receipt, Refund receipt, Donation receipt, or Event receipt.
  3. Edit the Email subject field. You can include merge tags here (for example, {Member.firstName}).
  4. Edit the template body. Write it as plain text — formatting is not kept in the email. Use the available merge tags to personalize the receipt content. On the Payment receipt tab, use only these:
    • {Member.firstName} — the member’s first name
    • {Payment.amount} — the payment amount
    • {Organization.name} — your org’s name
    • {Member.name} — the member’s full name
  5. If you use a merge tag that isn’t recognized, a warning will appear listing the available tags. Correct or remove the unrecognized tag before saving.
  6. To preview how the receipt will look to a member, select Preview as member.
  7. Select Save to save the template.

Verify

Section titled “Verify”

You’ll know it worked when the template saves without errors. The new template applies to all receipts of that type going forward. Use Preview as member to verify the content before your next payment is processed.

If something goes wrong

Section titled “If something goes wrong”
  • “Unrecognized merge tag” — a merge tag in the template doesn’t match the available library. The warning lists what’s available. Check for typos and correct or remove the unrecognized tag.
  • Your wording isn’t in the payment receipt email — the subject or body uses a tag other than the four above (or the body is empty), so the standard wording was sent for that part. Remove the other tag and save.
  • If you switch tabs without saving — a confirmation dialog asks if you want to discard unsaved changes. Select Discard to leave, or Stay to go back and save.
  • “You don’t have permission” — the template form is read-only. Contact your org’s primary admin to request the receipt_templates:write permission.
Section titled “Related”